Provider discovery
The public sandbox exposes a directory of synthetic provider records so clients can test search, filtering, capability rendering, and OAuth error handling. Directory inclusion does not mean a party is a live counterparty, customer, partner, reachable production service, or independently accredited.
bash
curl "https://phosra-api-sandbox-production.up.railway.app/api/v1/providers"Fixture fields may include:
| Field | Sandbox meaning |
|---|---|
did | Synthetic registry identifier |
name, icon_url | Presentation metadata |
tier | Proposed standing value used to exercise client logic |
capabilities | Declared fixture values for filtering |
connect_url | Sandbox reference flow, when configured |
Treat missing or unconfigured connect metadata as an expected test branch. Never present a provider as verified or accredited based solely on this directory.
In a future production architecture, independently governed registry records and verified counterparty metadata could support discovery. That production directory, hosted routing, and independent accreditation path remain roadmap.