# PayPal — API Agent Score

> Score: 71/100 (Grade: B) | Domain: paypal.com | Rubric: 1.0.0 | Checked: July 24, 2026

PayPal scored 71/100 (B), classified "partially-ready".

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

## Summary

- Overall: 71/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 77/100 (B)
- Developer Experience: 81/100 (A)
- Agent Discovery: 60/100 (C)
- Agent Understanding: 86/100 (A)
- Agent Usability: 59/100 (D)

## Check Results

### API Design

- [warn] Schema coverage & depth — 18/19 (95%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 92%, spec 58%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [warn] Security & governance hygiene — 3 credential-shaped strings detected in spec: bearer-jwt (×3). Investigated: spec 90%, wellknown 50%.
- [pass] Example coverage — No parameters or responses available to score example coverage. Investigated: spec 100%, sdk 100%.
- [warn] Auth declared & discoverable — No securitySchemes declared. Investigated: docs 30%, spec 15%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://www.paypal.com/console/signup; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Description completeness — 50% description completeness. Investigated: spec 100%, sdk 90%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%.
- [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.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (paypal/paypal-js, 238 snippets). Investigated: docs 100%, sdk 100%, mcp 50%, cli 0%, wellknown 0%.
- [warn] Crawlable / AEO — Sitemap present (1213 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%, sdk 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: docs 100%, sdk 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [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 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Pagination documented & consistent — page_size pagination detected (good for agents). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.

## Executive Summary

PayPal's API program shows strong fundamentals in contract design, schema quality, and auth — areas partners and agents can build against with confidence. The most urgent gaps are in operational reliability and agent discoverability: agents attempting to integrate today will find no idempotency guidance, no rate-limit signaling, and no machine-readable front door to navigate the API surface. Prioritize making the program reliably executable for agents first, then close the discoverability and contextual documentation gaps so partners — and the AI tools they rely on — can self-serve without friction.