# Corpay — API Agent Score

> Score: 80/100 (Grade: A) | Domain: corpay.com | Rubric: 1.0.0 | Checked: August 17, 2026

Corpay scored 80/100 (A), classified "ai-ready".

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

## Summary

- Overall: 80/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 87/100 (A)
- Developer Experience: 77/100 (B)
- Agent Discovery: 75/100 (B)
- Agent Understanding: 91/100 (A+)
- Agent Usability: 71/100 (B)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication is required across the API (declared globally or on every operation), so an agent knows credentials are needed. Investigated: docs 100%, spec 50%, wellknown 0%.
- [warn] Machine-readable, versioned contract — The API sets a version ("1.0.0") but exposes no versioning scheme in the URL, a header, or the media type, so an agent can't pin to a specific version. Investigated: spec 75%, docs 50%.
- [warn] Schema coverage & depth — Only 88% of the 32 operations document both request and response schemas (target 95%+), so an agent can't reliably call the rest. Investigated: spec 67%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — 81% of parameters and responses (104 of 128) include example values, grounding an agent in real payload shapes. Investigated: spec 100%, docs 100%.

### Developer Experience

- [pass] Self-service developer portal — Signup page found at https://www.corpaylodging.com/get-started, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples appear on 9 of 20 sampled docs pages across 1 language(s), but broader multi-language coverage is missing. Investigated: docs 100%.
- [pass] Changelog published — changelog is documented on the docs site at https://api.corpay.com/changelog, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [warn] Quickstart present — Quickstart page is reachable at https://api.corpay.com/integrate-ev-charging-network-into-the-car (1 variants scanned) but has no runnable code sample in its HTML or .md variant, so there's nothing to copy and run. Investigated: docs 50%.
- [fail] Description completeness — Only 55% of operations and parameters have descriptions (20 of 32 ops, 15 of 31 params), leaving an agent to guess what most endpoints do. Investigated: spec 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [warn] llms.txt present, valid & comprehensive — llms.txt contains parseable links but doesn't fully follow the proposed structure: https://api.corpay.com/llms.txt: No blockquote summary found. Investigated: docs 92%.
- [pass] Crawlable / AEO — robots.txt lets all monitored AI crawlers reach the docs paths. Investigated: wellknown 100%.
- [fail] Registry & SDK presence — Not indexed on Context7 — agents can't pull this API's docs on demand via Context7. Investigated: docs 0%, sdk 0%, cli 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Documents 6 distinct 4xx/5xx error response codes, so an agent can branch on specific failures instead of guessing. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations (32 of 32) have both a clear summary and a descriptive name, so an agent can pick the right endpoint. Investigated: spec 100%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [pass] Docs structured data — Machine-readable JSON-LD Article markup on 16 of 16 assessed pages (100%), with dateModified present. Investigated: docs 100%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/, so coding agents have no ready-made setup and usage instructions. Investigated: wellknown 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Rate-limit signaling — rate-limit behavior is documented on the docs site at https://api.corpay.com/rate-limits, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [pass] Pagination documented & consistent — pagination is documented on the docs site at https://api.corpay.com/api-reference/customer/list-customers, even though it isn't declared in the API spec. Investigated: docs 100%, spec 50%.
- [pass] Sandbox separation — Sandbox server (https://apigwuat.corpay.com) declared in spec with distinguishable test credentials. Investigated: spec 100%, docs 100%.
- [fail] Idempotency documented — Only 0% of mutating operations (0 of 24) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace found for the org, so there's no runnable collection an agent can execute against. Investigated: platform 0%.

## Executive Summary

Corpay's API program shows real strengths in API design — the contract is machine-readable and well-typed, giving partners a solid foundation to build against. The two areas that most urgently limit partner and agent adoption are description coverage (only 55% of operations and parameters are described, leaving agents to guess at intent) and discoverability (the API is absent from agent-accessible registries and toolchains). Prioritize enriching the spec and standing up an agent-ready documentation surface first, then layer in runnable collections and idempotency guidance to close the remaining reliability gaps that put production integrations at risk.