Payment Required, governed before the agent acts

HTTP 402 for AI Agents

HTTP 402 is becoming the handshake between autonomous agents and paid APIs. The protocol can request payment; SatGate decides whether the agent has authority to spend, access, and continue — then preserves proof of the decision.

What HTTP 402 means in an agent world

For years, HTTP 402 Payment Required was mostly dormant. AI agents make it useful: a paid API can respond with a machine-readable challenge instead of forcing a human through checkout.

That challenge may point to different payment methods: card-based credentials, shared payment tokens, invoices with payment details, or future protocols. But the payment challenge is not the governance layer.

On a paid route SatGate checks the agent's token and permissions, asks for payment in the methods you allow, and lets the request through only after the payment checks out.

A 402-aware control plane asks

Which payment method is being requested?
Is this route approved for delegated paid access?
Does the agent have authority and budget?
Should policy require human approval?
Which payment method is being requested, and is it allowed by policy?
What signed receipt should be recorded before forwarding?

HTTP 402 flow types

Treat 402 as a protocol surface, not a single payment system. L402 is one payment method; x402, AgentCore Payments, Pay.sh, and payment-token flows are separate payment methods that still need governance.

Flow
How it works
SatGate implication
Card checkout
Agent receives a temporary card credential and fills a merchant checkout.
Good for web purchases, but not request-native API monetization.
x402
API returns a 402 payment challenge for USDC on Base.
x402 payments still pass SatGate’s permission checks. AgentCore Payments and Pay.sh are planned.
Shared payment token
Agent receives a payment token for a supported 402 machine-payment flow.
Specific to one payment method; treat it as a subpattern of payment details that still needs governance.
L402 (Lightning)
API returns a Lightning-backed 402 challenge and verifies proof before access.
L402 can support request-native paid API access; SatGate governs the decision and receipt.

Where SatGate fits in a 402 exchange

Agent requests

An agent calls a paid API, model endpoint, MCP tool, or dataset.

SatGate evaluates

Policy checks identity, scope, budget, route, tenant, and allowed payment method.

402 is handled

On a paid route, SatGate answers with a 402 that says how to pay, and checks the payment before letting the request through.

Access is governed

Only approved, scoped, metered, auditable access proceeds upstream.

L402 is a payment method, not the governance layer

Payment details can carry payment proof: an API returns a 402 challenge, the agent or wallet client pays a Lightning invoice, and proof unlocks scoped access. SatGate evaluates the action before payment/access and records proof after the decision.

Other 402 payment methods still need policy

Stripe-style shared payment tokens, card credentials, and future payment protocols can help platforms delegate paid access to agents. They do not replace controls before the request goes through for budget, scope, revocation, metering, receipts, or signed receipt proof.

FAQ

HTTP 402 for AI agents questions

What is HTTP 402 for AI agents?

HTTP 402 lets an API tell an AI agent that payment is required before access. The response can include a machine-readable challenge describing how to pay.

Is HTTP 402 the same as L402?

No. HTTP 402 is the status code. L402 is a Lightning payment and access method that uses HTTP 402, and SatGate can govern it before the request goes through.

How are Stripe shared payment tokens different from L402?

Stripe-style shared payment tokens are a payment-credential method for supported 402 flows. L402 uses Lightning payment proof to unlock scoped API access. They are separate payment methods.

Why do 402 payment challenges need policy?

A payment challenge tells the agent how to pay, but it does not decide whether the agent should be allowed to spend, which budget applies, whether the route is in scope, or how the event should feed the signed receipt (Evidence Pack).

Related guides

Govern paid agent access before the agent acts

HTTP 402 can carry payment context. SatGate turns that context into governed action: authority, policy, budget and proof. SatGate signs a receipt when it refuses an agent for a missing payment.