# PwC — API Agent Score

> Score: 46/100 (Grade: F) | Domain: pwc.com | Rubric: 1.0.0 | Checked: July 30, 2026

PwC scored 46/100 (F), classified "not-ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/pwc)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 46/100 (F)
- Classification: not-ai-ready

## Category Scores

- API Design: 40/100 (F)
- Developer Experience: 100/100 (A+)
- Agent Discovery: 49/100 (F)
- Agent Understanding: 40/100 (F)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Schema coverage & depth — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.
- [skip] Example coverage — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.pwc.com/us/en/careers/entry-level/programs-events.html; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [skip] Quickstart present — No surface produced evidence for this capability in this run.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.
- [skip] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [warn] Registry & SDK presence — Discovered SDKs in only 1 language(s); target ≥3. Investigated: sdk 50%, docs 0%, cli 0%.
- [warn] Crawlable / AEO — Sitemap present (107 entries) but carries no lastmod values. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

PwC's API program shows meaningful presence in crawlability and registry basics, but partners and their agents face critical blockers in three areas: security hygiene gaps undermine trust before a first call is made, and the complete absence of machine-readable discovery signals (llms.txt, AGENTS.md) means AI agents cannot find or understand the API surface without manual intervention. To unlock self-serve partner adoption and agent-driven integrations, the immediate priority is establishing a secure, discoverable, and executable API front door — starting with discovery infrastructure and runnable context, then closing the security and agent-instruction gaps.