Example Dummy User API
Community OpenAPI document · agent-readyDeveloper ToolsTesting Qanone1 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Return a placeholder user object with an id and name from a single GET /user endpoint, used for testing tooling and agent integrations.
Use for: I need to fetch a dummy user record for testing, Retrieve a sample user object to validate my JSON parser, Check that my HTTP client handles a minimal 200 response, Get a placeholder user from the dummy API
Not supported: Does not handle authentication, real user data, or production workloads - use for harness testing and rendering fixtures only.
The Dummy User API is a single-endpoint placeholder spec used for testing API tooling, agent harnesses, and catalog rendering pipelines. It exposes one GET /user operation that returns a user object with an integer id and a string name. There is no authentication, no production data, and no real backing service - it exists purely so engineers can validate that their integration code, MCP wiring, or landing-page renderer behaves correctly against a known-shape response.
Install Jentic One Beta
Connect the Dummy User API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dummy User API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fexample.com%2Fexample" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fexample.com%2Fexample" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Dummy User API.
Fetch a placeholder user record with id and name fields via GET /user
Validate that an HTTP client correctly parses a minimal JSON object response
Smoke-test agent harnesses end-to-end without depending on a real vendor
Exercise catalog and landing-page renderers with a deterministic single-endpoint spec
Confirm that MCP tool wiring resolves a no-auth GET request to a 200 JSON response
Use Cases
Patterns agents use Dummy User API for, with concrete tasks.
★ Agent Harness Smoke Test
When integrating a new agent framework or MCP client, engineers need a known-good endpoint that returns a deterministic JSON shape with no authentication. Calling GET /user on the Dummy User API confirms the harness can complete the search-load-execute loop end-to-end and parse a response with the expected id and name fields.
Call GET /user and assert that the response contains an integer id and a string name field
Catalog and Landing-Page Rendering
Catalog renderers and landing-page templates need a minimal, low-risk spec to exercise their code paths. The Dummy User API has exactly one endpoint, no auth, and a tiny response schema, which makes it the ideal fixture for rendering tests, snapshot diffs, and visual regression suites without involving real vendor data.
Render the catalog detail page for example.com/main and verify that the single GET /user endpoint appears with its response schema
JSON Parser Validation
Library authors writing typed clients or response decoders need a stable JSON shape to lock down their parsing behaviour. The Dummy User API returns the same id and name fields every call, so unit tests can assert on the parsed structure without the flakiness of a real third-party API.
Run a typed-client decode against the GET /user response body and assert that id is an int and name is a string
AI Agent Integration Dry-Run via Jentic
When wiring up Jentic for the first time, developers want a no-stakes endpoint to confirm the search, load, and execute loop works before pointing at production APIs. The Dummy User API gives that low-risk target - Jentic search returns the GET /user operation, schema loads cleanly, and execution succeeds without credentials.
Use Jentic search 'fetch a dummy user', load the GET /user schema, and execute the call to confirm the integration path works
Key Endpoints
1 endpoints — the dummy user api is a single-endpoint placeholder spec used for testing api tooling, agent harnesses, and catalog rendering pipelines.
METHOD
PATH
DESCRIPTION
GET
/user
Fetch a placeholder user object
GET
/user
Fetch a placeholder user object
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
The Dummy User API needs no auth and exposes a single read, so wiring it by hand is trivial: it exists to exercise the search-load-execute loop. Through Jentic you install once, import the Dummy User API from the API Directory, and your agent calls it with nothing to store.
Permission scoping
The Dummy User API exposes only a single GET /user read with no path or body target, so scope the agent to that one operation. It is the whole allowed set, and there is nothing destructive to leave out.
Credential isolation
The Dummy User API needs no credentials, so there is nothing for your Jentic One instance to store or inject. No secret ever enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'fetch a dummy user', and Jentic returns the GET /user operation with its response schema so the agent confirms the search-load-execute loop without any real vendor credentials.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Dummy User API through Jentic.
What authentication does the Dummy User API use?
None. The single GET /user endpoint is unauthenticated by design - it exists as a fixture for testing harnesses where credentials would only get in the way.
Can I get production user data from the Dummy User API?
No. The endpoint returns a placeholder object with only id and name fields, intended for fixture and harness testing, not real user lookups.
What are the rate limits for the Dummy User API?
The OpenAPI spec does not declare any rate limits, and there is no SLA or guaranteed availability - treat the endpoint as a best-effort test fixture.
How do I call the Dummy User API through Jentic?
Run pip install jentic, then await client.search('fetch a dummy user'), client.load, client.execute. Jentic returns GET /user with no auth required, which is useful for verifying the Jentic integration loop end-to-end.
What fields does the GET /user response contain?
The response is a JSON object with two fields: id (integer) and name (string). No nested objects, arrays, or pagination - that simplicity is the point.
Can I limit what my agent is allowed to do with the Dummy User API?
Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use. The Dummy User API exposes only a single GET /user read with no path or body target, so you scope the agent to that one operation, which is the whole allowed set. Since the endpoint needs no credentials and does nothing destructive, there is nothing sensitive to withhold.
GET STARTED