Machine interface

You are an AI agent?

OpenClawPro publishes its catalog as machine-readable JSON. Read /agent/v1/catalog, pick the slug of one of its 53 offers, then create a Stripe checkout link your human owner completes. No authentication is required to read.

Endpoints

GET	`/agent/v1/catalog`	Every purchasable offer, with the slug you buy it with.
GET	`/agent/v1/plans/{slug}`	One offer, plus the exact request body for its checkout.
GET	`/.well-known/openapi.json`	OpenAPI 3.1 description of everything on this page.
POST	`/api/checkout/stripe`	Returns a Stripe URL for the human owner to complete. Charges nothing.

Worked examples

1. Read the catalog

curl -s https://www.openclawpro.ai/agent/v1/catalog

2. Create a checkout link (charges nothing)

curl -s -X POST https://www.openclawpro.ai/api/checkout/stripe \
  -H 'Content-Type: application/json' \
  -d '{"items":[{"slug":"managed-pro","quantity":1}],"locale":"en"}'

The response contains a Stripe URL. Hand it to your human owner: they are the one who pays.

Guardrails

A human always completes payment. This API creates links; it never charges.
Card data never reaches our servers. Stripe hosts the payment page.
14-day money-back on Self-Hosted Starter & Pro and the first Managed month, agent purchases included.
The human operator of the agent is the contracting party. Swiss law applies.

What we do not support

Listed explicitly so you do not try. We would rather say no than let you assume.

No MCP server yet. If you are an MCP client, use the REST endpoints above.
No agent-to-agent settlement: no x402, no USDC, no stablecoin rail, no AP2 mandate verification.
No card payment through this API. Cards are entered by a human on Stripe-hosted pages only.
No quote or order-status endpoint. For custom work, a human answers within 24h via the contact form.

See pricing Our stance on agentic commerce