Gateway
Health and readiness
Liveness and readiness probes for load balancers and orchestrators.
GET /health
/healthpublicLiveness checks no dependencies. The route returns 200after the Host check and, when an Origin is present, the Origin check pass. An unapproved Host or Origin gets 403; approved hosts are the publicBaseUrl hostname and loopback names, and approved origins come from server.allowedOrigins.
curl -s http://localhost:8080/healthGET /ready
/readypublicReadiness. 503 when the store, an adapter, a payment provider or an authorization provider reports fail; otherwise 200. A warn is degraded but still ready.
The x402 provider checks the RPC chain, token and facilitator support for both rail and resource offers. One failing offer fails the provider. When there are several offers, the discovery document publishes each one's status; the gateway logs the reason at debug level.
curl -s -w '\n%{http_code}\n' http://localhost:8080/readyResponse
readybooleanrequiredstoreReadinessCheckrequiredadapters / paymentProviders / authorizationProvidersReadinessCheck[]requiredname, a status of pass, warn or fail, and, when not passing, a detail from a fixed vocabulary such as store-unwritable or payment-provider-unreachable. Raw errors go to the log, never to this unauthenticated route./.well-known/agent-commerce, which limits repeated upstream checks when clients poll frequently.