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
  • 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

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
DIRECTsimple payment-gated APIs and contentuser pays merchant address directly
DELEGATEadvanced workflows with settlement orchestrationpayment can trigger callback-enabled business logic

Developer Quick Start

Get a payment flow working with the fastest integration path.

Payment Modes

Choose between DIRECT and DELEGATE before you design your integration.

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.

Edit on GitHub

On this page

x402 Payments on GOAT NetworkWhy x402 MattersWhere x402 Fits in GOAT NetworkPayment FlowSupported ModesWhat to Read NextRelated Guides