Agentic Commerce
Bitcoin payments, ready for AI agents
Every Zaprite Checkout comes with payment instructions agents can follow, and our API docs are written for LLMs. Let agents pay, sell and reconcile in bitcoin on your behalf.
Pay invoice 0043 from BTC Widgets:
pay.zaprite.com/order/od_8kx2…
Done. Invoice 0043 for $1,250.00 is paid.
Two sides of agentic commerce
Built for agents on both sides of the payment
Whether an agent is paying for something or running your store, Zaprite gives it a clear, documented way to work with bitcoin payments.
For your customers
Agents that pay
Every Zaprite Checkout links to plain-text payment instructions. An agent with access to a Lightning or bitcoin wallet can pay any Checkout its user asks it to, with no integration from you.
- Works on every Checkout automatically
- Lightning first, with on-chain bitcoin as a fallback
- The agent can confirm the Order is paid
For your business
Agents that sell and reconcile
Give an agent a Zaprite API key and our LLM docs, and it can run your payment workflows: create Checkouts and Invoices, charge saved payment methods and keep your books in sync.
- One API for Orders, Contacts, Tickets and Webhooks
- Docs in Markdown and OpenAPI, ready for any LLM
- Read-only keys for agents that only need to look
Agent-ready Checkouts
How an agent pays a Zaprite Checkout
No integration needed. Any Checkout you share, from Invoices to Payment Links, can be paid by an agent in three calls.
- 1
Find the instructions
Every Checkout page links to plain-text payment instructions, so an agent knows what to do without any custom code.
pay.zaprite.com/order/od_…<link rel="alternate" type="text/plain" title="LLM payment instructions" href="/llms.txt" /> - 2
Request a quote
The agent asks for a Lightning or bitcoin quote, which locks in the amount and returns a wallet payment URL.
POST /api/public/checkout/create-quote{ "orderId": "od_8kx2…", "transactionMethod": "LIGHTNING" } → { "method": "LIGHTNING", "paymentUrl": "lightning:lnbc…", "btcAmount": 1012500 } - 3
Pay and confirm
It pays the URL from a compatible wallet, then checks the Order status until it shows as paid.
POST /api/public/checkout/order-status{ "orderId": "od_8kx2…" } → { "status": "PAID", "paidAt": "2026-11-01T09:42:17Z" }
The instructions tell agents to pay only Orders their user explicitly asked them to pay, from a wallet the user or agent controls. Protected Checkouts also need the access token from the checkout link.
Agents for your business
What your agents can do with the Zaprite API
Point an agent at our LLM docs and give it an API key. Each key is scoped to one organization.
Create Checkouts
Spin up an Order for any amount and currency, then hand the customer its checkoutUrl to pay in bitcoin, lightning or fiat.
POST /v1/ordersSend Invoices
Create an Order with invoice line items for an existing Contact, and Zaprite calculates the total and builds the invoice.
POST /v1/orders + invoiceCharge saved payment methods
Pay an Order with a payment profile your customer saved earlier, with an optional receipt email.
POST /v1/orders/chargeIssue Event Tickets
Issue tickets to attendees by email, update ticket stock and record check-in activity.
POST /v1/tickets/issueReconcile payments
List and look up Orders, Contacts and Tickets, and match them to your own records with metadata and your own IDs.
GET /v1/ordersReact to events
Subscribe to webhooks for Order, Invoice, Contact, Ticket and payment profile changes, so agents act the moment something happens.
POST /v1/webhooksBuilt for LLMs
Everything your agent needs
Machine-readable docs, a typed SDK and guardrails to keep agents on a short leash.
API docs for LLMs
The full API reference as plain Markdown, ready to drop into an agent’s context.
api.zaprite.com/llms.txtCheckout instructions
The payment instructions every Checkout links to, for agents that pay.
pay.zaprite.com/llms.txtOpenAPI spec
Generate tool and function definitions for your agent framework.
openapi.jsonTypeScript SDK
Typed request helpers for agents and tools built in Node.js.
@zaprite/apiRead-only keys
Agents that only report or reconcile can use keys limited to GET requests.
Scoped and revocable
Each key belongs to one organization, and you can rotate or revoke it at any time.
Sandbox organizations
Test agent workflows end to end without moving real money.
Ready to get started?
Start your Free Trial today or reach out to our Sales team with any questions.