Discover the catalog
GET /api/catalog returns the machine-readable service list with prices, units, and delivery modes. Agents must read /llms.txt and /.well-known/agent.md first.
For AI agents
Services for the machine economy — ordered, paid, verified.
Quindart is building the private execution network where agents discover services, bind payment, receive work, and verify the result. Start with the catalog; finish with a signed receipt.
Read the agent policy first — it is short and binding.
The flow
Discover, order, pay, verify.
Four steps, one contract, receipts you can trust without an account.
Authenticate (optional)
Humans can browse and pay without a key. Agents with a Quindart API key (Authorization: Bearer quindart_…) get 201 with the order; unauthenticated requests receive HTTP 402 with a hosted Checkout URL for the human buyer.
Order
POST /api/orders starts a RAILS-aligned lifecycle: negotiation → binding → execution → evidence → verification → settlement → finality. Payment binds the obligation via Stripe.
Verify
GET /api/orders/:id/receipt returns a WebCrypto-signed receipt at finality. Anyone can verify it with POST /api/orders/:id/receipt — no account needed.
Quick start
Three endpoints to understand Quindart.
curl https://quindart.com/api/catalog
curl -X POST https://quindart.com/api/orders \
-H 'content-type: application/json' \
-d '{"serviceSlug":"workflow-audit-focused","name":"Example Corp","email":"ops@example.com"}'
# → 402 (no key) with { order, checkout_url }
# → 201 with { order } for Bearer quindart_… key holders
curl https://quindart.com/api/orders/:id # status
curl https://quindart.com/api/orders/:id/receipt # signed receipt at finalityRules
What to know first.
Can an agent really buy without a human?
Humans pay through Stripe Checkout today. Agent-only rail payments (x402/MPP) are next on the roadmap; the 402 contract is already in place so a key-carrying agent always receives a checkout link to hand back to its user.
What are the binding rules?
Read /.well-known/agent.md before calling anything. Never invent prices, turnaround times, or guarantees. Quote-based services return a 409 — they require a human scope conversation before payment.
How do I verify a receipt?
POST the receipt JSON plus the signature to /api/orders/:id/receipt. The signature is an HMAC over the canonical receipt payload with the Quindart receipt secret; verification returns { valid: true }.
How do I get an API key?
Keys are issued to verified operators today (dashboard or by contacting contact@quindart.com). A public self-serve developer portal is planned with paid plan tiers.