# Emburse — API Agent Score

> Score: 60/100 (Grade: C) | Domain: emburse.com | Rubric: 1.0.0 | Checked: July 29, 2026

Emburse scored 60/100 (C), classified "partially-ready".

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

## Summary

- Overall: 60/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 68/100 (C)
- Developer Experience: 58/100 (D)
- Agent Discovery: 70/100 (B)
- Agent Understanding: 75/100 (B)
- Agent Usability: 41/100 (F)

## Check Results

### API Design

- [warn] Machine-readable, versioned contract — info.version="1.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 83%, docs 67%.
- [warn] Schema coverage & depth — 86% of operations have documented schemas (target 95%+). Investigated: spec 67%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [warn] Auth declared & discoverable — No securitySchemes declared. Investigated: docs 33%, spec 17%.
- [fail] Example coverage — 1% example coverage. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.emburse.com/requests/demo-request; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [warn] Quickstart present — Quickstart page reachable (1 variants scanned starting at https://www.emburse.com/requests/demo-request) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [warn] Description completeness — 44% description completeness. Investigated: spec 17%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 1 pages. Investigated: docs 50%.
- [warn] Registry & SDK presence — Discovered SDKs in only 1 language(s); target ≥3. Investigated: sdk 50%, docs 0%, cli 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 7 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 81%.
- [warn] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 67%.
- [warn] Docs structured data — JSON-LD on 3/20 assessed pages, but coverage is sparse or dateModified is missing. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 13% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.

### Agent Usability

- [warn] Pagination documented & consistent — 4 list endpoint(s) exist but no pagination params found. Investigated: spec 33%, docs 33%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — No sandbox/test server declared across 2 server entries; no test-key prefixes 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

Emburse's API program shows strength in documentation discoverability and structured data, but two areas are holding back partner integration outcomes: agent usability (sandbox access, runnable examples, and operational reliability signals) and developer experience (no published changelog, missing code samples). Partners and their AI agents lack the executable context, safe testing environment, and reliability signals needed to build with confidence. Prioritize closing the agent usability gaps first — they block real integrations — then sharpen developer experience to compress partner onboarding time.