Anrok
Anrok is a SaaS-focused global sales tax and VAT compliance platform built for modern commerce. It provides a REST API that enables software companies to calculate sales tax in real time, manage nexus registrations across 11,000+ US jurisdictions, handle exemption certificates, and validate customer tax IDs. The platform integrates with billing systems such as Stripe, Chargebee, and Recurly, and automates tax filing and remittance across 100+ countries. Anrok also offers Anrok Atlas, an AI-native agentic tax partner for proactive compliance monitoring.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Anrok the way a machine reads it — 56 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Anrok scores 54.5/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Anrok
Each block below is one kind of artifact we hold for Anrok. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Anrok Customer certificates API
A sales tax exemption certificate documents the exemption claimed by a purchaser to legally make a tax-free purchase. Certificates can be uploaded to Anrok via the Anrok UI as w...
Anrok Filings API
**The Filings endpoint is a premium feature. Please contact [email protected] for more information to enable this on your seller account.** This endpoint can be used to fetch fili...
Anrok Product mappings API
The Anrok Product Mappings API endpoint allows you to dynamically map product IDs for [Anrok-built billing system integrations](https://help-center.anrok.com/hc/en-us/articles/4...
Anrok Products API
The Anrok Products API endpoints allow you to manage the products on your seller account. Each product is identified by an external ID and is assigned a product tax category (PT...
Anrok Tax ID validation API
**The Anrok Tax ID Validation endpoint is a premium feature. Please contact [email protected] for more information to enable this on your Anrok seller account.** 1. Pass a custome...
Anrok Transactions API
This documentation describes how to use Anrok's Transactions API to synchronize transactions between Anrok and your billing system, as well as calculate sales tax for new invoic...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Anrok Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Anrok Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Anrok Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Anrok Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Anrok API Rules
SPECTRALJSON Schema 33
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CommonTransactionProperties
JSON SCHEMACreateEphemeralTransactionSuccess
JSON SCHEMACreateEphemeralTransaction
JSON SCHEMACreateOrUpdateTransactionSuccess
JSON SCHEMACreateOrUpdateTransaction
JSON SCHEMACreateProduct
JSON SCHEMACreateTransactionCannotComputeTaxAmount
JSON SCHEMACreateTransactionCannotUpdate
JSON SCHEMAAddress
JSON SCHEMACustomerCertificateFile
JSON SCHEMACustomerCertificateJurisResponse
JSON SCHEMACustomerCertificateJuris
JSON SCHEMACustomerCertificateResponse
JSON SCHEMACustomerCertificate
JSON SCHEMACustomerId
JSON SCHEMALegacy US only address
JSON SCHEMACustomerName
JSON SCHEMACustomerTaxId
JSON SCHEMAFilingInfoFilter
JSON SCHEMAJurisSummary
JSON SCHEMALastModifiedAfterFilter
JSON SCHEMALineItemJurisTax
JSON SCHEMALineItem
JSON SCHEMANormalTransactionBody
JSON SCHEMANormalTransactionResponse
JSON SCHEMANotTaxedReason
JSON SCHEMAProductTaxCategoryId
JSON SCHEMATaxAmountDue
JSON SCHEMATransactionLineItem
JSON SCHEMATransaction
JSON SCHEMAValidateTaxIdSuccess
JSON SCHEMAValidateTaxId
JSON SCHEMAVoidedTransactionResponse
JSON SCHEMAScroll within the panel for all 33 ·
Examples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Create Certificate Request
EXAMPLEValidate Tax Id Request
EXAMPLEScroll within the panel for all 7 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Anrok — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/anrok · machine-readable index on apis.io