Developer docs
Sollection Docs
Sollection is an invoice creation and payment layer for AI assistants, agents, and humans. It turns an AI-written invoice draft into a payable Solana invoice, but only after the recipient wallet signs. These pages mark which side of that signature every endpoint sits on.
Start here
- OverviewThe three Sollection layers: AI assistants prepare invoice intents, a recipient wallet approves invoice creation, and only then is the invoice payable.
- QuickstartDecision tables for picking the right Sollection flow and the right integration path for your use case.
- AI invoicesHow ChatGPT, Claude, Gemini, Cursor and other assistants draft invoice intents, and the safety rules that apply to them.
Invoice flow
- Invoice intentsThe draft invoice object: required fields, supported tokens, implemented statuses, and why an unsigned intent has no payable links.
- Wallet approvalThe hosted signing page, what the approval message contains, and why signing approves invoice creation without transferring funds.
- Final invoicesThe payable invoice object, its payUrl, x402Url and statusUrl links, and the invoice lifecycle statuses.
- x402 paymentsHow an agent pays a final Sollection invoice over HTTP 402: the discover-and-settle flow, X-PAYMENT headers, and on-chain confirmation.
Integration
- REST APISollection API categories: AI-safe action endpoints, internal wallet endpoints, merchant/account endpoints, and payment endpoints.
- OpenAPI schemasThe action-safe schema at /.well-known/openapi.json and the full merchant/developer schema, and when to use each.
- AI assistant rulesThe published llms.txt discovery file and the AI usage contract: what assistants may and must not do with Sollection invoices.
- IntegrationsCapability matrix for Claude, Cursor, LangChain, LlamaIndex, n8n, custom backend agents, and the human dashboard.
- MCP assistantsConnect MCP clients to the hosted Sollection MCP endpoint and use its three tools: create_invoice_intent, get_invoice_intent, get_invoice_status.
- Backend agentsCall the Sollection REST API directly from LangChain, LlamaIndex, custom Node.js/Python agents, or n8n HTTP workflows.
Operations
- Security modelWhy Sollection is non-custodial, what each signature authorizes, and how action keys differ from merchant API keys.
- ErrorsThe assistant-safe error envelope, the assistantHint field, and the implemented assistant-facing error codes.
- WebhooksSigned invoice.sent and invoice.paid deliveries for merchant accounts, and why webhooks sit outside the action-safe AI schema.
- Payment linksThe legacy/account-only payment-link endpoint, why it is immediately payable, and why it is excluded from the AI action schema.