Build with OpenAccountants.
The public rule bundle and live tools for your AI agent.
Quickstart
There are two ways to start, depending on what you need. Neither takes more than a few minutes.
Try a rule bundle
Every published rule for a jurisdiction is available as a single markdown document from one public endpoint. Read the licence terms before including skill content in a product.
curl https://www.openaccountants.com/api/bundle/malta
That returns every published Malta skill, rates, thresholds, allowances, deadlines, as plain markdown, each figure cited to its source. The {jurisdiction} segment accepts a country name (malta) or an ISO code (MT, GB, DE, US, US-CA, CA-ON). The response carries an X-Skill-Count header, and a jurisdiction with no published skills returns 404. Building a tool? Add ?format=json for a structured pack, and ?version=2026.2 to pin an immutable snapshot, see the HTTP API reference.
Want the index first? /llms.txt is a plain-text quick-reference for AI agents, and /llms-full.txt lists every published skill grouped by jurisdiction, with its quality tier and tax year.
See the full HTTP API reference for the accountant directory and response details.
Give your AI agent live tax tools
For an interactive agent that looks rules up on demand, computes rates, and plans cross-border situations, connect the OpenAccountants MCP server:
- Add the connector from /connect. It works with any MCP-compatible AI agent.
- Eligible read tools allow limited guest use, then require a free account. Contribution and verification require sign-in and the relevant permissions.
- Your agent can now call the tools, starting with
startto scope a request, thensearch_skills/get_skillfor the cited rules andsearch_rulesandget_deadlinesfor figures, sources and dates.
Rate limits are 60 requests/minute per IP and 1,000 requests/day per signed-in account. The complete, always-current tool list is in the MCP tool reference.
Where next
- Skills, facts and review status, authorship, independent checks and what they mean.
- HTTP API reference, the bundle, the accountant directory, and the agent index files.
- MCP tools, currently advertised tools, generated from the server catalogue.
- Power your own calculator, a worked guide using just the bundle.
Skills, facts and review status
Skills
An AI skill (tax rules your AI follows) is a reference document for a tax or accounting task in a particular jurisdiction. The library shows the published material and current coverage.
Facts and sources
Skills use structured facts, such as rates, thresholds and deadlines, with source references. A stored fact is not a guarantee that the law is current. Check the applicable year and the official source before acting on a figure.
Approval
Every skill says Built from the law. It says Approved by [name] when an approved accountant stands behind it; otherwise Not yet approved. The public repository is the source of truth for approval. Do not infer approval from a legacy tier number.
Jurisdictions
A jurisdiction can be a country, state, province or territory, using codes such as MT, GB, US-CA and CA-ON. Library coverage, contributor location and availability for paid work are different. A skill for a country does not mean an accountant is available for every engagement there.
AI tools
Compatible agents can retrieve skills and sources through the hosted MCP server. Limited guest tool use is followed by free sign-in. The tool reference lists the currently advertised tools. Tool use and AI output still need checking.
Professional work
Reading a skill or using a tool does not create an engagement or submit a return. A request for professional help starts an enquiry. OpenAccountants confirms availability, scope, total fee and the responsible accountant in a written engagement before client work starts. See services and prices.
Licensing
The software is open source under AGPL-3.0-only. Skills and exports are covered by the OpenAccountants Guide License. Read the terms before building on the content.
HTTP API reference
Postman collectionOpenAccountants exposes a small, honest public surface. The HTTP read endpoints below are anonymous and CORS-enabled, no key, no sign-in. The MCP tools have separate access limits (see below).
GET /api/bundle/{jurisdiction}
Returns a jurisdiction's published rules as one document, markdown by default, or a structured JSON pack with ?format=json. Optionally pin an immutable version so a batch job sees a fixed snapshot that can't shift mid-run.
| Auth | None |
| Content-Type | text/markdown; charset=utf-8 (or application/json with ?format=json) |
| CORS | Access-Control-Allow-Origin: * |
| Cache | public, max-age=3600, s-maxage=3600 (rolling) · public, max-age=31536000, immutable (exact pin) |
The {jurisdiction} path segment accepts an ISO code (MT, GB, DE, US, US-CA, CA-ON) or a country name (malta, germany, brazil). A jurisdiction with no published skills returns 404.
Query params, all optional; with none supplied the response is the same markdown as before:
| Param | Values | Effect |
|---|---|---|
format | md (default) · json | Human markdown, or the structured JSON pack (facts + tier + citations). |
version | 2026.2 · 2026 / 2026.* · latest | Exact immutable pin · latest correction of that tax year (rolling) · current (default). |
domain | e.g. payroll, vat-gst | JSON only, subset facts to one tax domain. |
tax_year | e.g. 2026 | JSON only, subset facts to a tax year. |
Versions are {tax_year}.{minor}, the tax year is the major, and every released correction bumps the minor. Every response carries X-Content-Version (the resolved version) plus X-Skill-Count (markdown) or X-Fact-Count (JSON). An exact pin (?version=2026.2) is a byte-frozen snapshot served from the CDN, it never changes, so a batch can pin it and reproduce identical figures (it responds 302 to the immutable object). 2026.* (or 2026) always returns the latest correction of that tax year. Discover the current version per jurisdiction from /api/catalog; watch for changes with /api/changelog.
# human markdown (default, unchanged)
curl -i https://www.openaccountants.com/api/bundle/malta
# structured JSON pack, current version
curl -s "https://www.openaccountants.com/api/bundle/US-CA?format=json"
# pinned + immutable, reproducible across a batch
curl -s "https://www.openaccountants.com/api/bundle/US-CA?format=json&version=2026.2"
{
"schema_version": 1,
"jurisdiction": "US-CA",
"tax_year": 2026,
"version": "2026.2",
"acceptance": {
"owner": { "name": "Jane Roe", "credential": "CPA #12345" },
"verification_status": "accountant_verified",
"source_date": "2026-01-01"
},
"counts": { "facts": 37, "accountant_verified": 31 },
"facts": [
{
"fact_key": "ca_sdi_rate",
"skill_slug": "us-ca-payroll",
"domain": "payroll",
"fact_type": "rate",
"value": "1.2",
"unit": "percent",
"tier": "accountant_verified",
"review_status": "current",
"reference": "CA UI Code §984",
"source_url": "https://edd.ca.gov/…",
"effective_date": "2026-01-01"
}
]
}
GET /api/ruleset
Queries individual facts/rules (not whole documents) across the corpus, the public, third-party wrapper over the MCP search_rules tool. Returns cited markdown by default, or JSON with ?format=json.
| Auth | None |
| Content-Type | text/markdown; charset=utf-8 (or application/json with ?format=json) |
| CORS | Access-Control-Allow-Origin: * |
| Cache | public, max-age=3600, s-maxage=3600 |
Filter with any of these query params (all optional, comma-separated where plural): jurisdictions, domains, roles, block_types, status (or statuses), tax_year, topic, q (or text, free-text), limit, offset. The response sets an X-Fact-Count header. POST /api/ruleset accepts the same filters as a JSON body.
curl -s "https://www.openaccountants.com/api/ruleset?jurisdictions=MT&domains=vat-gst&q=standard%20rate&format=json"
GET /api/catalog
A JSON index of every jurisdiction with a published pack: its current version, the accounting owner, verification status, and a pack_url pointing straight at the immutable JSON pack for the current version. This is how a consumer discovers what to pin.
| Auth | None |
| Content-Type | application/json |
| CORS | Access-Control-Allow-Origin: * |
| Cache | public, max-age=300 |
curl -s https://www.openaccountants.com/api/catalog
{
"schema_version": 1,
"jurisdictions": [
{
"jurisdiction": "US-CA",
"tax_year": 2026,
"current_version": "2026.2",
"updated_at": "2026-07-09T12:00:00Z",
"owner": { "name": "Jane Roe", "credential": "CPA #12345" },
"verification_status": "accountant_verified",
"source_date": "2026-01-01",
"pack_url": "https://<project>.supabase.co/storage/v1/object/public/content-packs/US-CA/2026.2.json"
}
]
}
GET /api/changelog
A feed of version bumps, newest first, one entry per released change. Poll it to schedule deliberate re-pins instead of re-fetching every pack.
| Auth | None |
| Content-Type | application/json |
| CORS | Access-Control-Allow-Origin: * |
| Cache | public, max-age=60 |
Query params: jurisdiction (ISO code or country name) and since (ISO date/timestamp), both optional.
curl -s "https://www.openaccountants.com/api/changelog?jurisdiction=US-CA&since=2026-06-01"
{
"schema_version": 1,
"releases": [
{
"jurisdiction": "US-CA",
"version": "2026.2",
"tax_year": 2026,
"kind": "edit",
"summary": "ca_sdi_rate: 1.1 -> 1.2",
"changed_fact_key": "us-ca-payroll.ca_sdi_rate",
"published_at": "2026-07-09T12:00:00Z"
}
]
}
GET /api/accountants
A JSON directory of accountant profiles, optionally filtered by jurisdiction. Use it to read about accountants and their published work. Professional-work enquiries go to OpenAccountants.
| Auth | None |
| Content-Type | application/json |
| CORS | Access-Control-Allow-Origin: * |
| Cache | public, max-age=3600, s-maxage=3600 |
Query params
| Param | Type | Description |
|---|---|---|
jurisdiction | string (optional) | ISO code or country name (e.g. BR, malta). Omit for all. |
Results are capped at 50 (truncated: true when more exist). Profiles show credentials and published work. To discuss paid work, talk to OpenAccountants. Availability, scope, fee and the responsible accountant are agreed in a separate written engagement with OpenAccountants.
curl "https://www.openaccountants.com/api/accountants?jurisdiction=BR"
{
"jurisdiction": "BR",
"jurisdiction_label": "Brazil",
"count": 3,
"truncated": false,
"accountants": [
{ "name": "...", "credential": "...", "firm_website": "...", "profile_url": "..." }
],
"next_action": "...",
"attribution": "Verified on OpenAccountants"
}
GET /llms.txt and GET /llms-full.txt
Plain-text index files written for AI agents.
/llms.txt, a quick-reference: the bundle endpoint, the accountant directory, the MCP server, and the workflow trigger phrases./llms-full.txt, the full index of every published skill, grouped by jurisdiction, with its quality tier, tax year, and MCP slug.
Both are text/plain, public, cached ~1 hour.
The MCP server
POST /api/mcp is a JSON-RPC 2.0 (Streamable HTTP) endpoint with the current tools listed in the tool reference. The tool catalogue is public. Eligible read tools allow limited guest use, then require a free account. Contribution and verification tools require sign-in through the connector (an anonymous call to one of those returns a 401 with an OAuth challenge). Limits are 60 req/min per IP and 1,000 req/day per account.
The complete, auto-generated tool list is in the MCP tool reference.
On the roadmap (not yet live)
To set expectations honestly, these do not exist yet: a keyed REST API for platforms (today the machine paths are the public bundle, including the versioned JSON packs, catalog, and changelog above, plus the OAuth-gated MCP), automated submission-to-authority / e-filing, and filing-status webhooks. See the roadmap.
Power your own tax calculator
Skill content requires written permission for inclusion in a product or service; see the licence terms.
This is the lightest way to build on OpenAccountants: take only the data. If you're a neobank or invoicing tool building your own in-house tax calculator, you want accurate, cited inputs, local rates and allowances, and you'll do the computation yourself.
1. Fetch the rules for a jurisdiction
One anonymous request returns every published rule. Ask for JSON, it's the structured shape a calculator wants (each fact with its value, unit, quality tier, and citation), so there's no markdown to parse:
curl -s "https://www.openaccountants.com/api/bundle/US-CA?format=json"
No auth, no key. The {jurisdiction} segment takes an ISO code (US-CA, GB, MT) or a country name (malta). Drop ?format=json for the human markdown version. See the HTTP API reference for the full pack shape, headers, and caching.
Pin a version for reproducibility. So your calculator can't silently change mid-release, pin an immutable snapshot with ?version=2026.2, a byte-frozen pack that never shifts. Discover the current version per jurisdiction from /api/catalog, and watch /api/changelog so you re-pin deliberately when a figure is corrected.
2. Parse what you need
Each rule carries its source. Read the linked skill for its current approval. Legacy tier and review_status values are compatibility fields, not the displayed approval. Read skills and approval. Do not infer that a figure is current from a legacy tier number. Pull the figures you care about (brackets, thresholds, allowances, deadlines) into your own model. A common pattern:
fetch pack → read each fact's value + tier + source link (+ review_status)
→ store them with the pack's version as the "as of"
→ re-pin when /api/changelog reports a bump (or refresh the ~1h rolling cache)
Surface the tier and the source link in your own UI where it matters, a user (or your compliance team) should be able to see the recorded review status, applicable year and source.
3. Do the maths
The bundle gives you the inputs, not a computed answer. You apply them to the user's numbers in your own engine. That's the trade-off of the data-only path: maximum control, and you own the calculation.
When to reach for more
- Want the reasoning done for you, estimates, set-asides, deduction detection? That's the MCP intelligence tools.
- Need professional work on a user's situation? Talk to OpenAccountants about the scope and accountant responsible.
This guide is block one of the three composable building blocks on /for-developers, take just the data, or combine it with the others.
Add tax to your AI agent
If you're embedding tax Q&A into an AI agent or app, the MCP server gives your agent live, jurisdiction-accurate tools instead of guessing from training data.
1. Connect the server
Add the OpenAccountants connector from /connect. It speaks the Model Context Protocol, so it works with any MCP-compatible AI agent. The tool catalogue is public. Eligible read tools allow limited guest use, then require a free account. Contribution and verification tools are gated: your agent signs in, and those calls run as that account. Limits are 60 requests/minute per IP and 1,000/day per account.
2. A typical call sequence
Lead with start so the server can scope the request and tell the agent which skills to load:
start, pass the user'sintent(for example, "My client is preparing a UK VAT return") andjurisdiction. It returns the skills to load.search_skills/get_skill, pull the cited rules the answer is built from. Large skills split into sections you fetch withget_skill_sections.search_rules, look up the figures and their official sources. For cross-border work, load the relevant skills for each jurisdiction.share_with_openaccountants, only when the user asks to share the work with OpenAccountants. Professional work requires a separate engagement with OpenAccountants.
3. Cite the source
Tool responses carry an OpenAccountants source line. Keep it where it's natural, you're surfacing figures a user may act on, so cite them the way you'd cite any reference.
Full tool list
The available tools, their parameters, and which are public vs require sign-in vs an approved-accountant account are in the MCP tool reference, generated from the live server, so it never drifts.
Work with OpenAccountants
Read about the accountants
GET /api/accountants returns public accountant profiles, filterable by jurisdiction:
curl "https://www.openaccountants.com/api/accountants?jurisdiction=BR"
Read each profile's credentials and published work. A directory entry or skill byline does not guarantee availability or assign that accountant to a client. The HTTP reference describes the response fields.
Submit a help request only when the user asks
The currently advertised MCP tool is share_with_openaccountants. When the user requests professional help, its review option can send the details and working paper the user chooses to share. The tool reference lists its current parameters and access requirements.
Explain what will be sent before submitting it. Hosted tool requests reach OpenAccountants and are logged under the Privacy Policy. Our team reviews the enquiry and confirms whether we can take on the work. An enquiry does not itself create an engagement.
Confirm the engagement
You engage OpenAccountants for professional work. We confirm availability, the work, fee, start date and responsible accountant in writing before we start.
The accountant credited on a skill is not automatically the person responsible for client work. The engagement identifies any locally licensed professional required to sign or file. The free connection does not submit a return or make a payment.
Roadmap
We'd rather under-promise than point you at a spec that isn't live. Here's the honest split.
Live today
GET /api/bundle/{jurisdiction}, every published rule for a jurisdiction as cited markdown. Anonymous, CORS-enabled.GET /api/accountants, the accountant directory. Anonymous, CORS-enabled./llms.txtand/llms-full.txt, index files for AI agents.- The MCP server (
POST /api/mcp), 37 tools: skill discovery and retrieval, rates and cross-border planning, and requests to OpenAccountants for professional work are public; contribution and, for credentialed accountants, workflow authoring and skill verification require sign-in.
See the HTTP API reference and the MCP tool reference for the details.
On the roadmap
These are not yet shipped, don't build against them as if they're live:
- A keyed REST API for platforms. Today the machine paths are the public bundle and the OAuth-gated MCP server. A first-party, key-authenticated REST API for platform integrations is planned.
- Automated submission-to-authority (e-filing). Professional work requires a separate written engagement with OpenAccountants. Automated submission to a tax authority is roadmap.
- Filing-status webhooks. Events such as
return.submitted,accountant.reviewing, andreturn.filed, described on /for-platforms as part of the embedded-tax vision, are not yet emitted.
Want one of these sooner?
If a roadmap item is on your critical path, we'd rather scope a private integration with you than have you build against something that doesn't exist. Tell us what you need on /for-platforms or get in touch.
Pricing
Build for free. Pay when it runs in a live product.
| Plan | Price | What it covers |
|---|---|---|
| Build | Free | Testing and development. 100 calls a month. Not for a live product. |
| Developer | EUR 49 a month | One live product. Up to 5,000 calls a month. |
| Business | EUR 499 a month | Several products, up to 100,000 calls a month. Email support. |
| Enterprise and data | By quote | Higher volumes, and training or evaluating models on the methods. |
Prices exclude VAT. To start on a paid plan, tell us which one in the form below and we set it up.
What you get
- Methods for 290 countries, states and territories (223 countries). See coverage by country
- 123 methods approved by a named accountant, in 26countries. Every other method is labelled “Built from the law”, and each method names the official sources for its figures.
- The same methods over a plain HTTP API or the MCP server.
- Calculators (the MCP
computetool) that return the figure, every step, and the line of the method each rate came from. - Putting the methods in a product needs a paid plan. The full terms are in the licence terms.