# Recharge Payments — API Agent Score

> Score: 59/100 (Grade: D) | Domain: rechargepayments.com | Rubric: 1.0.0 | Checked: July 24, 2026

Recharge Payments scored 59/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 59/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 81/100 (A)
- Developer Experience: 49/100 (F)
- Agent Discovery: 47/100 (F)
- Agent Understanding: 75/100 (B)
- Agent Usability: 49/100 (F)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — API versioning documented in the docs site at https://docs.getrecharge.com/docs/api-versions. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [warn] Schema coverage & depth — Only 30% of operations have documented schemas. Investigated: spec 50%.
- [fail] Example coverage — 0% example coverage. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Description completeness — 66% description completeness (target 90%+). Investigated: spec 100%.
- [warn] Quickstart present — Quickstart page reachable (24 variants scanned starting at https://developer.rechargepayments.com/2021-11/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [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] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%, sdk 0%.

### Agent Discovery

- [warn] Docs reachable, not hard auth-gated — 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] Crawlable / AEO — Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.rechargepayments.com/2021-11/llms.txt, https://developer.rechargepayments.com/llms.txt, https://developer.rechargepayments.com/docs/llms.txt). Investigated: docs 0%.
- [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) — Only 3 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: spec 100%, docs 100%.
- [pass] Operation purpose clarity — 100% 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 71%.
- [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 1 assessed pages (1 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Rate-limit signaling — rate-limit behavior documented in the docs site at https://docs.getrecharge.com/docs/api-rate-limits. Investigated: spec 100%, docs 100%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — No sandbox/test server declared across 1 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%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Recharge Payments demonstrates strong API design fundamentals and solid agent understanding, but the partner program has critical gaps in discoverability, onboarding, and safe integration that will block both partners and AI agents before they can make a single call. The most urgent priorities are establishing a discoverable, self-serve front door with machine-readable documentation, and providing runnable, sandbox-safe workflows that let partners — and the agents they bring — go from zero to productive without a sales conversation or fear of hitting production data.