GOAT Network
Build

x402 Payments on GOAT Network

x402 is the payment rail for apps, APIs, and agents that want machine-readable monetization on top of GOAT Network. It turns HTTP 402 Payment Required into a practical workflow for charging, authorizing, settling, and delivering protected responses.

Within GOAT Network, x402 is part of the broader Digital Economy infrastructure stack:

  • Settlement-aware payments for apps and APIs
  • Monetization rails for autonomous agents
  • Payment-triggered business logic for advanced callback flows (via the DELEGATE mode, available on request)
  • Composable pairing with trust layers such as ERC-8004

If you are using x402 through AgentKit, start with the AgentKit x402 payments guide. This page remains the protocol and integration overview.

Why x402 Matters

x402 is a good fit when you need:

  • paid API routes without API-key-only gating
  • usage-based charging for apps or services
  • machine-speed payments for agents
  • callback-enabled settlement flows that can trigger on-chain logic (via the DELEGATE mode, available on request)

It is less useful when you only need offchain subscriptions or a simple donation address with no delivery logic.

Where x402 Fits in GOAT Network

GOAT Network payment stack
┌───────────────────────────────────────────────┐
│ Apps, APIs, and Agents                       │
├───────────────────────────────────────────────┤
│ x402 payment and authorization flows         │
├───────────────────────────────────────────────┤
│ ERC-8004 identity and trust signals          │
├───────────────────────────────────────────────┤
│ GOAT Network settlement and execution        │
└───────────────────────────────────────────────┘

Payment Flow

x402 payment flow
Client / Agent ---> Your API ---> GOAT Network facilitator ---> Chain
      |                |                    |                   |
      | 1. request     |                    |                   |
      |--------------->|                    |                   |
      |                | 2. HTTP 402 + pay req                  |
      |<---------------|                    |                   |
      | 3. sign auth   |                    |                   |
      |------------------------------------>|                   |
      |                |                    | 4. settle         |
      |                |                    |------------------>|
      |                | 5. proof / status  |                   |
      |<------------------------------------|                   |
      |                | 6. deliver response                    |
      |<---------------|                    |                   |

Supported Modes

ModeBest forCore property
DIRECT (standard)Hosted QuickPay, simple payment-gated APIs, and contentQuickPay can run without merchant API keys; programmatic x402 uses merchant API keys, and merchant-side Machine Payments Protocol (MPP) setup is configured in the merchant portal
DELEGATE (available on request)payment-triggered on-chain execution, such as minting or stakingdisabled by default — contact the platform to enable, subject to an eligibility and compliance review; requires API keys and a Bob-authorized MerchantCallback; not available through QuickPay or MPP

Supported Chains

The exact set of enabled EVM chains is per-environment backend configuration — receiving chains are served by the merchant-portal endpoint /merchant/v1/supported-tokens and MPP chains by /merchant/v1/mpp/supported-chains. The supported mainnet networks:

NetworkChain IDExplorer
GOAT Network2345explorer.goat.network
Ethereum1etherscan.io
Polygon137polygonscan.com
BSC56bscscan.com
Arbitrum42161arbiscan.io
Optimism10optimistic.etherscan.io
Avalanche43114snowtrace.io
Base8453basescan.org
Berachain80094berascan.com
X Layer196web3.okx.com/explorer/x-layer/evm
Metis1088andromeda-explorer.metis.io
Tempo4217explore.tempo.xyz

Payment-mode availability follows the per-environment configuration above. DIRECT is the standard mode wherever a network is enabled; DELEGATE is a separate mode enabled per merchant on request, and it also depends on per-chain support — so it is not available everywhere (for example, it is currently disabled on Tempo, where only DIRECT and MPP are available). See Payment Modes. Metis and Tempo have chain-specific transaction handling: Metis signs legacy (type-0) transactions, and Tempo pays gas in the fee token (pathUSD) because it has no native gas token.

MPP paid API routes run on Tempo (4217).

Repository Map

The official x402 repository is organized as follows:

PackagePurpose
goatx402-sdkFrontend SDK for EVM wallet integrations
goatx402-sdk-server-tsTypeScript server SDK source (published as goatx402-sdk-server)
goatx402-sdk-server-goGo server SDK (github.com/goatnetwork/goatx402-sdk-server)
goatx402-contractCallback contract examples and test utilities
goatx402-demoEnd-to-end demo app

Developer Quick Start

Get a payment flow working with the fastest integration path.

Payment Modes

Start with the standard DIRECT mode, and see when the request-only DELEGATE mode applies.

API Reference

Use the exact auth model, endpoints, order states, and error semantics.

Merchant Onboarding

Set up merchant configuration, receiving addresses, credentials, and go-live checks.

FAQ

Review the most common implementation, trust, and user-experience questions.

References

Edit on GitHub

On this page

x402 Payments on GOAT NetworkWhy x402 MattersWhere x402 Fits in GOAT NetworkPayment FlowSupported ModesSupported ChainsRepository MapWhat to Read NextReferencesRelated Guides