Developer platform
Tax compliance, as an API your product calls.
The same deterministic engine, the same versioned rules and the same audit trail that the application uses — reachable from your own software, under your own interface. Every response carries the rule version that produced it, so a figure you render to your users can be explained later.
MCP tools
Your agent calls the tax engine as a tool.
One endpoint — POST /mcp — speaking the Model Context
Protocol. Each tool declares its arguments and its scope, and every invocation is
authorised and audited exactly as a REST call would be. An agent's key is scoped like
any other, and can be narrower.
| Tool | What it does | Scope |
|---|---|---|
| tax_rules_search | Search the rule corpus by jurisdiction, tax type and text. | read |
| tax_rule_at_date | The version of a rule in force on a given date, with its source and whether it is quotable. | read |
| tax_rule_history | Every version of a rule, for explaining a change. | read |
| jurisdiction_get | A jurisdiction and its hierarchy. | read |
| jurisdiction_authorities | Who administers which tax, and whether a filing route exists. | read |
| taxpayer_get | A taxpayer's profile and registrations. | read |
| taxpayer_position | The computed position for a tax year, with its caveat when incomplete. | read |
| taxpayer_obligations | Derived obligations, including the ones with no verified date. | read |
| documents_search | Find documents by kind, state or tax year. | read |
| document_get | One document's extraction and the transactions matched to it. | read |
| transactions_search | Find transactions, matched or unmatched. | read |
| transaction_trace | The chain from a figure back to its source document and rule. | read |
| evidence_gaps | Transactions whose treatment is not yet supported by evidence. | read |
| return_get | A return's state, figures and whether it can be filed. | read |
| filing_status | A return's submissions and whether any authority actually holds it. | read |
| tax_classify | Determine a treatment from facts, with the rule versions it rested on. | calculate |
| tax_calculate | Compute a liability from facts. Deterministic; no model in the arithmetic. | calculate |
| tax_scenario | Compare alternatives without storing anything. | calculate |
| suggest_category | Suggest taxonomy categories, and say what evidence each will need. | calculate |
| return_validate | Check a return without submitting it. | calculate |
What is deliberately not a tool.
These operations exist in the REST API. They are not exposed over MCP, because putting them within reach of a language model would put a legally consequential act one hallucination away from happening. The platform's authorization layer refuses them to a non-human actor regardless of the key's scopes, so this is not a documentation convention — it is enforced.
returns.approve
Approval is an assertion that a human has reviewed the return. A model asserting it would make the assertion worthless.
returns.sign
A signature carries personal liability in most jurisdictions. It requires an identified human with signing authority.
returns.file
Transmission to a revenue authority cannot be undone. It is reachable over REST with an idempotency key and an explicit human approval already recorded.
returns.amend
An amendment restates a filed position and restarts limitation periods.
returns.withdraw
Withdrawing a filing can create a failure-to-file exposure.
returns.access_tax_authority
Establishing or using a credential held with a tax authority is not something to put behind a natural-language interface. The credential belongs to the taxpayer or their agent, and using it is them acting.
payments.initiate
Moving money. Reachable over REST under a separate scope and approval.
documents.delete
Evidence deletion is authorised by a human against a retention policy, and is refused outright while a legal or audit hold is in place.