Skip to content

Add public readiness endpoint for facilitator and provider configuration #56

Description

@emrekayat

Why this matters

SCF demos need to distinguish an unavailable facilitator/provider from a broken product. A public readiness endpoint can expose non-sensitive status for API, x402 facilitator config, and provider availability.

Scope

Add a public readiness endpoint such as /api/readiness returning:

  • API uptime/build metadata;
  • demo mode status;
  • Stellar network label;
  • facilitator configured: boolean;
  • facilitator supported check status if safe and cached;
  • provider counts by mode;
  • storage backend status.

Do not return API keys, secret keys, facilitator auth headers, private URLs, or wallet secrets.

Suggested files

  • apps/api/src/routes/public.ts
  • apps/api/src/lib/config.ts
  • apps/api/src/lib/build-metadata.ts
  • apps/api/src/lib/storage/index.ts

Acceptance criteria

  • Endpoint returns useful non-sensitive readiness JSON.
  • Tests verify secret-like config values are not emitted.
  • Endpoint works in demo mode without live facilitator credentials.
  • Existing /health behavior remains compatible.

Metadata

Metadata

Labels

Stellar WaveIssue proposed for the Drips Stellar Wave programarea: apiAPI servicearea: x402x402 and Stellar paymentscomplexity: highExpected high implementation complexitydrips-candidateCandidate for a Drips Stellar WaveenhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions