# FareSide

FareSide is a hosted x402 facilitator and infrastructure service for AI agent payments, it lets API providers accept autonomous machine-to-machine payments using the [x402 protocol](https://x402.org) — an open standard built on HTTP status code 402. When an AI agent requests a paid resource, the server responds with 402, the agent signs a payment voucher, and a facilitator (FareSide) verifies and settles it on-chain. The server never manages blockchain complexity; FareSide handles it.

What FareSide Provides:
- Hosted Facilitator — Verifies payment payloads and settles transactions on-chain on your behalf, never holds funds, only executes signed transactions
- Reliable Settlement — Smart nonce management, automatic gas bumping for stuck transactions, and multi-RPC failover, stayed online during ecosystem-wide surges, briefly handling 77% of all x402 traffic
- Omni-Chain — Accept payments on all EVM chains (Base, Polygon, Avalanche, Sei, XDC...), Solana, Aptos... Users pay on any chain, you settle where you want
- Open Protocol, No Lock-in — Standard x402 spec. Switching facilitators is just changing an endpoint. Built on [x402-rs](https://github.com/x402-rs/x402-rs), a fully open-source Rust implementation

Use Cases:
- API Monetization — Per-call payments for any metered service (data, AI queries, storage) without accounts or API keys
- Multi-Party Payments — Revenue splits, referral fees, marketplace commissions routed to multiple recipients automatically
- Cross-Chain Services — Accept on any chain, settle where profitable, no manual bridging
- Custom Settlement Logic — Token issuance, loyalty points, escrow, refunds

# Documentation

- [Welcome to FareSide](/docs/welcome.md): x402 infrastructure: open-source tools and managed services for AI agent payments
- [Quickstart](/docs/quickstart.md): Accept your first x402 payment in 5 minutes
- [Supported Networks](/docs/supported-networks.md): Chains and tokens supported by FareSide
- [Dashboard](/docs/dashboard.md): Monitor payments, manage organizations, and get your API key
- [Setup Guide](/docs/setup-guide.md): Get your FareSide API key and configure your integration
- [Hono / Express / Next.js](/docs/express-hono-nextjs.md): TypeScript integration examples for popular frameworks
- [Rust (Axum)](/docs/rust-axum.md): Rust integration with Axum framework using x402-axum
- [Making Payments](/docs/making-payments.md): Learn how to build x402 clients that can pay for services
- [EVM Asset Transfer Methods](/docs/evm-asset-transfer-methods.md): How EIP-3009 and Permit2 transfers work in x402 on EVM chains
- [Upto Scheme](/docs/upto-scheme.md): Usage-based payments with maximum amount authorization
- [EIP-2612 Gas Sponsoring](/docs/eip2612-gas-sponsoring.md): Gasless Permit2 approval for ERC-20 tokens with EIP-2612 support
- [Self-Hosting](/docs/self-hosting.md): Run your own x402 facilitator with x402-rs
- [Build Your Own Facilitator](/docs/build-your-own-facilitator.md): Create a custom x402 facilitator using Rust
- [How to Write a Scheme](/docs/how-to-write-a-scheme.md): Implement custom payment logic for x402-rs
- [Contact](/docs/contact.md): Get in touch with the FareSide team

# Blog

- [x402 Contracts Dashboard: A Missing Public Good](/blog/2026-07-06-contracts-dashboard.md): x402 payments don't work on a chain without a handful of shared contracts deployed there. We built a public dashboard to show which chains have them, and let anyone deploy the missing ones.
- [Why x402 v2 Uses CAIP-2 Chain Identifiers](/blog/2026-01-22-x402-v2-caip2-identifiers.md): A deep dive into why x402 v2 adopted CAIP-2 chain identifiers instead of human-readable names, and why those weird-looking identifiers actually make sense.
- [Why FareSide Exists](/blog/2025-12-05-hello-world.md): Why we built FareSide: surviving the x402 memecoin surge at 77% market share, shutting down because free isn't sustainable, and bringing it back as production infrastructure.