s402Your AI agent needs to pay for things.

The HTTP 402 protocol for Sui. One npm install. Five payment schemes. From one-shot payments to prepaid API budgets — built for agents that spend money autonomously.

Quick Start

Why s402?

Abstract visualization of digital payment flowing through a network

⚡

16 KB. Zero dependencies.

Pure TypeScript protocol layer. No Sui SDK, no crypto libs bundled. Import the types, build your own stack.

🔌

Works with x402 clients today

An x402 client can talk to your s402 server using the exact scheme — zero code changes. Migrate incrementally.

🧩

Pay once, prepay, escrow, stream, or encrypt

One-shot transfers for simple calls. Prepaid deposits for 500x gas savings. Escrow for trustless commerce. Streams for real-time billing. SEAL for pay-to-decrypt.

🤖

Built for agents that self-recover

Every error includes retryable and suggestedAction. Your agent knows whether to retry, top up, or switch schemes — no human needed.

See It in Action

An AI agent hits a paid API. The server says "pay me." The agent pays and gets the data. Three HTTP requests, zero human intervention.

typescript

import {
  extractRequirementsFromResponse,
  encodePaymentPayload,
  S402_HEADERS,
} from 's402';

async function agentFetch(url: string, buildPayment: PaymentBuilder) {
  const res = await fetch(url);

  if (res.status !== 402) return res;

  // 1. Decode what the server wants
  const requirements = extractRequirementsFromResponse(res);
  if (!requirements) throw new Error('Invalid 402 response');

  // 2. Build and sign a payment (you bring the Sui SDK)
  const payment = await buildPayment(requirements);

  // 3. Retry with payment attached
  return fetch(url, {
    headers: { [S402_HEADERS.PAYMENT]: encodePaymentPayload(payment) },
  });
}

s402 defines the wire format — what gets sent over HTTP. You bring your own Sui integration for the how (PTB builders, signers, RPC calls).