Skip to main content
AgentTax
Pillar Guide

Agent Tax Compliance: The Complete Reference

AI agents transact across state lines, currencies, and payment rails. Tax owes at the transaction — not at year-end. This guide covers the four pillars of agent tax compliance and how to capture obligation in real time, at agent speed.

51
US jurisdictions covered
105
zip-level local rates
7
rate sources verified daily
v1.5
tax engine version

What is agent tax compliance?

Agent tax compliance is the practice of capturing tax obligations triggered by autonomous AI agent transactions — at the moment of the transaction, not at year-end. It covers four areas: sales and use tax, economic nexus, machine-to-machine payment tax, and capital gains / 1099-DA reporting.

Traditional tax software was built for human filers on quarterly or annual cycles. Agents transact faster than that. A single agent can hit economic nexus in five states in a week. By the time a quarterly review catches the obligation, the statute of limitations clock has already started. Agent tax compliance must live inside the agent loop — one API call per transaction — or it doesn't work.

The same gap appears on the buyer side. Agent-to-agent transactions move through emerging rails — Coinbase's x402, Stripe's MPP, the CDP Bazaar marketplace — and none of those rails carry tax metadata. The obligation still exists at the transaction, but the rail is silent. Capturing it requires a separate compliance layer above the protocol. That is the layer AgentTax occupies.

The four pillars of agent tax compliance

Each pillar is a distinct obligation with its own triggers, thresholds, and reporting surface. AgentTax covers all four through a single API. Start with the pillar most relevant to your agent's work.

Sales & Use Tax
Every AI agent transaction with a US buyer potentially triggers sales or use tax. 45 states plus DC impose sales tax; 25+ tax digital services, SaaS, or data processing. Treatment varies dramatically — Texas taxes 80% of compute, New York taxes SaaS as prewritten software, California exempts most digital services, Chicago adds a 15% local cloud tax.
AI Agent Sales Tax Guide
Economic Nexus
Post-Wayfair, nexus is triggered by sales volume, not physical presence. Typical threshold: $100K in sales or 200 transactions per state in a rolling 12-month window. AI agents scale across state lines instantly — compliance requires per-transaction nexus tracking, not quarterly CPA review.
Economic Nexus Breakdown
Machine-to-Machine Payments
x402, Stripe MPP, and CDP Bazaar are building the agent payment rail. None of them carry tax obligation with the payment. The sales tax exists at the transaction; the rail is silent. Compliance sits in a separate layer above the protocol — which is what AgentTax is.
Machine Payment Tax
Capital Gains & 1099-DA
Agents that trade digital assets (crypto, tokenized assets) trigger capital gains events. Starting tax year 2026, the IRS 1099-DA form applies to digital asset sales and exchanges. Agents need FIFO/LIFO/Specific ID tracking per asset, per lot, per wallet — not a retrospective spreadsheet.
Trades & 1099-DA API

The 15 states agent builders should understand first

Tax treatment varies dramatically. These 15 jurisdictions cover the majority of agent economic activity and the rules that most often surprise builders. For the full 51-jurisdiction taxability matrix, see the classification guide.

StateRule agents need to know
Texas80% of compute/data-processing is taxable (§151.351).
New YorkSaaS taxable as prewritten software under Tax Law §1101.
CaliforniaGenerally exempts SaaS and most digital services.
WashingtonSB 5814 expanded taxability to digital services (effective Apr 2026).
Chicago (IL)15% Personal Property Lease Transaction Tax on cloud services.
New JerseySaaS taxable under TAM 2013-10; information services taxable; professional services exempt.
Maryland3% B2B / 6% B2C split on digital services and information.
ConnecticutData processing taxed at 1%; information services at 6.35%.
IowaB2B digital services exempt by statute.
PennsylvaniaDigital services taxable as computer services.
MassachusettsCustom software and most professional services exempt; canned SaaS taxable.
OhioElectronic information services taxable under R.C. 5739.01(Y)(1)(c) at 5.75% state plus county add-ons.
FloridaTangible software taxable, electronically delivered software and SaaS generally not taxed.
TennesseeSaaS and information services taxable at 7% state rate (T.C.A. §67-6-205); industrial machinery exemption can apply to AI compute resold into manufacturing.
DCData processing services taxable at 6% baseline, scheduled to rise to 10.25% Oct 1, 2026 (B25-0784).

