# Brex — API Agent Score

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

Brex scored 72/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 81/100 (A)
- Developer Experience: 66/100 (C)
- Agent Discovery: 76/100 (B)
- Agent Understanding: 75/100 (B)
- Agent Usability: 63/100 (C)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: docs 100%, wellknown 100%, spec 55%.
- [warn] Machine-readable, versioned contract — info.version="1.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [warn] Schema coverage & depth — Only 69% of operations have documented schemas. Investigated: spec 73%, sdk 0%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [warn] Example coverage — 0% example coverage. Investigated: spec 5%, docs 0%, sdk 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.brex.com/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 43% description completeness. Investigated: spec 100%.
- [pass] Changelog published — changelog documented in the docs site at https://developer.brex.com/changelog. Investigated: spec 100%, docs 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/developer_brex_guides, 112 snippets). Investigated: docs 100%, sdk 100%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 75%.
- [warn] Docs reachable, not hard auth-gated — 38 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] Crawlable / AEO — robots.txt blocks 2 of 7 monitored AI crawlers on docs paths (google-extended, ccbot). Investigated: wellknown 50%.

### 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%, spec 50%.
- [warn] Operation purpose clarity — 86% of operations are agent-inferable (target 90%+). Investigated: spec 90%.
- [warn] Agent-navigable, token-efficient docs — 2 of 48 pages have substantive content differences between markdown and HTML (avg 2% missing). Investigated: docs 80%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 6% (threshold 35% for full credit).
- [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 2 assessed pages (2 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Pagination documented & consistent — Cursor pagination detected (most robust 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%.
- [warn] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 38%, docs 38%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Brex's API program shows strong API design fundamentals and solid agent discoverability foundations, but two areas are holding back partner outcomes: agent understanding and developer experience. AI agents and coding assistants lack the structured context files, machine-readable doc formats, and explicit instruction guides they need to build integrations autonomously — increasing the risk of hallucinated or broken implementations. Partners also face friction at the start of their journey, with no quickstart path or copy-paste code samples to reach a first working call quickly. Prioritizing agent-ready documentation and runnable onboarding will meaningfully reduce integration time and support load across your partner program.