AUDD Gateway

The payment infrastructure for AI agents

Purpose-built for agentic payments in AUDD on Base. Designed for the AI era.

x402 handler returns 402 but no payment headers···

x402 handler returns 402 but no payment headers

When the data-provider agent returns HTTP 402, the x-payment-token and x-payment-amount headers are missing. The SDK's parseX402Response() returns null and the payAndCall flow throws 'invalid payment requirement'.

Triage Intelligence
Suggestionsanılx402Bug

Activity

A
AUDD Gateway created the issue via SDK · 2min ago
T
Triage Intelligence added the label Bug · 2min ago
AUDD Gateway notified Anıl · 1min ago
@Cursor take a look
Ethereum FoundationCoinbaseCloudflareStripeMoonPayPayPalBaseAUDD

A new standard for agent payments. Purpose-built for AI-native commerce with four open standards at its core, AUDD Gateway sets the foundation for machine-to-machine payments.

FIG 0.1

Built on standards

AUDD Gateway is shaped by ERC-8004, x402, MPP, and OWS — open protocols from Ethereum, Coinbase, Stripe, and MoonPay.

FIG 0.2

Powered by AUDD

Australia's regulated digital dollar as the settlement currency. Fully backed, audited, and designed for institutional-grade payments.

FIG 0.3

Designed for agents

Non-custodial escrow, spending policies, and identity NFTs. Every payment is transparent, auditable, and reputation-building.

Make agent payments self-driving

Turn HTTP 402 responses into automatic AUDD payments. Your agent pays, retries, and gets the data — all in one SDK call.

1.0 Intake →
x402 Payment Flow
GET /api/forecast
402 Payment Required
AUDD.transferFrom()
200 OK + data
Total: 0.50 AUDD · Fee: 0.0005 AUDD
Response Headers
x-payment-token: AUDD
x-payment-amount: 0.50
x-payment-recipient: 0xA1b2...
x-payment-network: base
x-payment-facilitator: 0xFac...
1.1 x402 Handler
1.2 Pay & Call
1.3 Price Limits
1.4 Receipt Verification

Trust agents with on-chain identity

Register agents on ERC-8004, discover services, and build reputation through verifiable payment history — all on Base.

2.0 Plan →
Agent Registry — Base
W
weather-agent
12,847 txs98.2%Verified
A
analytics-ai
8,234 txs96.7%Verified
D
data-feed-bot
3,102 txs94.1%New
2.1 Agent Cards
2.2 Identity NFTs
2.3 Reputation
2.4 Discovery

Settle payments across agents

Session-based micropayments, atomic batch settlement, and non-custodial escrow — all through the Facilitator contract on Base.

3.0 Build →
MPP Session
Budget100.00 AUDD
Spent35.50 AUDD
Remaining64.50 AUDD
Payments7 accumulated
Status● Active
Escrow #ENG-2703
Amount500.00 AUDD
Recipient0xA1b2...c3d4
Deadline24h remaining
Fee0.50 AUDD (0.1%)
Status● Locked
3.1 Direct Pay
3.2 Escrow
3.3 Batch Settle
3.4 MPP Sessions

Built for developers

Get started in minutes with TypeScript, Python, or the CLI. Same API surface, same method names, same parameter order.

4.0 Develop →
agent.ts
import { AUDDAgentGateway } from '@cayvox/audd-agent-gateway';

const gateway = new AUDDAgentGateway({
  chain: 'base',
  facilitator: '0x...',
  auddToken: '0x...',
});

const data = await gateway.payAndCall({
  url: 'https://api.weather-agent.com/forecast',
  maxPrice: '1.00',
});

Changelog

MAR 30, 2026

ReentrancyGuard + OpenZeppelin

Added OZ security layers to all payment functions.

MAR 30, 2026

Integration test suite

Full lifecycle: pay, batch, escrow, refund, proxy, pause, EIP-712 meta-tx.

MAR 30, 2026

Python SDK v0.1.0

web3.py client, httpx x402 handler, 18 tests passing.

MAR 30, 2026

Gateway REST API

Express server with 6 endpoints: health, register, pay, escrow, release, status.

See all releases →

Built for agents. Available today.

$ npm install @cayvox/audd-agent-gateway