ReqRes
ReqRes (reqres.in) is a hosted REST API originally launched by Ben Howdle as a free no-auth fake-API surface for AJAX prototyping, tutorials, and frontend testing. As of the 2025 relaunch it operates as a freemium SaaS product: every request to /api/* and /app/* now requires an x-api-key header obtained via free signup at app.reqres.in, while the /agent/v1/* Agent Sandbox is open in v1 with IP-based rate limiting. The legacy demo surface (/api/users, /api/login, /api/register, /api/unknown, delayed responses) continues to return the same fixture payloads it always has — what changed is the API-key gate and the addition of persistent collections, app users, custom endpoints, and an agent-targeted sandbox with deliberate failure scenarios. ReqRes remains the default fake-API endpoint cited in countless React, Vue, Angular, and bootcamp tutorials.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles ReqRes the way a machine reads it — 160 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — ReqRes scores 58.2/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile ReqRes
Each block below is one kind of artifact we hold for ReqRes. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
ReqRes Agent Sandbox API
Endpoints designed for AI coding agents. Cursor pagination, deeply nested resources, deliberate error scenarios, deterministic seeded fixtures.
ReqRes App Users API
The App Users API from ReqRes — 13 operation(s) for app users.
ReqRes Authentication API
The Authentication API from ReqRes — 3 operation(s) for authentication.
ReqRes Collections API
The Collections API from ReqRes — 4 operation(s) for collections.
ReqRes Custom Endpoints API
The Custom Endpoints API from ReqRes — 1 operation(s) for custom endpoints.
ReqRes Legacy API
The Legacy API from ReqRes — 4 operation(s) for legacy.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
ReqRes API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Reqres Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Reqres Rate Limits
RATE LIMITSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Legacy Demo Fixtures
Stable /api/users, /api/users/{id}, /api/unknown, /api/unknown/{id} fixture data preserved from the original reqres.in launch — the same payloads tutorials have been wired again...
Simulated Auth Flows
/api/register, /api/login, and /api/logout return success-shaped tokens without creating real accounts — drop-in for teaching auth patterns without standing up a real identity p...
Persistent Collections
/api/collections/{slug}/records supports GET/POST/PUT/DELETE with real persistence on paid plans, with custom schemas on the Dev tier and above.
Project-Scoped App Users
/app/* surface lets each app user authenticate independently with a session bearer, so client-side prototypes can model real per-user isolation.
Custom Endpoints
/api/custom/{path} executes user-defined endpoints, letting builders shape arbitrary REST surfaces without writing backend code.
Agent Sandbox
/agent/v1/* exposes endpoints designed for AI coding agents — cursor pagination, deeply nested resources, deliberate failure scenarios, and deterministic seeded fixtures.
15 Deliberate Failure Scenarios
The Agent Developer plan unlocks 15 failure scenarios on /agent/v1/scenarios so AI agents can be tested against timeouts, rate limits, validation errors, and pagination edge cases.
Delayed Responses
Legacy endpoints accept a ?delay=N query param to simulate slow upstream conditions — useful for spinner/loading-state testing.
HTTPS Only
Served exclusively over HTTPS at reqres.in.
CORS Enabled
All origins are allowed, making ReqRes safe to call directly from browser-based prototypes.
Scroll within the panel for all 10 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Reqres Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
ReqRes API Rules
SPECTRALReqRes API Rules
SPECTRALJSON Schema 40
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AgentHealthResponse
JSON SCHEMAAgentMoney
JSON SCHEMAAgentPaginationMeta
JSON SCHEMAAgentUserDetailResponse
JSON SCHEMAAgentUserListResponse
JSON SCHEMAAgentUser
JSON SCHEMAAppUserCreateRequest
JSON SCHEMAAppUserListResponse
JSON SCHEMAAppUserLoginRequest
JSON SCHEMAAppUserLoginResponse
JSON SCHEMAAppUserResponse
JSON SCHEMAAppUser
JSON SCHEMAAppUserSessionResponse
JSON SCHEMAAppUserTotalResponse
JSON SCHEMAAppUserUpdateRequest
JSON SCHEMAAppUserVerifyRequest
JSON SCHEMAAppUserVerifyResponse
JSON SCHEMAAuthRequest
JSON SCHEMACollectionCreateRequest
JSON SCHEMACollectionListResponse
JSON SCHEMACollectionRecordCreateRequest
JSON SCHEMACollectionRecordListResponse
JSON SCHEMACollectionRecordResponse
JSON SCHEMACollectionRecord
JSON SCHEMACollectionRecordUpdateRequest
JSON SCHEMACollectionResponse
JSON SCHEMACollection
JSON SCHEMACollectionUpdateRequest
JSON SCHEMALegacyMutationRequest
JSON SCHEMALegacyMutationResponse
JSON SCHEMALegacyUnknownListResponse
JSON SCHEMALegacyUnknownResponse
JSON SCHEMALegacyUnknown
JSON SCHEMALegacyUserListResponse
JSON SCHEMALegacyUserResponse
JSON SCHEMALegacyUser
JSON SCHEMALoginResponse
JSON SCHEMARegisterResponse
JSON SCHEMATemplate
JSON SCHEMATemplatesResponse
JSON SCHEMAScroll within the panel for all 40 ·
JSON Structure 40
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Reqres Agent Health Response Structure
JSON STRUCTUREReqres Agent Money Structure
JSON STRUCTUREReqres Agent Pagination Meta Structure
JSON STRUCTUREReqres Agent User Detail Response Structure
JSON STRUCTUREReqres Agent User List Response Structure
JSON STRUCTUREReqres Agent User Structure
JSON STRUCTUREReqres App User Create Request Structure
JSON STRUCTUREReqres App User List Response Structure
JSON STRUCTUREReqres App User Login Request Structure
JSON STRUCTUREReqres App User Login Response Structure
JSON STRUCTUREReqres App User Response Structure
JSON STRUCTUREReqres App User Session Response Structure
JSON STRUCTUREReqres App User Structure
JSON STRUCTUREReqres App User Total Response Structure
JSON STRUCTUREReqres App User Update Request Structure
JSON STRUCTUREReqres App User Verify Request Structure
JSON STRUCTUREReqres App User Verify Response Structure
JSON STRUCTUREReqres Auth Request Structure
JSON STRUCTUREReqres Collection Create Request Structure
JSON STRUCTUREReqres Collection List Response Structure
JSON STRUCTUREReqres Collection Record Create Request Structure
JSON STRUCTUREReqres Collection Record List Response Structure
JSON STRUCTUREReqres Collection Record Response Structure
JSON STRUCTUREReqres Collection Record Structure
JSON STRUCTUREReqres Collection Record Update Request Structure
JSON STRUCTUREReqres Collection Response Structure
JSON STRUCTUREReqres Collection Structure
JSON STRUCTUREReqres Collection Update Request Structure
JSON STRUCTUREReqres Legacy Mutation Request Structure
JSON STRUCTUREReqres Legacy Mutation Response Structure
JSON STRUCTUREReqres Legacy Unknown List Response Structure
JSON STRUCTUREReqres Legacy Unknown Response Structure
JSON STRUCTUREReqres Legacy Unknown Structure
JSON STRUCTUREReqres Legacy User List Response Structure
JSON STRUCTUREReqres Legacy User Response Structure
JSON STRUCTUREReqres Legacy User Structure
JSON STRUCTUREReqres Login Response Structure
JSON STRUCTUREReqres Register Response Structure
JSON STRUCTUREReqres Template Structure
JSON STRUCTUREReqres Templates Response Structure
JSON STRUCTUREScroll within the panel for all 40 ·
Examples 40
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Reqres Agent Money Example
EXAMPLEReqres Agent User Example
EXAMPLEReqres App User Example
EXAMPLEReqres Auth Request Example
EXAMPLEReqres Collection Example
EXAMPLEReqres Legacy User Example
EXAMPLEReqres Template Example
EXAMPLEScroll within the panel for all 40 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 7
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Frontend Tutorial Endpoints
The default fake API cited in React, Vue, Angular, and Svelte tutorials when an author needs a real HTTP endpoint without standing up a backend.
Bootcamp Curriculum
Coding bootcamps wire exercises against ReqRes legacy endpoints so students can practice CRUD flows on a stable, free, no-signup surface.
API Client Test Suites
Use the legacy and Collections surfaces to exercise HTTP client libraries (fetch, axios, requests, OkHttp) against a real REST API.
Frontend-First Prototyping
Build a UI against persistent ReqRes collections before standing up a real backend; swap in a real API later by renaming the base URL.
AI Agent Testing
Test AI coding agents against the /agent/v1/* sandbox — cursor pagination, deliberate failures, deterministic seeded fixtures.
Sales Demos
Power live sales demos for tools that need to talk to an API without exposing customer data.
Workshop Sandboxes
Hands-on workshops where every participant needs a working API endpoint in under a minute.
Scroll within the panel for all 7 ·
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Postman
Public Postman collections wrap ReqRes endpoints for quick HTTP exploration and learning.
Hoppscotch
Frequently used as the default example endpoint in HTTP clients including Hoppscotch and Insomnia.
MSW (Mock Service Worker)
Often paired with MSW so frontend tests can intercept and stub ReqRes traffic deterministically.
Claude Code / AI Coding Agents
The /agent/v1/* sandbox is purpose-built for AI coding agents like Claude Code, with deliberate failure scenarios and cursor pagination.
Cypress / Playwright
Browser E2E test suites use ReqRes as a stable upstream when writing tests that depend on real network traffic.
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Self-Hosted Deployment
From $499/year per team, deploy ReqRes inside your own infrastructure with no external dependencies — useful for regulated environments that can't call a public service.
Scoped Per-Engineer API Keys
On the Team plan, issue scoped API keys per engineer with usage tracking, so a single project can attribute spend back to individuals.
Webhook Automations
On the Pro plan, configure webhooks that fire on collection data changes, letting ReqRes drive downstream pipelines as a prototyping backend.
Resources
Every other property we hold for ReqRes — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/reqres · machine-readable index on apis.io