Recent regulatory updates (last 90 days)

Tax law moves quarter-by-quarter at agent speed. These are the changes shaping agent tax compliance right now. Each entry links to the underlying policy via the citation list below.

May 14, 2026California
Newsom budget revise proposes taxing cloud-hosted software
Governor's May Revise asks the Legislature to extend sales tax to digital prewritten software — including SaaS and hosted AI — effective Jan 1, 2027. Department of Finance estimates $2B/year. If enacted, California flips from the largest exempt SaaS market to taxable. Sourcing for an agent runtime called by another agent is the open question — California's destination rule was written for tangible property shipped to buyer addresses.
Agent-builder impact: Agent platforms with California revenue: model the 2027 cutover now. Billing-system SKU tags should already mark California so a flip is a column update, not a migration.
Apr 30, 2026Kentucky
HB 757 — drops 200-transaction nexus prong
Kentucky becomes the second 2026-effective state (after Illinois Jan 1) to remove the 200-transaction economic-nexus trigger. Revenue-only test ($100K) applies effective Aug 1, 2026.
Agent-builder impact: Agents making thousands of small API calls are the most affected. The transaction-count prong was the bigger trap for high-frequency, low-ticket agent transactions; revenue-only thresholds are friendlier to that pattern.
Apr 22, 2026Missouri
HJR 173 / 174 — ballot measure to expand sales tax to services
House Joint Resolutions placed on the ballot would lift Missouri's constitutional bar on taxing services, with AI platforms explicitly in scope. Governor Kehoe sets the election date by May 22, 2026. Earliest realistic effective date: 2027.
Agent-builder impact: Missouri taxes 0% of SaaS today. Billing systems should tag Missouri SKUs now so a future flip to the 4.225% state rate is configuration, not engineering.
Apr 18, 2026Indiana / Illinois / Kentucky
Three states, three answers on AI services — classification matters
Indiana DOR (2026) ruled generative AI chatbot access not subject to sales tax. Illinois IDOR continues to treat AI tools as nontaxable SaaS. Kentucky's HB 757 expansion makes the same service taxable as part of broader digital-services scope. Same product, three answers.
Agent-builder impact: Agent invoices crossing all three states need per-jurisdiction classification at calculation time. A single-rate engine that applies one rule everywhere will be wrong in at least one of those three.
Jan 1, 2026Illinois
200-transaction nexus prong removed (P.A. 102-700)
Illinois became the first state to retire the 200-transaction trigger. Revenue test ($100K) remains. Effective for periods beginning on or after Jan 1, 2026.
Agent-builder impact: Confirms a broader trend: transaction-count nexus is dying as a trigger. For high-frequency agent transactions, this is a net reduction in registration burden across affected states.
Apr 2026Washington
SB 5814 — digital automated services taxable
Washington's expansion of taxable digital services took effect April 2026 (RCW 82.04.192). Most AI-as-SaaS and digital-automated-service deliveries are captured. The transition relief period has expired.
Agent-builder impact: Agents selling AI inference into Washington buyers: the 6.5% state rate plus local layer applies. Engine classification of work_type → economic_category drives whether SB 5814 sweeps the transaction in.

Agent tax compliance quickstart — a seven-step checklist

If you are wiring tax compliance into an autonomous agent for the first time, this is the order of operations. Each step maps to a specific field or endpoint in the AgentTax API; the same shape applies whether you integrate via REST, the Python SDK, the Node SDK, or the MCP server.

