Skip to main content
GET
Health and Readiness
Use readiness for service monitoring. It is not proof that a wallet transaction, one token route, or one RPC call will succeed.

Request

Response use

  • Require HTTP 200 and top-level readiness before directing a new flow to production.
  • Record the returned release with incident logs.
  • Inspect individual checks when readiness fails.
  • Keep transaction simulation and receipt verification in the user flow even when readiness is healthy.
GET /api/health/live is the lighter process-liveness check. Use /ready when deciding whether the service and required dependencies can serve normal requests.
A healthy API can still be behind the chain for a short time. A successful on-chain receipt remains the source of truth for launch creation.