# FedEx — API Agent Score

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

FedEx scored 73/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 85/100 (A)
- Developer Experience: 66/100 (C)
- Agent Discovery: 63/100 (C)
- Agent Understanding: 61/100 (C)
- Agent Usability: 90/100 (A+)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [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] Schema coverage & depth — 83% of operations have documented schemas (target 95%+). Investigated: spec 75%, sdk 25%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%, spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.fedex.com/signup (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Changelog published — changelog documented in the docs site at https://developer.fedex.com/api/en-us/home.html/changelog. Investigated: spec 100%, docs 100%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://developer.fedex.com/api/en-us/home.html/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [warn] Description completeness — 14/18 operations lack a description. Investigated: sdk 22%, spec 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (fishisfast/fedex_apis, 82 snippets). Investigated: docs 100%, sdk 50%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.fedex.com/api/en-us/home.html/llms.txt, https://developer.fedex.com/llms.txt, https://developer.fedex.com/docs/llms.txt). Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.
- [warn] Docs reachable, not hard auth-gated — All 1 pages require authentication. Investigated: docs 20%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 1 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 86%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, sdk) is 10% (threshold 35% for full credit).
- [fail] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Idempotency documented — idempotency documented in the docs site at https://developer.fedex.com/api/en-us/home.html/idempotency. Investigated: spec 100%, docs 100%, sdk 0%.
- [pass] Rate-limit signaling — rate-limit behavior documented in the docs site at https://developer.fedex.com/api/en-us/home.html/rate-limits. Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — sandbox documented in the docs site at https://developer.fedex.com/api/en-us/home.html/sandbox. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

FedEx's API design surface is strong, and agent discoverability shows a solid foundation — but the partner program has a critical gap in agent-readiness: docs lack the structured signals, operational clarity, and machine-parseable context that AI agents and modern developer tooling require to integrate without hand-holding. The highest-priority work is making every operation and endpoint self-describing for both human partners and AI agents, followed by ensuring partners can go from discovery to a running, tested workflow without friction. Closing these gaps will meaningfully reduce partner onboarding time and support burden.