Skip to content

For developers and AI agents

Commerceyou can call.

Nothing to deploy. Prood runs the commerce engine, and /v1 is the API the dashboard is built on. Free keys reach catalog, carts and placing orders. Admin access starts on Grow. Multibanco and MB WAY are already at hosted checkout, through Easypay or Ifthenpay.

Example key

Storefront

x-api-key: pkAbC123...

Build

Four ways into the same store.

One data model, whichever you pick. What you can do depends on the key or grant you hold.

  • REST API

    More than 40 operations under /v1 for catalog, carts, orders, customers and store settings.

    Read the endpoints
  • OpenAPI and TypeScript

    An OpenAPI 3.1 spec at /v1/openapi.json. The typed client, @prood/api-client, is generated from it. Available from the source repo for now.

    Read about the API client
  • prood CLI

    Check who you're signed in as, list products, and print MCP client config. @prood/cli is available from the source repo for now.

    Read about machine access
  • MCP server

    41 tools at /mcp that mirror the REST API, for any MCP-compatible client. Free keys reach the 21 storefront tools. 18 do useful work today: the MCP docs list the three that don't.

    Read the MCP docs
zsh
# Check a key with Storefrontprood auth whoami --json \  --api-url https://api.prood.com/v1# Create a product (Grow and above)curl -X POST \  https://api.prood.com/v1/admin/products \  -H "x-api-key: $PROOD_API_KEY" \  -H "content-type: application/json" \  -d @linen-tote.json # Point an MCP client at the storeprood mcp config \  --api-url https://api.prood.com/v1 

Keys

A key reaches what its scopes say.

Choose Storefront, Admin or both when you make a key. Payment accounts, domains, team and keys stay in the dashboard. Paid plans can't be bought yet, so every key today is a Storefront key. Want to know when admin access opens? Email us.

Key ledger

Example keys

  • WebsiteEvery planpkAbC123...storefront
  • Stock syncFrom GrowpkDeF456...admin
  • Back officeFrom GrowpkGhI789...storefront, admin
Example: three keys, one with the storefront scope, one with the admin scope and one with both.
  • Storefront

    Every plan

    The public storefront API: catalog, carts and placing orders.

    Example calls

    • GET /v1/products
    • POST /v1/carts
  • Admin

    From Grow

    Reading your orders and customers by API, and all admin writes. A key with only Admin can't call the storefront routes, such as /v1/products and carts. It reads products through /v1/admin/products.

    Example calls

    • GET /v1/admin/orders
    • POST /v1/admin/products
  • Both scopes

    From Grow

    Catalog, carts, your orders and customers, and changes to the store, on one key.

    Example calls

    • GET /v1/products
    • PATCH /v1/admin/products/{id}

Access

With Agent Auth, agents ask you.

With Agent Auth, an AI agent starts with nothing until you approve it for your store.

After that it keeps the public catalog, and anything else needs your approval. You see every capability the agent asks for and approve or deny the request as a whole. Approved access ends after an hour idle, or 24 hours at most. Then the agent asks again.

An API key isn't Agent Auth: anything holding an admin key can do what the key allows, without asking. Agent Auth is coming with Grow.

An AI agent asks to change your store

Asks for
adminListOrders
adminRefundOrder
Lasts
1 hour idle, 24 at most

Sample approval

What each kind of key or grant can reach
Public catalogCarts and placing ordersRead orders and customersChange the store
Free API key
Key with both scopes, from Grow
Agent Auth, from GrowAfter you approveAsks youAsks youAsks you

Payment runs on hosted checkout, started from your store. 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. Each store's payment credentials are stored separately and encrypted at rest with AES-256-GCM. The ticks in the second row need both scopes: a key with only Admin doesn't reach the catalog or carts columns. Agents discover the API at /.well-known/agent-configuration.

Get an API key in minutes.

Create a free store, open API keys and make one. Free keys reach the public storefront API.

By key

MCP tools each one reaches

Storefront, on Free
21 tools
Admin, from Grow
20 tools
Both scopes
41 tools