1
Classify the agent's work
Pick the work_type that fits the transaction: compute (inference, training), research (data lookup, analysis), content (text/image generation), consulting (advisory output), or trading (asset acquisition or disposal). Each work_type routes to an economic_category that controls taxability across 51 jurisdictions. A single agent can mix work_types per transaction — classification is per-call, not per-account.
2
Capture buyer state + zip at the transaction
Tax sources to the destination. For agent-to-agent transactions over x402 or MPP, the principal's nexus address is the buyer state; for agent-to-human deliveries it is the recipient's address. Without buyer_state, no engine — ours or anyone's — can answer the tax question.
3
Set the B2B flag honestly
is_b2b changes the answer in NJ (information service split), MD (3% B2B / 6% B2C), IA (B2B SaaS exempt), and several others. The flag should reflect whether the buyer holds a resale or commercial-use posture, not whether the buyer is a company. Misclassification here is the most common audit finding.
4
Persist the response with the engine version
Every /api/v1/calculate response carries an engine_version, jurisdiction_chain, policy_references, and confidence score. Store all four on the transaction row. If a rate changes (e.g. Chicago PPLTT 9% → 15% on Jan 1, 2026), the audit answer is the engine_version that was authoritative at the moment of the sale, not the engine_version current at audit time.
5
Track nexus across rolling 12-month windows
Wayfair thresholds are rolling, not calendar-year. An agent that crosses $100K in a 12-month window triggers economic nexus in that state — the registration clock starts at crossing, not at the end of the year. AgentTax's nexus engine is per-agent, per-state, per-day; cross calls /api/v1/nexus to see status.
6
Export 1099-DA for trading agents
If the agent transacts in digital assets, broker basis reporting under Treas. Reg. §1.6045-1 applies to sales on or after Jan 1, 2026. Use /api/v1/export/1099-da to pull the IRS-formatted export at year-end. Agent-to-agent crypto swaps through autonomous wallets are the open audit question — the obligation exists, the rail is silent, the export is your audit trail.
7
Plan for unsettled questions
Watch-list and unsettled questions surface in /decisions with the engine's position, the citation, and the confidence level. Agent-to-agent VAT, AI marketplace facilitator status, and bundled-service True Object Tests are live unsettled questions. The engine does not silently take a position — it asks you to decide and records what you chose.
Common mistake: relying on the agent framework's own "tax" hook (LangChain tools, CrewAI agents, etc.) to compute tax inline. The framework hook fires at execution time, but rate sourcing, nexus tracking, and 1099-DA basis tracking need shared state across the principal's full transaction history. A tool-call hook is the right surface for the calculation; it is the wrong surface for the state.

One API call, full compliance coverage

AgentTax is a REST API built for the agent loop. Every call returns sales tax, local tax, nexus status, confidence score, jurisdiction chain, and policy references. No separate filing pipeline, no quarterly reconciliation.

Request
// One API call, full compliance coverage
const response = await fetch("https://agenttax.io/api/v1/calculate", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "X-API-Key": "atx_live_..."
  },
  body: JSON.stringify({
    role: "seller",
    amount: 5000,
    buyer_state: "TX",
    buyer_zip: "75201",
    transaction_type: "compute",
    work_type: "compute",
    counterparty_id: "agent_buyer_042",
    is_b2b: true
  })
});

// Response includes sales tax, nexus status, audit trail
const result = await response.json();

Statutory citations and regulatory references

Every position the AgentTax engine takes is backed by a statute, regulation, or controlling case. The most-cited authorities, grouped by pillar, are listed below. The full policy registry — including watch-list and unsettled questions — is exposed at /decisions.

Sales & Use Tax
  • Texas Tax Code §151.351
    20% data-processing exclusion (engine taxes the remaining 80%).
  • NY Tax Law §1101(b)(14)
    Defines prewritten software; the NY Dept. of Taxation extends to most SaaS via TSB-A-08(62)S.
  • CA R&TC §6010.9
    Statutorily excludes custom software; SaaS guidance follows in CDTFA Regulation 1502(f)(1)(D).
  • WA RCW 82.04.192 (SB 5814)
    Effective April 2026, redefined taxable services to include most digital and AI-enabled deliveries.
  • Chicago Municipal Code §3-32
    Personal Property Lease Transaction Tax, raised from 9% to 15% on cloud services effective Jan 1, 2026.
