JSONPlaceholder
JSONPlaceholder is a free, no-auth fake REST API for prototyping, tutorials, and testing. It exposes six relational resources — posts, comments, albums, photos, todos, and users — over six standard REST routes per resource. All write operations (POST, PUT, PATCH, DELETE) are accepted and respond as if successful, but no changes are persisted. The service is built on the open-source json-server engine (also by typicode) and serves billions of requests per month with no rate limits or authentication.
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 JSONPlaceholder the way a machine reads it — 53 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 — JSONPlaceholder scores 48.4/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). 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 JSONPlaceholder
Each block below is one kind of artifact we hold for JSONPlaceholder. 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.
JSONPlaceholder Albums API
100 sample photo albums owned by users
JSONPlaceholder Comments API
500 sample comments belonging to posts
JSONPlaceholder Photos API
5000 sample photos belonging to albums
JSONPlaceholder Posts API
100 sample blog posts owned by users
JSONPlaceholder Todos API
200 sample todo items owned by users
JSONPlaceholder Users API
10 sample users with profile, address, and company metadata
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).
JSONPlaceholder REST 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.
Rate 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.
Jsonplaceholder Rate Limits
RATE LIMITSFeatures 8
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.
Six Relational Resources
Posts, comments, albums, photos, todos, and users with realistic relationships between them (posts belong to users, comments belong to posts, etc.).
Full REST Surface
GET, POST, PUT, PATCH, and DELETE methods are accepted on every resource — write operations simulate success without persisting changes.
Nested Routes
Single-level nested access such as /posts/1/comments, /albums/1/photos, and /users/1/todos for relational queries.
Query Filtering
Basic query-string filtering on any resource field (e.g. /comments?postId=1, /posts?userId=1).
No Authentication
Open to the public — no API keys, OAuth, or signup required. Use it in tutorials, sandboxes, and frontend demos freely.
No Rate Limits
The service does not publish or enforce documented rate limits and routinely serves about three billion requests per month.
CORS Enabled
All origins are allowed, making the service usable directly from browser-based applications without a proxy.
HTTPS Only
Served exclusively over HTTPS for safe inclusion in modern web tutorials and demos.
Scroll within the panel for all 8 ·
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.
Jsonplaceholder 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.
JSONPlaceholder API Rules
SPECTRALJSONPlaceholder API Rules
SPECTRALJSON Schema 6
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.
JSON Structure 6
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.
Jsonplaceholder Album Structure
JSON STRUCTUREJsonplaceholder Comment Structure
JSON STRUCTUREJsonplaceholder Photo Structure
JSON STRUCTUREJsonplaceholder Post Structure
JSON STRUCTUREJsonplaceholder Todo Structure
JSON STRUCTUREJsonplaceholder User Structure
JSON STRUCTUREExamples 6
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.
Jsonplaceholder Post Example
EXAMPLEJsonplaceholder Todo Example
EXAMPLEJsonplaceholder User Example
EXAMPLESecurity Posture 1
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 6
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 Prototyping
Wire up React, Vue, Angular, or Svelte tutorials against a real HTTP endpoint without standing up a backend.
API Client Testing
Exercise HTTP client libraries (fetch, axios, requests, OkHttp) against a stable public REST surface.
Tutorial and Courseware
Power coding tutorials, bootcamp exercises, and conference workshops that need a deterministic JSON API.
Mobile App Demos
Drive iOS and Android sample apps that demonstrate networking, list rendering, and CRUD flows.
Tooling QA
Smoke-test API generators, codegen tools, SDK builders, and OpenAPI tooling against a stable real-world API.
Workshop Sandboxes
Provide a no-signup HTTP API for hands-on workshops where participants cannot wait for credentials.
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.
json-server
The open-source engine that powers JSONPlaceholder — runs the same fake REST API locally with a single command.
lowdb
The tiny local JSON database that json-server uses for storage; ships from the same typicode org.
Postman
Public collections wrap JSONPlaceholder 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 JSONPlaceholder traffic deterministically.
Solutions 2
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Local Mirror via json-server
For teams that need write persistence or offline development, install json-server, point it at a local db.json, and reproduce JSONPlaceholder routes verbatim.
My JSON Server
typicode operates an additional service (My JSON Server) that turns any GitHub-hosted db.json into a personal hosted fake REST API.
Resources
Every other property we hold for JSONPlaceholder — 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 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/jsonplaceholder · machine-readable index on apis.io