# httpbin — API Agent Score

> Score: 62/100 (Grade: C) | Domain: httpbin.org | Rubric: 1.0.0 | Checked: November 10, 2026

httpbin scored 62/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 64/100 (C)
- Developer Experience: 40/100 (F)
- Agent Discovery: 71/100 (B)
- Agent Understanding: 89/100 (A)
- Agent Usability: 54/100 (D)

## Check Results

### API Design

- [warn] Schema coverage & depth — Only 0% of the 78 operations document request and response schemas, so an agent can't do function-calling against most endpoints. Investigated: spec 67%, sdk 0%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [warn] Machine-readable, versioned contract — The API declares no version and exposes no versioning scheme, so an agent can't pin to a stable contract across releases. Investigated: spec 50%, docs 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Auth declared & discoverable — The spec declares no authentication scheme, so an agent can't tell how to authenticate a request. Investigated: spec 0%, docs 0%.

### Developer Experience

- [fail] Self-service developer portal — No self-service signup detected — no signup link on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved — so an agent can't onboard on its own. Investigated: docs 0%.
- [fail] Quickstart present — No quickstart or getting-started page found at the conventional docs paths, so new developers and agents have no obvious first step. Investigated: docs 0%.
- [fail] Code samples in docs — No code samples detected across 1 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [fail] Description completeness — Only 56% of operations and parameters have descriptions (62 of 78 ops, 22 of 69 params), leaving an agent to guess what most endpoints do. Investigated: spec 0%.
- [fail] Changelog published — No changelog link or mention appears in the spec, so an agent can't tell what changed before something breaks. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (postmanlabs/httpbin, 388 snippets). Investigated: docs 100%, sdk 50%, cli 0%.
- [warn] Crawlable / AEO — No sitemap found via robots.txt or /sitemap.xml on the docs host, so AI search engines have no crawl map for your docs. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://httpbin.org/llms.txt, https://httpbin.org/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Documents 5 distinct 4xx/5xx error response codes, so an agent can branch on specific failures instead of guessing. Investigated: spec 100%, docs 100%.
- [pass] Operation purpose clarity — Surface uses a single dominant casing convention (snake_case). Investigated: sdk 100%, spec 0%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [pass] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 40% (threshold 35% for full credit).
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 1 assessed pages (1 JS-rendered), so answer engines have nothing to cite. Investigated: docs 0%.

### Agent Usability

- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 0%.
- [fail] Idempotency documented — Only 0% of mutating operations (0 of 25) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Httpbin's API contract and discoverability are functional, but the partner onboarding experience is critically underdeveloped — there is no self-service portal, no quickstart, no code samples, and no changelog, meaning partners and their AI agents have no guided path from discovery to a working integration. The two areas demanding immediate attention are Developer Experience (no portal, no examples, incomplete descriptions) and Agent Usability (zero idempotency documentation, no rate-limit signaling), both of which will cause partner integrations to stall or behave unpredictably in production. Prioritize standing up a self-service documentation portal with runnable examples first, then fill the operational reliability gaps that cause agent retry failures.