# Kintsugi > Kintsugi is a hosted sales tax, VAT and GST compliance platform. Its API estimates tax, records transactions, customers and exemptions, and manages nexus, registrations and filings. Two MCP servers connect AI assistants to the API and to account data. - Canonical: https://www.anchorterminal.com/tools/kintsugi - Markdown: https://www.anchorterminal.com/tools/kintsugi.md (~8,100 tokens) - Slim: https://www.anchorterminal.com/tools/kintsugi.min.md (~1,830 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/kintsugi.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade C · 60.7/100 · rank #392 of 722 · #3 in Tax calculation & compliance · not agent-ready · confidence medium** ## Assessment The docs are built for machine readers, with llms.txt, Markdown pages, a public OpenAPI 3.1 file, a dated changelog and an MCP server whose 55 tools carry read-only and destructive annotations. API keys need the custom-priced Premium plan and carry no scopes, no general rate limit is published, and breaking changes reached the pinned 2026-07-21 release in October 2026. ## Facts | Field | Value | | --- | --- | | Vendor | Kintsugi AI, Inc. (https://trykintsugi.com) | | Kind | HTTP API | | Category | Tax calculation & compliance (https://www.anchorterminal.com/categories/tax) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://api.trykintsugi.com` | | Auth | OAuth or key · API keys are self-serve in the app under Configuration, API Keys, but only on a paid plan that includes them, and the pricing page lists API access under Premium, which is arranged through sales. The Tenanted API takes the key in `Api-Key`. v1, the SDKs and the docs MCP server take `x-api-key` with `x-organization-id`. A key belongs to one organisation, can expire, and has no scopes. Key and user management endpoints accept only an Owner or Admin session token. The account-data MCP server uses OAuth 2.1 with PKCE, dynamic client registration and the scope `read:user_data`, signed in with the app login. | | Pricing | Paid ($75 / tx) · API access is listed only under Premium, which is priced on request. Free is $0 with no card and covers exposure monitoring, CSV imports and no-code integrations, without API keys. Starter starts at $75 per filing or registration. No free tier or sandbox with live API access was found, so an agent can't start on the API without a Premium plan. The API Lab in the docs runs against simulated responses (https://trykintsugi.com/pricing, checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the API docs, the OpenAPI file or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under the Kintsugi Terms of Service. The Python SDK repository is MIT | | Tools exposed | 55 | | Packages | pypi: `kintsugi-tax-platform-sdk`; npm: `@kintsugi-tax/tax-platform-sdk` | | Source | https://github.com/kintsugi-tax/kintsugi-tax-python-sdk | | Docs | https://docs.trykintsugi.com | | llms.txt | https://docs.trykintsugi.com/llms.txt | | Last release | 2026-10-07 | | npm downloads / week | 71 | | PyPI downloads / week | 10 | | APIs | Tenanted API at https://api.trykintsugi.com with no path prefix, 287 operations in each of releases 2026-07-21 and 2026-10-06. v1 under `/v1`, 55 documented operations, labelled legacy. A separate Partner API is documented too | | Calculation | `POST /tax-estimations` (v1 `POST /v1/tax/estimate`) returns tax without storing anything. Tax is zero where no active registration covers the destination unless `simulateActiveRegistration` is set | | Transactions | Creating a transaction answers 202 and tax is calculated just after. Credit notes record refunds. Creates are idempotent on `externalId` and `source` | | MCP servers | Docs and API server at https://docs.trykintsugi.com/mcp, Streamable HTTP, 55 tools over v1 with the API key in headers. Account-data server at https://mcp.trykintsugi.com/mcp, OAuth 2.1, 46 read-only tools per Kintsugi | | Credentials | Organisation API key with optional expiry (one month, six months, one year or never), several keys allowed, no scopes. OAuth 2.1 with PKCE, dynamic client registration and scope `read:user_data` for the account-data MCP server | | Rate limits | No general limit published. `POST /filings/{filing_id}/enhanced-data/rebuild` allows 10 requests a minute. 429 answers with code `rate_limited` | | Errors | Tenanted API envelope of `code`, `message`, `requestId` and `errors`, with 20 documented codes and four field-level codes. v1 error shapes vary by endpoint | | Paging | Keyset cursors with `limit` and `cursor` on the Tenanted API, plus `sort`, `order` and filters. v1 uses `page` and `size` | | Pricing | Free $0. Starter from $75 per filing or registration. Premium quoted by sales, and the only plan listed with API access, SDKs and coverage outside the US | | SDKs | Python `kintsugi-tax-platform-sdk` 0.13.0 (15 September 2026), TypeScript `@kintsugi-tax/tax-platform-sdk` 0.10.2 (7 July 2026), Java, PHP and Ruby, generated with Speakeasy, covering v1 only | | Certifications | SOC 2 Type II per trykintsugi.com/security-and-privacy. AES-256 at rest and TLS 1.2 or later in transit, per the same page | | Status | Statuspage at https://status.trykintsugi.com with five components, among them API and Filings and Registrations | | Data | Processed in the United States per the DPA of 26 August 2026. 60 days to retrieve data after termination, and deletion on request, per the terms | | Capabilities | tax.calculate, tax.transactions, tax.filing, tax.exemptions | | Tags | hosted, paid, closed-source, api-key, oauth, mcp, openapi, llms-txt, python, typescript, java, php, ruby, sales-led, status-page, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/kintsugi.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 73 | 14.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 87 | 14.1 | | Agent ergonomics | 13% | 16.2 | 75 | 12.2 | | Security & auth | 14% | 17.5 | 52 | 9.1 | | Payments & pricing | 10% | 12.5 | 13 | 1.6 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 78 | 6.8 | | Transparency & trust (editorial 44, provenance 75) | 7% | 8.8 | 60 | 5.2 | | Negative events | up to −15 | up to −15 | 2 to 7 October 2026. The API changelog marks five changes applied to the pinned 2026-07-21 release as breaking (address access rules and import `userId` on 2 October, filing pause window and a changed error code on 5 October, billing callers on 7 October), while the docs say a pinned release can't change an integration. Each is documented with migration steps on the day, so we deducted the minimum of 3. No advance notice was found (https://docs.trykintsugi.com/reference/changelog) | -3 | | **Total** | | | | **60.7 → C** | ### Why each score - Reliability 73: Graded on the public API with the hosted lines. Statuspage at status.trykintsugi.com with five components, among them API (20). No incident in the 90 days to 8 October 2026. The only real entry is 16 March 2026, elevated API errors, minor, about seven and a half hours (30). No general rate limit was found in the docs. One endpoint, `POST /filings/{filing_id}/enhanced-data/rebuild`, states 10 requests a minute (2). The error guide says to retry 429, 500 and 503 with exponential backoff and jitter, creates are idempotent on `externalId` and `source`, and one import endpoint takes an `idempotencyKey`. No `Retry-After` header is documented (11). The pricing page lists SLA-backed premium support, and no uptime SLA document was found (0). The Tenanted API and v1 carry no beta label (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 87: OpenAPI 3.1 is public at `https://api.trykintsugi.com/openapi.json` with 901 operations, covering v1, partner and admin paths. No downloadable file was found for the date-versioned Tenanted API, whose 287 operations a release are documented in the reference (22). `llms.txt`, a `.md` twin of every page and `llms-full.txt` (10). Reference pages state what a call does, when a selector is needed and what each status means, and MCP tool descriptions say whether a call is read-only or changes data. Some v1 descriptions are one line (16). 205 enums and 683 maxLength constraints in the spec, with required fields marked. Several v1 filters are free strings that take comma-separated values (12). 866 examples in the spec, plus a documented error envelope and a table of 20 error codes (14). Tenanted releases are dated and chosen with `Api-Version`, and the changelog is public with dated entries. Changes marked breaking were applied to the pinned 2026-07-21 release (13). - Agent ergonomics 75: List endpoints take `limit` and a cursor, with no field selection found. The docs MCP server returns 55 tool definitions of about 185 KB in all, three of them over 25 KB each, and the account-data server has 46 (10). Keyset cursors, sort and order, and filters by date, status, source, customer and country (18). One envelope with a stable `code`, `requestId` and field-level `errors` naming each field. v1 error shapes vary by endpoint, per the changelog (18). Creates are idempotent on `externalId` and `source`, and all 55 MCP tools set readOnlyHint, destructiveHint and idempotentHint. No general idempotency key header (17). Five official SDKs (Python, TypeScript, Java, PHP, Ruby), which cover v1 only. An estimate needs three required fields plus line items and an address (12). - Security & auth 52: Two credential models. An API key is tied to one organisation, shown once, revocable at once, with optional expiry and several keys allowed for rotation, and no scopes (22 on its own). The account-data MCP server uses OAuth 2.1 with PKCE (S256), dynamic client registration and one scope, `read:user_data` (27 on its own). Scored between the two (24). Kintsugi says all 46 tools on the account-data server are read-only, the docs MCP server marks 23 of its 55 tools as changing data and tells the client to confirm with the user, and key management needs an Owner or Admin session. The API key has no read-only mode (13). Responses carry customer names and descriptions written by others, and no injection guidance was found (3). Every error carries a `requestId`. No audit log of API calls was found (2). SOC 2 Type II per the security page and a 72-hour breach notice in the terms. No `security.txt`, disclosure policy or bug bounty found (10). - Payments & pricing 13: No x402, MPP or L402 (0). Free is $0 and Starter starts at $75 per filing or registration, both public, but API access is listed only under Premium, which is priced on request (5). The Free plan needs no card, and the account-data MCP server asks only for a Kintsugi login. API keys need a paid plan that includes them, so we scored the free tier as partial (8). Signup happens in a browser, and the endpoint that creates API keys accepts only a signed-in Owner or Admin session token (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 78: The API changelog's newest entry is 7 October 2026, and release 2026-10-06 shipped the day before (30). 33 changelog entries on eight dates from 17 September to 7 October 2026 (20). Closed service with a public changelog, support by email, phone and live chat, and a developer community marked coming soon (10). Five official SDKs generated with Speakeasy. Python 0.13.0 is dated 15 September 2026 and `@kintsugi-tax/tax-platform-sdk` 0.10.2 is dated 7 July 2026, and they cover v1 only. Neither MCP server is in the official registry (11). The Python SDK repository is MIT with Dependabot updates merged (7). - Transparency & trust 60: Closed service with clear terms, last updated 29 September 2026, naming Kintsugi AI, Inc. of Delaware. The SDKs are MIT (15). The terms give 60 days to retrieve data after termination and deletion on request, and allow Customer Data to be used to improve the models Kintsugi runs for all customers. The DPA of 26 August 2026 says processing happens in the United States and promises 30 days' notice of a new sub-processor. The privacy policy is dated 13 April 2025 (17). No deprecation policy with dates was found. v1 is labelled legacy with no end date, and deprecated fields are described as removed in future releases (5). The DPA states the United States as the processing location. No sub-processor list was found on the public pages, and the Drata trust centre was not read (7). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (22 items): https://www.anchorterminal.com/fixes/kintsugi.md (JSON https://www.anchorterminal.com/fixes/kintsugi.json) ### What we couldn't check - unchecked: the Drata trust centre at app.drata.com linked from the security page, which may hold a sub-processor list and the SOC 2 report. We didn't load it - unchecked: the live tool definitions of the account-data MCP server, which need a Kintsugi login. The count of 46 and the read-only claim come from the help centre and the announcement - unchecked: Maven Central, Packagist and RubyGems for the Java, PHP and Ruby SDKs. We read npm, PyPI and the Python repository only - Whether advance notice of the breaking changes of September and October 2026 reached customers by email. None was found in the changelog or docs - Whether the docs MCP server calls the API. The setup guide says it never proxies calls or sees credentials, while its own configuration sends `X-API-KEY` and the server's instructions say each tool calls the API with that key - Whether the account-data MCP server works on the Free plan. The help article asks for an active account and names no plan - What the general rate limits are. Only one endpoint states a number - Whether an uptime SLA exists in Premium contracts. The pricing page names SLA-backed premium support only - No downloadable OpenAPI file was found for the Tenanted API. The public file covers v1, partner and admin paths - The terms bar using the services to train or improve any machine-learning model and bar competitors from benchmarking. Recorded as a fact with no deduction ### Sources - docs index for agents: (seen 2026-10-08) - full docs text (API keys, authentication, error handling, SDKs, MCP, reference): (seen 2026-10-08) - API changelog and releases: (seen 2026-10-08) - OpenAPI 3.1 file: (seen 2026-10-08) - unauthenticated API response and headers: (seen 2026-10-08) - docs MCP server, initialize and tools/list: (seen 2026-10-08) - MCP setup guide: (seen 2026-10-08) - account-data MCP OAuth metadata: (seen 2026-10-08) - account-data MCP announcement, 18 September 2026: (seen 2026-10-08) - help centre, MCP tool reference: (seen 2026-10-08) - help centre, connect to Claude: (seen 2026-10-08) - pricing: (seen 2026-10-08) - terms of service: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - data processing agreement: (seen 2026-10-08) - security page: (seen 2026-10-08) - status page components: (seen 2026-10-08) - status incident history: (seen 2026-10-08) - npm package: (seen 2026-10-08) - PyPI package: (seen 2026-10-08) - Python SDK repository: (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - domain registration: (seen 2026-10-08) ## Who's behind it (provenance 75/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Kintsugi AI, Inc. | 20/20 | | Domain age | trykintsugi.com, registered 2023-03-10 (3 years) | 7/15 | | Endpoint on the vendor's domain | api.trykintsugi.com | 15/15 | | Terms of service | read, states 7 of the 7 things a reader expects, and has 3 clauses that cost points | 4/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.trykintsugi.com | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The terms of service (last updated 29 September 2026) name Kintsugi AI, Inc., a Delaware corporation at 2261 Market St, Suite 5931, San Francisco, and cover the platform unless a signed Customer Agreement applies. The terms incorporate the privacy policy (last updated 13 April 2025) and the Data Processing Agreement at trykintsugi.com/data-processing-agreement (last updated 26 August 2026). The API answers at api.trykintsugi.com and the MCP servers at docs.trykintsugi.com and mcp.trykintsugi.com, all on the vendor's domain. trykintsugi.com/.well-known/security.txt returns 404. The security page names no disclosure address or bug bounty. RDAP for trykintsugi.com gives a registration date of 2023-03-10 and GoDaddy as registrar. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://trykintsugi.com/terms-of-service), read 2026-10-08, dated 2026-09-29, states 7 of the 7 things a reader expects. - To know. Says it may use customer content to train or improve models, and no opt-out was found (costs points). "Kintsugi may also use Customer Data to operate, secure, maintain, troubleshoot, and improve the Services, including to develop and improve the models, algorithms, taxonomies, and automation Kintsugi uses to serve all customers." - To know. Restricts automated access (costs points). "(d) access the Services by any automated means (including scrapers, crawlers, or bots) other than through Kintsugi's documented APIs, or systematically retrieve data to build a database, compilation, or directory;" - To know. Restricts benchmarking or competitive use (costs points). "Government list of prohibited or restricted parties, or if you are a competitor of Kintsugi accessing the Services to evaluate, benchmark, or build a competing product." - To know. Requires arbitration or waives class actions. "YOU UNDERSTAND THAT BY AGREEING TO ARBITRATION YOU ARE WAIVING THE RIGHT TO A JURY TRIAL AND TO BRING OR PARTICIPATE IN A CLASS ACTION." - Gives the date it was last updated. Last updated 2026-09-29. - Names the governing law or courts. The law of Internal Substantive Laws. - States a limit on its liability. Capped at US$100. - Says how changes to the terms are announced. Gives thirty days of notice before a change. - Also in the text (2026-10-08). Customers may not use the Services or Kintsugi content to train, fine-tune or improve any machine-learning or artificial-intelligence model. "(e) use the Services or Kintsugi Content to build, train, benchmark, or support a product or service that competes with the Services, or to train, fine-tune, or improve any machine-learning or artificial-intelligence model;" - Also in the text (2026-10-08). Kintsugi exports customer data only on a request made within 60 days after the subscription ends. "Upon request made within sixty (60) days after your subscription ends, Kintsugi will provide an export of Customer Data stored on its systems in a commonly used format or limited access to the Services to retrieve it, at no additional charge." - Also in the text (2026-10-08). Kintsugi may name the customer and show its logo as a customer unless the customer objects in writing. "Unless you notify us otherwise in writing, Kintsugi may identify you as a customer by name and logo in accordance with any marketing guidelines you provide." **Privacy policy** (https://trykintsugi.com/privacy-policy), read 2026-10-08, dated 2025-04-13, states 7 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2025-04-13. - Says how long data is kept. For as long as needed, with no period named. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. help@trykintsugi.com. - Not found in the text. Says where data is transferred or stored. - Also in the text (2026-10-08). Inputs, outputs and personal information used with the AI products are shared with third-party AI providers, including OpenAI and Amazon Bedrock. "As outlined in this Privacy Notice, your input, output, and personal information will be shared with and processed by these AI Service Providers to enable your use of our AI Products for purposes outlined in "WHAT LEGAL BASES DO WE RELY ON TO PROCESS YOUR PERSONAL INFORMATION?"" ## Live (updated 2026-10-08 21:58 UTC) - Right now: up, HTTP 404, 598 ms, checked 2026-10-08 21:53 UTC (get on `https://api.trykintsugi.com`) - Uptime 24h 100.0% (28 probes) · 30 days 100.0% (28 probes) · p50 574 ms · p95 672 ms - Vendor status page: none, All Systems Operational - Always current: https://www.anchorterminal.com/api/v1/live/kintsugi.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Starter plan, per filing or registration | $75 | per transaction | Starting price. API access is not included in Starter and is listed only under Premium, which is quoted by sales | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Docs served for agents. `llms.txt` indexes 682 pages, every page has a `.md` twin, and `llms-full.txt` holds the full text - Public OpenAPI 3.1 file at `https://api.trykintsugi.com/openapi.json`, readable without a key, with 901 operations and 1,325 schemas - The MCP server at `https://docs.trykintsugi.com/mcp` lists 55 tools, each with readOnlyHint, destructiveHint and idempotentHint set - A second MCP server at `https://mcp.trykintsugi.com/mcp` uses OAuth 2.1 with PKCE and dynamic client registration, and Kintsugi says its 46 tools are all read-only - One error envelope on the Tenanted API with a stable `code`, a `requestId` and field-level `errors`, and creates that are idempotent on `externalId` and `source` ## Weaknesses - API access, SDKs and real-time tax calculation are listed only under Premium, which is priced on request. API keys need a paid plan that includes them - Nine changelog entries from 17 September to 7 October 2026 are marked breaking, five on the pinned 2026-07-21 release and four on v1. No advance notice was found - No general rate limit is published and no `Retry-After` header is documented. The docs say only to retry 429, 500 and 503 with backoff - API keys act on a whole organisation with no scopes or read-only mode. Expiry is the only setting - No `security.txt`, disclosure policy, bug bounty, uptime SLA document or subprocessor list was found on the public pages ## Before you call it (notes for agents) 1. Send `Api-Key` and pin `Api-Version` (for example `2026-10-06`) on Tenanted API calls to `https://api.trykintsugi.com`. Without the header a request runs against `2026-07-21` 2. Use `x-api-key` and `x-organization-id` with `/v1` paths for the SDKs and the docs MCP server. They don't cover the Tenanted API 3. Call `POST /tax-estimations` for a quote. Nothing is stored. Record the sale with a transaction create, which answers 202, then check `processingStatus` before reading tax totals 4. Always send `externalId` on creates. A repeat with the same `externalId` and `source` returns the stored record with 200 and doesn't apply the new fields 5. Branch on the error `code`, not the message. Retry 429, 500 and 503 with exponential backoff, and restart paging from the first page on `stale_cursor` ## Connect Install: ```bash pip install kintsugi-tax-platform-sdk ``` First request: ```bash curl https://api.trykintsugi.com/products/categories \ -H "Api-Key: $KINTSUGI_API_KEY" \ -H "Api-Version: 2026-07-21" ``` MCP client configuration: ```json { "mcpServers": { "kintsugi": { "headers": { "X-API-KEY": "your-api-key", "X-ORGANIZATION-ID": "your-org-id" }, "url": "https://docs.trykintsugi.com/mcp" } } } ``` Through letme (picks today, calling later): https://letme.dev/kintsugi. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Avalara AvaTax | B | 68.8 | 172 | tax.calculate, tax.transactions, tax.exemptions, tax.filing | no | https://www.anchorterminal.com/tools/avalara.md | | Anrok | C | 61.6 | 361 | tax.calculate, tax.transactions, tax.exemptions, tax.filing | no | https://www.anchorterminal.com/tools/anrok.md | | Zamp | D | 49.5 | 609 | tax.calculate, tax.transactions, tax.filing, tax.exemptions | no | https://www.anchorterminal.com/tools/zamp.md | | Numeral | D | 49.3 | 611 | tax.calculate, tax.transactions, tax.exemptions, tax.filing | no | https://www.anchorterminal.com/tools/numeral.md | | TaxJar | C | 57.6 | 470 | tax.calculate, tax.transactions, tax.exemptions | no | https://www.anchorterminal.com/tools/taxjar.md | | TaxCloud | C | 57.4 | 475 | tax.calculate, tax.transactions, tax.exemptions | no | https://www.anchorterminal.com/tools/taxcloud.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Two API generations share one host. The Tenanted API is versioned by date with the `Api-Version` header (releases 2026-07-21 and 2026-10-06, 287 operations each), and v1 keeps `/v1` paths and is labelled legacy (source: ) - The changelog lists 33 entries on eight dates from 17 September to 7 October 2026, nine marked breaking, five of them applied to the pinned 2026-07-21 release (source: ) - The MCP server at https://docs.trykintsugi.com/mcp answered tools/list with 55 tools, one for each documented v1 operation, 32 read-only and 23 that change data, each with annotations (checked 2026-10-08) - A second MCP server at https://mcp.trykintsugi.com/mcp, announced on 18 September 2026, uses OAuth 2.1 and, Kintsugi says, has 46 read-only tools across nine areas of an account (source: ) - The MCP setup guide says the docs server never proxies API calls or sees credentials, while its configuration sends `X-API-KEY` and the server's own instructions say each tool calls the API with that key (source: ) - The terms bar using the services to train, fine-tune or improve any machine-learning model, and allow Kintsugi to use Customer Data to improve the models it runs for all customers (source: ) - The status page has one incident on record, elevated API errors on 16 March 2026 for about seven and a half hours, and none in the 90 days to 8 October 2026 (source: ) ## Compare - [Anrok vs Kintsugi](https://www.anchorterminal.com/compare/anrok-vs-kintsugi.md): C 61.6 vs C 60.7 - [Avalara AvaTax vs Kintsugi](https://www.anchorterminal.com/compare/avalara-vs-kintsugi.md): B 68.8 vs C 60.7 - [Fonoa vs Kintsugi](https://www.anchorterminal.com/compare/fonoa-vs-kintsugi.md): D 51.7 vs C 60.7 - [Kintsugi vs Numeral](https://www.anchorterminal.com/compare/kintsugi-vs-numeral.md): C 60.7 vs D 49.3 - [Kintsugi vs Quaderno](https://www.anchorterminal.com/compare/kintsugi-vs-quaderno.md): C 60.7 vs C 59.5 - [Kintsugi vs TaxCloud](https://www.anchorterminal.com/compare/kintsugi-vs-taxcloud.md): C 60.7 vs C 57.4 - [Kintsugi vs TaxJar](https://www.anchorterminal.com/compare/kintsugi-vs-taxjar.md): C 60.7 vs C 57.6 - [Kintsugi vs Vertex O Series](https://www.anchorterminal.com/compare/kintsugi-vs-vertex-tax.md): C 60.7 vs C 54.7 - [Kintsugi vs Zamp](https://www.anchorterminal.com/compare/kintsugi-vs-zamp.md): C 60.7 vs D 49.5 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on trykintsugi.com or one of its subdomains, or the README of github.com/kintsugi-tax/kintsugi-tax-python-sdk. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "kintsugi", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Kintsugi on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Kintsugi on Anchor Terminal](https://www.anchorterminal.com/badges/kintsugi.svg)](https://www.anchorterminal.com/tools/kintsugi) ``` Plain link: ```html Kintsugi on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Kintsugi is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/kintsugi-dark.png - Light: https://www.anchorterminal.com/assets/share/kintsugi-light.png