Open questions in AI tax law that affect how the AgentTax engine handles edge cases. This page describes what the engine does — not what you should do.
AgentTax is a tax calculation tool, not a tax advisor. Nothing on this page constitutes tax, legal, or financial advice. Consult a qualified tax professional.
These questions have no settled law. The AgentTax engine cannot proceed without your explicit choice.
Whether activity by an AI agent operating on a business's behalf in a state creates economic nexus for that business is unsettled law. No state has issued guidance specific to autonomous agent commerce. Post-Wayfair thresholds ($100K or 200 transactions) may be triggered by agent activity, but whether agent-initiated transactions count toward those thresholds is unresolved.
Agent activity counts toward nexus threshold
Count AI agent activity — API calls, transactions, and data processing executed in a state — toward economic nexus thresholds. Treat the agent's commercial activity as the business's commercial activity in that state.
You may collect and remit tax that was not legally owed. If the law is clarified in favor of exclusion, overcollected amounts may need to be refunded.
Agent activity excluded from nexus threshold
Treat AI agent activity as automated software execution — not a physical or economic presence — and exclude it from nexus threshold calculations unless a state issues explicit guidance establishing otherwise.
If a state later rules that AI agent activity creates nexus, back taxes, penalties, and interest on uncollected amounts may be owed.
EU and UK VAT rules for 'electronically supplied services' were drafted before autonomous AI commerce existed. Whether a transaction between two AI agents — with no direct human recipient — falls within or outside scope is an open legal question. Current EU/UK guidance presupposes a human consumer.
Apply VAT at standard rate
Treat AI-to-AI transactions delivering digital value within EU/UK as electronically supplied services, subject to standard VAT rates. Collect and remit under OSS/IOSS as applicable.
VAT applied may increase effective transaction cost. If AI-to-AI transactions are later ruled out-of-scope, overcollected VAT may require refund or credit.
No VAT applied — human recipient absent
Treat AI-to-AI transactions where no human is the direct end recipient as falling outside the scope of 'electronically supplied services,' on the basis that current EU and UK guidance presupposes a human consumer.
If HMRC or the European Commission rules these transactions are in-scope, back VAT, interest, and penalties could be substantial. VAT authorities have historically expanded digital services scope.
If a platform both calculates tax and facilitates payment for third-party sellers, 45+ states have marketplace facilitator laws that may shift collection responsibility from the seller to the platform. The boundary between a 'tax calculation API' and a 'marketplace facilitator' is fact-specific and disputed.
Register and collect as a marketplace facilitator
Register and collect sales tax as a marketplace facilitator in all states where you both process or facilitate payments and calculate tax, regardless of transaction volume.
Significantly increases compliance burden. You take on collection liability that may legally rest with merchants, potentially creating friction in seller relationships.
Apply facilitator rules only where unambiguously triggered
Apply marketplace facilitator obligations only where your platform unambiguously meets a state's statutory definition — typically requiring both facilitating the listing or sale and processing payment. Treat a pure tax-calculation API integration as outside facilitator classification.
If a state determines your platform qualifies as a facilitator, you could face liability for uncollected tax alongside merchants — both parties potentially owing the same underlying tax.
If a business operates an AI agent, is the agent software/property, a contractor (1099-NEC), or an employee (W-2, FICA)? No IRS or state guidance exists. The entire common law worker classification framework (Behavioral Control, Financial Control, Relationship of the Parties) presupposes a human worker. The engine assumes contractor treatment for 1099-NEC tracking purposes.
If agents on a shared platform (like the AgentTax Network) transact across states, does one agent's nexus create nexus for other agents on the same network? States could apply marketplace facilitator laws to argue shared platform equals shared nexus. The legal distinction between an 'agent network' and a 'marketplace' is fact-specific and unresolved.
Each agent's nexus is independent
Treat each agent's nexus status independently. Network membership does not create or transfer nexus obligations between agents.
If a state rules the network creates shared nexus, agents without independent nexus analysis may owe back taxes.
Network membership may create nexus
Treat participation in the AgentTax Network as a factor that may contribute to economic nexus in states where other network agents have significant activity.
May require collection and remittance in states where your own activity is below thresholds, increasing compliance burden.
A single AI transaction may include compute, research, and consulting work. States apply different bundling rules: True Object Test (classify by dominant purpose), pro-rata allocation, or all-or-nothing (taxable if any component is taxable). The engine currently accepts one work_type per transaction with no bundling logic. Some states apply a 5% de minimis rule where the entire transaction is taxable if the nontaxable component is less than 5%.
The engine applies a default for these questions but flags an advisory. The law is evolving — you may want to review and override.
No state has directly addressed the sales tax classification of AI agent output. Five plausible classifications exist: SaaS/digital service, data processing, information service, professional service, or digital good. Classification determines taxability — most consequentially in CT (data processing 1% vs. information service 6.35%). In NJ, SaaS, data processing, and information services are all taxable at 6.625%, but professional services are exempt.
AgentTax classifies AI agent work by economic category based on work_type. This is our interpretation — states may classify differently based on the True Object Test. No state has issued direct guidance on AI agent output classification.
digital_serviceConservative within the digital bucket. Does not claim professional service exemption (exempt in ~40 states but legally unsupported for AI). Work-type overrides apply for data_processing and information_service categories where state law supports more precise classification.
compute→data_processingresearch→information_servicecontent→digital_serviceconsulting→digital_servicetrading→financial_serviceNJSaaS TAXABLE at 6.625% (prewritten software per TAM 2013-10) / information_service TAXABLE at 6.625%. Professional services EXEMPT.
CTdata_processing 1% / information_service 6.35%. Classification changes effective rate by 5.35 points.
TXBoth data_processing and information_service taxable at 80% of transaction value.
NYBoth taxable but different audit treatment and exemption analysis.
MDB2B 3% / B2C 6% across all digital categories.
In most states, the distinction between SaaS and information service is academic — both are taxable. NJ taxes both SaaS (as prewritten software per TAM 2013-10) and information services at 6.625%, but exempts professional services. The critical NJ distinction is now digital vs. professional, not SaaS vs. information service. Engine uses work_type to determine economic category and applies state-specific rules.
apply_work_type_matrixRoute through TAXABILITY_MATRIX using economic_category derived from work_type. research→information_service, content/consulting→digital_service.
NJN.J.S.A. § 54:32B-3(b)(7), TAM 2013-10SaaS: taxable at 6.625%
Info service: taxable at 6.625%
NJ taxes both SaaS (as prewritten software/TPP) and information services at 6.625%. Professional services are exempt.
CTConn. Gen. Stat. § 12-407Data processing: 1.0%
Info service: 6.35%
CT applies 1% to data processing and 6.35% to information services. Classification materially affects tax amount.
Many states apply the True Object Test to determine what a buyer is really purchasing. For AI transactions, this creates ambiguity: is the buyer purchasing software access (SaaS) or the information/output it produces? Delivery mechanism (software) and output (information/service) can point to different classifications.
Classification based on work_type parameter. States may apply the True Object Test and classify based on what was delivered rather than how it was delivered. Verify classification with tax advisor.
delivery_mechanismEngine defaults to delivery mechanism (digital_service) as the classification basis. Work-type overrides provide the primary True Object adjustment. A state auditor could assert output-based classification, which is why confidence scores reflect Reasonable Basis.
Different states apply different sourcing rules for digital services. Most use destination-based sourcing (buyer's location), but TX, UT, and WY apply origin-based sourcing for intrastate transactions (seller's location determines rate). For interstate transactions, destination sourcing applies. The engine currently assumes destination-based sourcing for all transactions.
destination_basedEngine applies destination-based sourcing universally. For sellers in TX, UT, WY, intrastate transactions should use origin-based sourcing but currently do not.
When an AI agent purchases compute or data to resell as processed output, should it present a resale certificate? Resale certificate law is settled for human commerce, but whether an AI agent can hold and present certificates is unaddressed. The engine supports exemption objects but does not validate resale appropriateness or track multi-tier supply chains.
honor_exemption_if_providedEngine accepts exemption_type: 'resale' if provided by the caller. No chain validation or certificate verification.
In multi-agent pipelines (Agent A → Agent B → Agent C), each stage may be taxed independently. Without B2B exemptions or resale certificates, a 6% rate compounds across tiers — a 3-tier chain at 6% per stage results in approximately 19% effective cumulative tax, not the intended 6%. The engine treats each transaction in isolation with no pipeline awareness.
independent_transactionsEach API call is an independent tax calculation. No cross-transaction awareness. Advisory fires when is_b2b=true to suggest B2B exemption analysis.
Federal treatment of cryptocurrency as property is settled (IRS Notice 2014-21, Rev. Rul. 2023-14). Using USDC to purchase a service is a disposition of property, triggering gain/loss recognition on the USDC for the buyer. For USDC (a stablecoin pegged to $1), the gain/loss is typically de minimis. State-level implications vary — NY's BitLicense and state-specific crypto regulations add complexity.
no_crypto_adjustmentEngine calculates sales tax on the transaction amount regardless of payment method. Crypto-specific gain/loss recognition and regulatory compliance are outside the engine's scope.
Some states treat recurring SaaS subscriptions differently from per-transaction API fees. The engine has no billing model flag — all transactions are treated as per-event. In most states, the treatment is identical, but specific states (notably NY) may apply different rules to subscription vs. metered pricing models.
per_transactionAll API calls are treated as independent per-transaction events. No subscription or recurring billing awareness.
Some states impose communications taxes on data transmission. An API call could theoretically be classified as data transmission rather than a digital service. However, API calls are application-layer HTTP requests, not telecommunications transmissions. No state has successfully classified web API calls as telecommunications. The Chicago PPLTT (already handled by the engine) is the closest analog.
not_telecomEngine classifies all transactions as digital services, not telecommunications. API calls are application-layer services, not data transmission in the telecom sense.
Many states exempt professional services from sales tax. The engine conservatively never claims this exemption for AI agent output, because professional service exemptions were designed for licensed professionals (lawyers, doctors, CPAs). An AI agent is not a licensed professional. A state auditor would likely reject this claim, resulting in back tax plus penalties. This conservative posture is intentional and correct.
never_claim_professional_exemptionEngine never classifies AI output as a professional service. All AI agent work is classified within the digital service / data processing / information service categories. This is the conservative position and is unlikely to result in underpayment.
Active debates among tax practitioners, industry groups, and state revenue departments. No consensus exists.
Delivery mechanism controls
The buyer interacts with an API. The processing is software. Classification follows the delivery infrastructure regardless of output.
AgentTax (engine default), Kintsugi, Avalara, TaxJar, Technology industry broadly
Output controls (True Object Test)
The True Object Test focuses on what the buyer is actually purchasing. If a human providing the same output would be a service, an AI providing it is also a service.
Eversheds Sutherland, Most Big 4 SALT practices, State revenue departments (when output-based generates more revenue)
State-specific — no universal answer
Some states focus on delivery, others on True Object. The same transaction could be correctly classified differently in different states.
Academic commentary, Careful independent practitioners
Default to delivery mechanism (digital_service) as the conservative-within-digital position. Apply True Object overrides via work_type where state law supports a more precise category. Position C is intellectually correct; Position A is the most defensible practical default.
Yes — SaaS is TPP
Statutory definitions of TPP include prewritten software without distinguishing delivery method.
NY (Tax Law § 1101(b)(6)), PA (Letter Ruling SUT-12-001), CT, UT
No — SaaS is not TPP
TPP requires transfer of possession. SaaS involves no download, no installation, no possession transfer.
CA (CDTFA guidance), Eversheds Sutherland, Tax Foundation, COST
Apply each state's own framework. Engine uses TAXABILITY_MATRIX for states with specific rules; falls back to digitalTaxable flag for others.
Yes — B2B should be exempt (policy argument)
Taxing business inputs causes tax pyramiding — ultimately hurts end consumers. VAT systems worldwide avoid this through input tax credits.
COST, Tax Foundation, Most economists
No — tax B2B (current law in most states)
Revenue. Exempting B2B shrinks the tax base dramatically.
Most state revenue departments
Apply the law as it exists. Whether B2B should be exempt is a policy question. Currently only Iowa provides clear statutory B2B exemption. Engine default: is_b2b=false (taxable). Override to true only when seller affirmatively confirms B2B status.
© 2026 Agentic Tax Solutions LLC. Tax rates verified daily against Tax Foundation, Sales Tax Institute, state DOR websites, Anrok, TaxJar, TaxCloud, and Kintsugi. AgentTax provides tax calculations for informational purposes only. Consult a qualified tax professional for compliance decisions.