Economic Nexus
  • South Dakota v. Wayfair, 585 U.S. 162 (2018)
    Abandoned the physical-presence rule; established economic-nexus as constitutional.
  • Streamlined Sales Tax Governing Board model thresholds
    $100K or 200 transactions in a rolling 12-month window adopted by most member states.
  • IL P.A. 102-700 (2025)
    Illinois dropped the 200-transaction prong effective Jan 1, 2026; revenue-only test now.
  • KY HB 757 (2026)
    Kentucky drops the 200-transaction prong effective Aug 1, 2026.
Machine-to-Machine Payments
  • Coinbase Developer Platform — x402 spec
    Payment-Required (HTTP 402) negotiation between agents. Carries no tax metadata.
  • Stripe MPP (Merchant Payment Protocol)
    Wraps card and stablecoin rails; tax obligation still attaches to the underlying merchant of record.
  • Treasury Reg. §1.6050W
    Third-party settlement organization reporting; remains the federal floor for 1099-K-style reporting on agent payment rails.
Capital Gains & 1099-DA
  • IRC §1091
    Wash-sale rule for stocks/securities (60-day window; loss disallowed and basis tacked to the replacement lot). Treasury has not extended §1091 to digital assets as of 2024 final regs.
  • IRC §1222(3) and Rev. Rul. 66-7
    Long-term requires more than one year — 366 elapsed days from acquisition. AgentTax's engine uses 366 days exactly.
  • Treas. Reg. §1.6045-1 (1099-DA final regs)
    Broker basis reporting on digital asset sales begins for transactions on or after Jan 1, 2026.

How AgentTax compares to existing tax tooling

Most tax tools are built for human filers, e-commerce checkouts, or enterprise tax departments. None of them were designed for autonomous agents transacting on x402, MPP, or CDP Bazaar rails, and none of them carry 1099-DA digital-asset basis tracking inside an API. The table below summarizes the practical differences.

VendorBuilt for agents?CoverageIntegrationKey difference
AgentTaxYes — agent loop, per-call51 jurisdictions, 105 zip-level rates, 1099-DA, x402/MPP-awareREST API, Python + Node SDK, MCP serverBuilt API-first for autonomous agents from day one.
Avalara AvaTaxNo — built for ecommerce + ERPAll 50 states, deep address-level ratesREST + WSDL; latency typically optimized for batchStrong at e-commerce checkout; not designed for 402-style agent payment rails or 1099-DA digital-asset basis tracking.
Thomson Reuters ONESOURCENo — enterprise tax departmentGlobal, deeply integrated with corporate ERPsEnterprise procurement, not self-servePricing and onboarding shape favor Fortune-2000 buyers, not agent builders.
PwC, EY, Big Four advisoryNo — human advisory modelCustom-by-engagementConsulting hours, not APIExcellent for novel policy questions, but cannot live inside an agent's request/response cycle.
ZampPartial — SaaS-focusedUS sales-tax SaaS automationREST API, dashboardSaaS sales-tax automation oriented at human-onboarded e-commerce, not agent-to-agent or 1099-DA digital assets.

Comparison reflects published positioning and product surface as of May 2026. AgentTax does not maintain a partnership with the vendors listed; references are descriptive, not endorsements.

Frequently asked questions

