Prood docs
The keys to your store.
How to open a store on Prood, take payments through your own accounts and build on the API. Written for merchants, agencies, developers and AI agents.
Stock photographs. Not Prood customers.
Start here
Pick your way in.
Four kinds of people use Prood. Each has a short path through these docs.
Merchants
Open a store, add your products, connect a payment account and go live on your own domain.
Agencies
Build and run client stores, each with its own data, payment accounts and domain.
Developers
Build on the API the dashboard uses, with an OpenAPI 3.1 spec and a typed client.
AI agents
With Agent Auth, an AI agent starts with nothing until you approve it for your store. Agent Auth starts on Grow. Paid plans are coming.
Stock photographs. Not Prood customers.
Quick start
Call the API in three steps.
Create a store
Register on the dashboard. Every plan includes a prood.app address and a key for the public storefront API.
Make an API key
Open API keys in the dashboard. The key belongs to your organization and is shown once.
Call the API
Send the key in the x-api-key header. Free API keys reach the public storefront API: catalog, carts and placing orders. Reading your orders and customers by API, and all admin writes, start on Grow.
# Check the keycurl https://api.prood.com/v1/me \ -H "x-api-key: $PROOD_API_KEY"{ "organizationId": "org_abc123", "scopes": ["storefront"], "via": "api-key" }# List the store's productscurl https://api.prood.com/v1/products \ -H "x-api-key: $PROOD_API_KEY"Reference
Look something up.
- REST APIEvery operation under /v1, with schemas and a request console.
- MCP serverTools that mirror the REST API, for any MCP-compatible client.
- prood CLICheck a key, list products, and print MCP client config. Available from the source repo for now.
- PaymentsStripe, Easypay and Ifthenpay, connected per store.
- WebhooksPoint your provider's notifications at Prood, so orders are marked paid.
- Plans and limitsWhat each plan includes and where the limits apply.