Dummy Products API
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsTesting Qanone20 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
A free, no-auth fake e-commerce API for prototyping agent flows. Provides realistic CRUD over products, users, carts, and reviews for demos and tests.
Use for: I need a fake e-commerce API to demo my agent, List sample products for a tutorial, Create a test user without setting up authentication, Walk through a cart-checkout flow for a demo
Not supported: Does not handle real payments, real inventory, or production traffic - use for prototyping, demos, and CI tests only.
Jentic publishes the only available OpenAPI specification for Dummy Products API, keeping it validated and agent-ready. Dummy Products is a free fake e-commerce REST API used for prototyping, demos, and integration testing without standing up a real backend. The API exposes 20 endpoints providing full CRUD over products, users, carts, and reviews with realistic test data. No authentication is required, which makes it convenient for tutorials, agent dry-runs, and CI smoke tests.
Install Jentic One Beta
Connect the Dummy Products API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dummy Products 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%2Fdummyproducts-api.herokuapp.com%2Fdummyproducts-api" | 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%2Fdummyproducts-api.herokuapp.com%2Fdummyproducts-api" | 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 Products API.
Read sample product data via GET /products and GET /products/{id}
Exercise creation flows via POST /products, POST /users, POST /carts, and POST /reviews
Test update logic via PUT /products/{id}, PUT /users/{id}, PUT /carts/{id}, and PUT /reviews/{id}
Validate delete handling via DELETE on the same four resources
Wire end-to-end agent demos without provisioning a real e-commerce backend
Run CI smoke tests against a stable, no-auth public surface
Use Cases
Patterns agents use Dummy Products API for, with concrete tasks.
★ Agent Demo Without a Real Backend
Show off a shopping or commerce agent end-to-end without standing up a real e-commerce backend. The agent calls GET /products to populate the catalog, POST /carts to add items, and POST /reviews to leave feedback, all against a public no-auth surface. This is ideal for sales demos, conference talks, and onboarding tutorials.
GET /products to list, POST /carts with two product IDs, GET /carts/{id} to confirm contents, then POST /reviews for one of the products
CI Smoke Test for an HTTP Client
Validate an HTTP client library or agent runtime against a stable public REST API in CI. The Dummy Products API exposes predictable JSON responses on /products and /users with no auth, so tests can assert request shaping, JSON parsing, and error handling without managing API keys. Suitable for SDK regression suites and adapter integration tests.
In CI, GET /products and assert a 200 response with a JSON array, then POST /users with a fixture body and assert a 201 response
Agent Tutorial Content via Jentic
Teach Jentic's search-load-execute flow against a no-auth API where readers do not need to register. The agent searches Jentic, loads the schema for POST /carts, and executes a real call against the Dummy Products surface. Because no key is required, tutorials are reproducible by every reader, which lowers the barrier to first successful agent execution.
Search Jentic for 'create a shopping cart', load the schema for POST /carts, and execute with two product IDs sourced from GET /products
Key Endpoints
20 endpoints — jentic publishes the only available openapi specification for dummy products api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/products
List all products
POST
/products
Create a product
GET
/products/{id}
Get a product by ID
POST
/users
Create a user
POST
/carts
Create a shopping cart
POST
/reviews
Create a product review
GET
/products
List all products
POST
/products
Create a product
GET
/products/{id}
Get a product by ID
POST
/users
Create a user
POST
/carts
Create a shopping cart
POST
/reviews
Create a product review
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
The Dummy Products API needs no auth, but wiring it still means building each product, cart, and review call and its request bodies yourself. Through Jentic you install once, import Dummy Products from the API Directory, and your agent calls it through the same execution path you will use later for an authenticated production API.
Permission scoping
Dummy Products takes its inputs in the request body, so you limit the agent to the operations it needs, such as listing products or creating a test cart. You choose which operations are allowed, so creating users or reviews is not included unless you add them.
Credential isolation
The Dummy Products API requires no credentials, so there is nothing to store. Jentic still routes the call through your own Jentic One instance so the same code path works when you later switch to an authenticated production API.
Intent-based discovery
Agents search Jentic by intent such as 'create a test cart' or 'list sample products', and Jentic returns the matching Dummy Products operation with its input schema so the agent calls the right endpoint without browsing the docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Dummy Products API through Jentic.
Why is there no official OpenAPI spec for Dummy Products API?
The Dummy Products project does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Dummy Products API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Dummy Products API use?
None. The API is intentionally open so it can be used in tutorials, demos, and CI without setting up keys. Through Jentic the same call is wrapped behind the standard execute flow.
Can I create products and carts with the Dummy Products API?
Yes. POST /products, POST /users, POST /carts, and POST /reviews all return created records, and PUT and DELETE work on the same resources by ID.
What are the rate limits for the Dummy Products API?
The OpenAPI spec does not declare rate limits. The service is hosted on a free Heroku tier so expect cold-start latency and informal throttling; use it for demos and tests rather than load benchmarks.
How do I prototype a shopping agent through Jentic?
Search Jentic for 'create a shopping cart', load the schema for POST /carts, and execute against /api/v1. Install with pip install jentic and chain with GET /products to populate the cart.
Is the Dummy Products API safe for production use?
No. Data is shared and may reset, the host is a free tier, and there is no SLA. Use it for prototyping, demos, and tests; switch to a real e-commerce API for production traffic.
Can I limit what my agent is allowed to do with the Dummy Products API?
Yes. Because you self-host Jentic One, your own rules decide which Dummy Products operations the agent may call, so you can allow only what a task needs, such as listing products with GET /products or creating a test cart with POST /carts. Write operations like POST /users and POST /reviews stay off limits unless you explicitly add them. The Dummy Products API takes its inputs in the request body and needs no credentials, so scoping is purely a matter of which operations you permit.
GET STARTED