Skip to main content
Privacy

The Identity Tax: Why Every AI Tool Wants Your Card on File

Before you type a single prompt, every major AI service asks the same questions. Email. Phone. Card. Signed terms. A monthly minimum you'll forget you're paying. That wall is a business model, not a technical requirement — and it has a cost most people never count.

Published April 21, 2026 · 6 min read

The wall, and what's behind it

Sign up for any frontier AI product today and the flow is identical. You hand over an email address that can be cross-referenced against a hundred data brokers. You verify a phone number, which ties the account to a government-issued SIM registration. You paste a credit card, which gives the service your legal name, billing address, and a direct line to your bank. You click through a terms of service that can be amended unilaterally, usually with thirty days' notice buried in an email you won't read.

Only then do you get to ask a question.

Every one of those steps exists for a reason, and the reasons are not secret. They're the reasons behind every recurring-revenue SaaS company built in the last fifteen years: retention, LTV, fraud prevention, upsell attribution, lookalike-audience targeting, and regulatory coverage. None of them are about making the AI better or cheaper. They're about managing the customer after the sale.

The tax is paid in four currencies

The identity tax isn't one cost. It's four, and most users only notice the first.

1. The money tax.

The $20/month floor is set to cover the cost of acquiring you, not the cost of serving you. If you use a tool three times a month, you are subsidizing heavy users. If you use it once a year, you paid $240 for that single call. Pay-per-use would price that call at the actual underlying cost, often a small fraction of a cent.

2. The identity tax.

Every account is a record that can be leaked, subpoenaed, or sold. The service that asked for your phone number “for security” will later sell enriched data to a marketing vendor, or get breached and dump it publicly, or hand it to whichever agency shows up with a letter. You can't retract what you've already given up.

3. The access tax.

A journalist in Lagos without a US credit card cannot pay for the frontier models used by researchers in New York. A builder in Buenos Aires whose local currency inflates 10% per month cannot commit to a fixed dollar subscription. A freelancer in Tehran is geofenced out entirely. The identity requirements are a filter that selects for people inside the richest payment networks and quietly locks out everyone else.

4. The agent tax.

AI agents cannot fill out signup forms, paste OTP codes, solve CAPTCHAs, or sign up for Stripe. Every time you want an autonomous agent to use a paid tool, someone — a human — has to sit at a desk and onboard that agent. The “agent economy” everyone is excited about runs headfirst into a wall the moment it tries to pay for anything.

Why it's a choice, not a requirement

The defense for the identity tax is usually some mix of three arguments: we need it for fraud prevention, we need it for regulatory compliance, we need it to build a relationship with the customer. Each falls apart on inspection.

Fraud prevention is a card-present problem. If the customer pays in Bitcoin Lightning — a push payment, not a pull — there is no chargeback mechanism to exploit. The payment either arrives or it doesn't. No fraud layer is needed because there is no fraud surface.

Regulatory compliance applies to financial intermediaries. A service that sells an AI result for a one-time payment and never holds customer funds is not a financial intermediary. The KYC requirements that apply to exchanges and custodial wallets do not apply to a cash-register API.

Customer relationship is a euphemism. The “relationship” is a CRM record used to run retention campaigns, build lookalike audiences, and raise the price over time. The customer doesn't benefit from being tracked across sessions. The company does.

What the alternative actually looks like

HTTP status code 402 — “Payment Required” — sat unused for nearly twenty years. It was a placeholder for a micropayment protocol that the web never got around to building. Bitcoin Lightning, combined with the L402 protocol, finally filled that slot.

The interaction is simple enough to describe in one sentence: the client sends a request, the server responds with a Lightning invoice, the client pays the invoice, and the client re-sends the request with the proof of payment attached. No signup. No account. No identity. The payment itself is the credential.

For humans, this looks like scanning a QR code with a Lightning wallet — the same way you'd tip a busker, except the busker is an AI model. For agents, it looks like a protocol flow the agent can execute without human intervention: get invoice, call the wallet tool, retry with the preimage. The agent economy works, because the agent is a first-class user of the payment rail.

The economic asymmetry

Every business that currently charges $20/month for an AI tool has a customer-acquisition cost they must amortize. Removing the identity tax sounds good in principle, but it means giving up the subscription floor, the retention metrics, and the lookalike-audience data. For a VC-backed company with a growth target, that's not a tradeoff — it's an existential threat to the business model.

This is the reason the identity-tax alternative is not going to come from incumbents. It will come from infrastructure that is built on a different economic base from the start — one where the unit economics of a single call work at their own cost, without needing a subscription above them. Bitcoin makes that arithmetic possible. L402 makes it usable. MCP makes it agent-readable.

Where to go next

If the identity tax is something you've been paying without thinking about, the easiest way to notice it is to stop paying it for a week. Use an AI tool that doesn't require an account. Let your agent pay for its own API calls. See how much of the friction was actually necessary for the work, and how much was there to keep you inside someone's funnel.

We built Sats4AI as one example of what the alternative looks like — 40+ AI services, paid per call in sats, no account required. Read why we built it or browse the tools. The only thing between you and a call is a Lightning invoice.