canonical: https://jentic.com/apis/fakejson.com/fakejson # FakeJSON API FakeJSON generates synthetic JSON test data on demand from a schema-style request body. The two endpoints handle a single-document request at /q and a batched request at `/q/batch`, both authenticated by an API token included in the request body. It is a small but focused tool for filling staging environments, demoing UIs, and running load tests without touching real production data. ## For AI agents Generate synthetic JSON test data from a schema specification, either one document at a time or in batches. Useful for seeding test environments and demo fixtures. ## Scope Does not validate schemas, store generated data, or anonymise real production data - use for synthetic JSON generation from a schema only. ## Capabilities - Generate a single fake JSON document from a schema specification - Generate a batch of fake JSON documents in one request - Seed a staging or demo environment with synthetic records - Produce structured fixtures for UI prototypes without real user data - Simulate API responses for offline development and testing ## Use cases ### Staging Environment Seeding A QA engineer needs to populate a staging database with realistic-looking but synthetic records before running a smoke test. The agent calls `/q/batch` with a schema describing user, order, or product objects and writes the response into the staging store. The whole seeding run is one API call regardless of batch size. Example prompt: POST a batch schema describing 100 user records with name, email, and address fields to `/q/batch` and write the returned array to the staging users table. ### UI Prototype Fixtures A frontend developer building a prototype needs realistic JSON to render lists and cards before the backend exists. The agent calls /q with a schema matching the UI's expected shape and the response feeds the component as a static fixture. Removes the need to hand-write JSON or scrape sample data from production. Example prompt: POST a single-document schema describing a product card to /q and write the returned JSON to a fixtures file the prototype reads on load. ### AI Agent Test Data Helper An AI agent helping a developer scaffold a new project uses Jentic to generate fixture data without leaving the chat session. Jentic exposes the /q and `/q/batch` operations with their schema parameters, and the agent picks the correct endpoint based on the requested record count. Useful in scaffolding and onboarding flows. Example prompt: Call jentic.search with 'generate fake JSON data', load the `/q/batch` operation, execute it with the developer's schema and a record count of 50, and return the JSON array. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/q` | Generate a single fake JSON document from a schema | | POST | `/q/batch` | Generate a batch of fake JSON documents from a schema | ## Key resources - **Generate** — Single-document and batched generation of fake JSON data from a schema ## Why Jentic - **Setup:** Wiring the FakeJSON API by hand means placing its token inside the request body, targeting the app.fakejson.com host, and choosing between the single and batch generation routes yourself. Through Jentic you install once, import the FakeJSON API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** FakeJSON carries the schema and token in the request body rather than a resource id in the path, so you limit the agent to the operations it needs: generating a single record set with /q or a batch with `/q/batch.` You choose those operations, so the agent only ever generates synthetic data. - **Credential handling:** Your FakeJSON token is stored once, encrypted, by your own Jentic One instance and merged into the outgoing request body at execution time. The token value never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'generate fake JSON data', and Jentic returns the /q and `/q/batch` operations with their schema parameters so the agent picks single or batch based on the requested record count without browsing the reference docs. ## Related APIs - **Mailchimp** — Real production data sink that consumes test records during integration testing - **Shopify** — Production e-commerce API where fake-product fixtures are useful in dev stores - **Segment** — Event ingestion API often loaded with synthetic events during integration testing ## FAQ ### What authentication does the FakeJSON API use? FakeJSON uses an apiKey passed inside the request body as the token field on the JSON payload. Through Jentic the token is stored encrypted in the vault and injected into outgoing /q and `/q/batch` request bodies so the agent never sees the raw value. ### Can I generate a batch of fake records with the FakeJSON API? Yes. POST a schema specification along with the desired record count to `/q/batch.` The endpoint returns the array of generated documents in a single response and is the right choice when you need more than one record. ### What are the rate limits for the FakeJSON API? Rate limits are not declared in the spec. Plans on FakeJSON's pricing page are credit-based per generated record rather than per-second quotas - the token's plan determines monthly throughput. ### How do I generate fake JSON through Jentic? Run pip install jentic, call jentic.search with 'generate fake JSON data', load the /q operation for a single document or `/q/batch` for many, and execute with your schema. The token is replayed from the vault on each call. ### Does FakeJSON return realistic field values? Yes. The schema fields accept type tokens like 'firstName', 'email', and 'address' that produce plausible synthetic values, which is the main reason to use it over hand-written JSON fixtures. ### Is the FakeJSON API free? FakeJSON offers a limited free tier and paid plans for higher record volumes. The original fakejson.com domain has been redirected and the active host is app.fakejson.com - check current plan terms before relying on it for production-scale fixture generation. ### Can I limit what my agent is allowed to do with the FakeJSON API? Yes. Because you run Jentic One yourself, your own rules decide which FakeJSON operations the agent may call and which credentials it may use. FakeJSON only exposes two operations, generating a single document at /q and a batch at `/q/batch`, so you can permit just the one your workflow needs and leave the other off. Since the schema and token travel in the request body rather than a path resource, scoping to those operations means the agent can only ever generate synthetic JSON data and nothing else.