Private payments
for autonomous agents

Confidential x402Early access

TACEO brings confidential settlement to agent-to-API payments.
Amounts and assets stay hidden and every payment stays verifiable.

Let's talk

HTTP 402: Payment Required

What is x402?

x402 is the emerging standard for paying APIs on the fly.

It uses HTTP 402, the “Payment Required” status code that has sat unused in the spec since 1997, to turn a paid API call into a single round trip. The client requests, the server quotes, the client pays, the server delivers.

Autonomous agents need this.

They don't have pre-funded accounts at every API they might call. x402 lets them pay-as-they-go on public rails, with no relationship to negotiate up front. It is becoming the default payments protocol for the agent stack.

Why confidential x402

Why confidentiality matters
for agent payments.

Public rails expose everything.

Every API your agent calls. Every counterparty it transacts with. Every price it accepts.

x402 protocol
HTTP request - 402 quote - payment header - response
Value transfer routes here
TACEO Merces
Private accounts - encrypted balances - operator-blind execution
Settlement verified onchain

Shared infrastructure

How confidential x402 extends TACEO Merces.

Connect to TACEO Merces

Confidential x402 is x402 with an integrated privacy layer.

The payment headers, the facilitator handshake, the onchain settlement: all unchanged. The value transfer itself routes through TACEO Merces: private accounts, encrypted balances, operator-blind execution.

Confidential x402 is the agentic-finance surface of TACEO Merces. The accounts that pay an API are the same accounts that hold a stablecoin issuer's institutional balances. The compliance levers are the same levers: screening, disclosure on authorised request, and your own stack or Predicate.

Confidential transfers encrypt the asset and the amount. Sender and recipient remain visible onchain, which is what regulated counterparties generally need. Private transfers, which encrypt all four, are on the roadmap for agent payments.

The TACEO Network execution is the same execution.

How the TACEO Network works

Integration

A drop-in replacement
for the x402 client & facilitator.

Same call shape, same HTTP semantics, encrypted state behind them. The agent-side change is the client SDK;
the API-side change is the facilitator endpoint.

The wire format is compatible.

Design partnerships

Early access through
design partnership

for teams building agents now.

The specification
Direct work with the protocol team
Guided integration

The protocolPeer-reviewed

Proving the
security protocol.

Confidential x402 inherits its security model from TACEO Merces, published as IACR ePrint 2026/850, with a full UC security proof.

What carries over from TACEO Merces

Merces paper

300 TPS
With proof, on a CPU instance
Single-digit cent
gas on L2
Operator-blind
No plaintext access, ever

Confidential solutionExplore finance

TACEO Merces

Private balances and confidential transfers, with compliance and audit controls built in. Confidential x402 is one capability of TACEO Merces; the full protocol also covers institutional payments and DeFi composability, with a published UC security proof.

Moving agent payments
on public rails?

Let's design your integration together.

Talk to us

Read the x402 docs Read more about x402 on Core