Ownrecord documentation
Ownrecord lets software and AI companies sell worldwide in their own name, with correct tax, invoices, subscriptions and filings.
Ownrecord is software for being your own merchant of record. You sell digital products and services worldwide in your own name, and Ownrecord charges the right indirect tax (VAT, GST and US sales tax), issues compliant invoices, runs subscriptions, keeps a real-time double-entry ledger and tracks your tax registrations in every jurisdiction.
Software, not a merchant of record
A merchant of record is the company that legally sells to your customers. With a platform merchant of record, that company is the platform. With Ownrecord, it's you:
- Your legal entity is the seller everywhere. Checkout, receipts, invoices, the customer portal and emails say "Sold by" your legal name, address and VAT ID.
- Payments go through your own payment processor account. Ownrecord never creates charges on its own account for your sales, never receives or holds your funds, and never pays out.
- Invoices use your name and your numbering, under your tax registrations.
- Your terms apply. Checkout links your own terms and privacy policy. Ownrecord's terms cover only your use of the software.
- Your product delivers your service. Entitlements and webhooks tell your product what a customer has paid for; your product enforces it.
Being your own seller means you take on what a platform merchant of record would otherwise carry: tax registrations, tax liability and chargebacks. Ownrecord tells you when a registration is needed, by when, and what to prepare, and turns each obligation into a task that a person or an authorized agent completes.
Tax rules are a tool, not advice
You're responsible for your tax compliance and registrations. Tax rules maintained by Ownrecord come with their sources and the date they were last verified, so you can check them.
Built for people and agents
Everything you can do in the console you can also do through the API and the MCP server. Each capability is one operation with one permission, one risk tier and one audit trail, whether a person or an AI agent calls it. Agents work under scoped credentials, approval policies and limits; see Building an agent on Ownrecord.
How these docs are organized
- Concepts: The ideas behind Ownrecord's data model and rules. Read these before you integrate.
- Guides: Step-by-step guides for building on Ownrecord.
- API reference: The Ownrecord REST API: conventions, every operation, error codes and event types, generated from the operation registry.
- MCP reference: Every Ownrecord MCP tool, generated from the operation registry: arguments, annotations, dry runs, idempotency and errors.
Terms such as regime, reverse charge and livemode are explained on the concept page where they first matter.
Docs for machines
- Every page is also available as plain markdown: add
.mdto its URL, for example /docs/concepts/ledger.md. - /llms.txt lists every page with a one-line summary, in the llms.txt format.
- /llms-full.txt contains the whole documentation in one file.
Ownrecord is being built in stages, and these docs grow with it. Reference pages for the API, the MCP server, events and error codes are added as each part ships.