# Modern Treasury — API Agent Score

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

Modern Treasury scored 70/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 79/100 (B)
- Developer Experience: 52/100 (D)
- Agent Discovery: 71/100 (B)
- Agent Understanding: 83/100 (A)
- Agent Usability: 65/100 (C)

## 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="v1" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [warn] Schema coverage & depth — 87% 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 0%.
- [fail] Example coverage — 0% example coverage. Investigated: spec 0%.

### Developer Experience

- [pass] Description completeness — 67% description completeness (target 90%+). Investigated: spec 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/moderntreasury_platform_reference, 156 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — Could not test any pages; 1 failed to fetch. Investigated: docs 50%.
- [warn] Docs reachable, not hard auth-gated — 1 JavaScript redirect(s) detected across 1 pages. Investigated: docs 50%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 10 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 98% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 69%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [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 — Pagination params detected on 41 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Test credentials signaled (test-key prefixes) but no sandbox server declared in spec. Investigated: spec 100%, docs 100%.
- [warn] Idempotency documented — 43% of mutating operations document idempotency (target 70%+). Investigated: spec 50%, docs 50%.
- [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

Modern Treasury's API program shows genuine strengths in agent discoverability and documentation parseability, but two areas demand immediate attention: partners lack a self-service portal and quickstart path, meaning they cannot get hands-on without a sales conversation, and the API spec is missing concrete request/response examples, leaving both developers and AI agents guessing at real data shapes. Closing these gaps — alongside adding agent instruction context and rate-limit signaling — will materially shorten partner onboarding and make the API safe for autonomous agent workflows.