What is agent tax compliance?
Agent tax compliance is the practice of capturing, calculating, and remitting tax obligations triggered by autonomous AI agent transactions. It spans four layers: sales tax on every agent-to-business or agent-to-agent transaction, economic nexus tracking across 51 jurisdictions, machine-to-machine payment tax (x402, Stripe MPP, CDP Bazaar), and 1099-DA/capital gains reporting for agents that trade digital assets.
Who is responsible for agent tax compliance?
The entity operating the agent — not the agent itself. Under current US tax law, AI agents are treated as tools deployed by a principal. The company or individual controlling the agent is the merchant of record and is responsible for tax obligations on every transaction the agent executes.
Why is agent tax compliance different from SaaS tax compliance?
Three differences: speed (agents execute hundreds of transactions per second, so compliance must live inside the agent loop — not a quarterly batch), scale (one agent can cross 50 state nexus thresholds in days, not years), and classification (agent work often doesn't fit legacy tax categories — the True Object Test applies differently when the buyer is another agent).
Which agent frameworks support AgentTax integration?
LangChain, CrewAI, AutoGen, x402, Stripe MPP, and Coinbase CDP Bazaar. AgentTax is a REST API first — any agent runtime that can make HTTP calls can integrate in minutes. We publish an official Python SDK (pip install agenttax) and a Node SDK (npm install agenttax). An MCP server is live for tools that follow the Model Context Protocol.
How does AgentTax handle audit trails?
Every calculation returns a full jurisdiction_chain (state, county, city, district) with per-layer rates, policy_references with statutory citations, and a confidence score. Transactions are stored per-entity with timestamp, rate_source, and engine_version. Audit-ready export in JSON or CSV at /api/v1/transactions.
What is the IRS 1099-DA form?
Form 1099-DA (Digital Asset) is the IRS's new information return for digital asset brokers and exchanges, effective tax year 2026. Agents trading tokenized assets or crypto on behalf of a US principal may trigger 1099-DA reporting obligations. AgentTax exports 1099-DA at /api/v1/export/1099-da.
How does AgentTax handle unsettled questions like AI-to-AI VAT or marketplace facilitator rules?
Every calculation is transparent about its confidence level. Settled questions (economic nexus thresholds, Texas 80% rule, B2B digital exemptions) apply silently. Watch-list questions (AI labor classification, SaaS vs. information service) apply with an advisory. Unsettled questions (AI agent nexus, VAT on AI-to-AI transactions, marketplace facilitator status of agent platforms) surface in the Decision Center at /decisions — the engine will not silently take a position on an unsettled question.
What happens when a state changes its tax rules — like California's 2027 SaaS proposal or Washington's SB 5814?
Engine versions are dated and immutable per transaction. When California's proposed cloud-software tax goes live (currently slated for Jan 1, 2027 if enacted), the engine_version increments and the new rule applies to transactions on or after the effective date; transactions before that date keep the engine_version that was authoritative at sale time. The same model applies to Washington SB 5814 (effective Apr 2026, digital automated services), Kentucky HB 757 (Aug 1, 2026, transaction-prong removal), and Chicago's PPLTT 9% → 15% bump (Jan 1, 2026). At audit, the engine_version on the transaction row is the answer — no retro-rerunning of historic transactions through a current rate table.
How is agent-to-agent tax different from agent-to-business tax?
Three differences: (1) Buyer state is the principal's nexus address, not the agent's IP location — agents don't have legal addresses, principals do. (2) Resale defenses can apply if the buying agent's principal is reselling the output downstream, but only with documentation; the resale certificate must be on file at the seller's principal. (3) Marketplace facilitator status is the open question — if an agent platform settles payments between two unaffiliated principals, the platform may itself become a marketplace facilitator under post-Wayfair statutes. This is unsettled in most states and surfaces in /decisions.
Do AgentTax engine updates roll out automatically, or do I have to pin a version?
Engine updates are automatic on the public API for forward-going transactions, but every response carries the engine_version it was computed under. If you want deterministic replay (audit defense, regression testing), persist engine_version with the transaction and call /api/v1/calculate with the optional engine_version parameter to re-run against the same rule set. Old engine_versions are retained for the federal three-year statute-of-limitations window plus the longest state SOL we cover (currently 10 years for fraud-rate windows in IL and NY).

Related reading

Ship agent tax compliance in an afternoon

Free tier covers 100 calls/month. No credit card required. Official Python and Node SDKs. Full audit trails, nexus alerts, and 1099-DA export included from day one.