# FastNEAR x402 facilitator

Open-source, API-key-gated x402 exact-payment verification and durable settlement for Circle USDC on NEAR and Base.

## This instance

- Network: near:mainnet
- Canonical asset: 17208628f84f5d6ad33f0da3bbbeb27ffcb398eac501a31bd6ad2011e36133a1
- Scheme: exact
- Canonical wire version: x402 v2
- Facilitator fee: 0
- Build version: 0.6.0
- Only canonical x402 v2 is advertised by this instance.
- NEAR payments use the configured canonical NEP-141 Circle USDC contract.

## Public routes

- GET /supported - live payment capabilities and signer identity
- GET /readyz - sanitized settlement readiness
- GET /healthz - process liveness
- GET /llms.txt - this agent-readable, instance-specific onboarding document
- GET /openapi.yaml - same-origin OpenAPI 3.1 contract
- GET /discovery/resources - public opt-in catalog of independently operated merchants; an entry does not claim settlement activity or volume

## Authenticated routes

- POST /verify - read-only payment verification
- POST /settle - durable, idempotent settlement

Resource servers require a separate API key for every deployed instance and environment. Keep the key in server-side secret storage or a mode-0600 regular file. Never put it in payer, browser, issue, log, or source code.

## Integrate

- Access guide: https://github.com/fastnear/x402-facilitator/blob/main/docs/reference-access.md
- Tested TypeScript recipes: https://github.com/fastnear/x402-facilitator/tree/main/examples/resource-server/typescript
- Runnable Express resource server: https://github.com/fastnear/x402-facilitator/tree/main/examples/resource-server
- Access request: https://github.com/fastnear/x402-facilitator/issues/new?template=access_request.yml
- Base merchant pilot: https://github.com/fastnear/x402-facilitator/issues/new?template=base_merchant_pilot.yml
- Source and security: https://github.com/fastnear/x402-facilitator

Base mainnet resource servers must use Circle USDC's exact EIP-712 domain name "USD Coin", version "2". Each deployed facilitator instance requires its own credential.

The public reference deployment serves NEAR mainnet, NEAR testnet, and Base mainnet. Base Sepolia is a supported software profile, not a claimed live public instance.