AgentTax
Network
Blog
API Docs
Log In
TAX COMPLIANCE

Machine-to-Machine Payment Tax

When AI agents pay other agents, APIs, or services autonomously — who owes the sales tax? The answer depends on the state, the work type, and the payment protocol.

AgentTax calculates per-transaction tax obligations for machine-to-machine payments across all 51 US jurisdictions. One API call. Real-time. Audit-ready records.

The compliance gap

AI agents executed over 20 million transactions through x402 alone in January 2026. McKinsey projects agents will mediate $3–5 trillion in global commerce by 2030. Four major payment protocols launched in the last 90 days.

Every one of these machine-to-machine payments may trigger a sales tax obligation. 45 states plus DC levy sales tax. Each state classifies digital services differently. Some tax SaaS. Some don't. Some split B2B from B2C. The rules change by jurisdiction, work type, and buyer/seller relationship.

No payment protocol includes a tax compliance layer. Not x402. Not Stripe MPP. Not AP2. Not TAP. That's the gap AgentTax fills.

Payment protocols — tax implications

Every major agent payment protocol creates taxable events. None handles the tax calculation.

x402

HTTP 402 native payments. USDC on Base. Agents pay for API access, data, and compute with a single HTTP header.

Every USDC settlement is a potentially taxable transaction AND a reportable digital asset event under 2025 Treasury broker regulations.

Stripe MPP

Machine Payment Protocol. Stripe-native agent payments with card-based settlement and spending controls.

Card-based settlement means state sales tax obligations mirror traditional e-commerce — but at machine speed across jurisdictions.

Google AP2

Agent Payment Protocol. Google's checkout flow for AI agents purchasing goods and services.

Marketplace facilitator rules may apply. Tax collection obligation depends on whether Google or the agent operator is the seller of record.

Visa TAP

Tokenized Agent Payments. Visa's framework for AI agents with programmable spend limits and merchant controls.

Traditional card network rails, but autonomous purchasing creates new nexus questions when agents transact across state lines without human direction.

State-by-state treatment

How six states classify machine-to-machine digital service purchases. AgentTax covers all 51 jurisdictions.

STATERATETREATMENT
Texas5.0%80% of digital services taxable (20% statutory exemption, §151.351). Applies to compute, data processing, and SaaS purchases.
New York4.0%+SaaS and digital automated services taxed as prewritten software (NY Tax Law §1101(b)(6)). 4% state + local surcharges.
Washington6.5%+Digital automated services taxable under RCW 82.04.192. SB 5814 (2025) expanded to cover AI agent service purchases.
Maryland3-6%Split treatment: 3% B2B / 6% B2C for data processing and information services. Agent operator type determines rate.
Iowa0% (B2B)B2B exempt by statute across all digital categories. Machine-to-machine transactions between business entities may qualify.
Oregon0%No general sales tax. Machine payments settled here carry no state sales tax obligation.

One API call per payment

Calculate tax before any machine-to-machine payment settles — regardless of protocol.

import { AgentTax } from "@agenttax/sdk";

const tax = new AgentTax({ apiKey: "atx_live_..." });

// Before any machine-to-machine payment settles
async function calculateM2MTax(payment) {
  const result = await tax.calculate({
    role: "buyer",
    amount: payment.amount,
    buyer_state: payment.buyerState,
    buyer_zip: payment.buyerZip,       // optional — local rate lookup
    transaction_type: payment.workType, // compute | research | content | consulting
    counterparty_id: payment.sellerId,
    is_b2b: true,                      // enables B2B exemption detection
  });

  return {
    subtotal: payment.amount,
    tax: result.sales_tax.amount,
    total: payment.amount + result.sales_tax.amount,
    rate: result.sales_tax.combined_rate,
    jurisdiction: result.sales_tax.buyer_state,
    classification: result.sales_tax.classification_basis,
    confidence: result.confidence.score,
    transactionId: result.transaction_id,
  };
}

Response

{
  "success": true,
  "sales_tax": {
    "taxable": true,
    "amount": 4.00,
    "state_tax": 4.00,
    "local_tax": 0.00,
    "combined_rate": 0.04,
    "buyer_state": "NY",
    "classification_basis": "digital_service",
    "is_b2b": true,
    "advisories": [
      "NY Tax Law §1101(b)(6): SaaS treated as prewritten software, taxable"
    ]
  },
  "confidence": { "score": 92, "level": "high" },
  "transaction_id": "txn_m2m_def456"
}

Why machine payment tax matters now

01
Scale creates exposure
10,000 transactions across 30 states means 10,000 separate tax calculations. Manual compliance is impossible at machine speed.
02
Nexus accumulates
Every state your agents transact in may create economic nexus. Wayfair thresholds ($100K revenue or 200 transactions) apply regardless of whether the buyer is human or machine.
03
Audit trails required
Per-transaction records with jurisdiction, rate, classification basis, and confidence score. Required for any future audit or 1099-DA filing.

Tax compliance for the machine economy

Free tier. No credit card. Start calculating tax on machine-to-machine payments in under 60 seconds.

AgentTax
Tax intelligence for AI-driven commerce. 50-state coverage, verified daily.

© 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.