Provider Readiness
Provider readiness determines when PubFi can safely say a source is callable through the gateway.Readiness Layers
| Layer | Question |
|---|---|
| Discovery listing | Does the public source-selection record exist? |
| Source freshness | Is public provider evidence current enough? |
| Capability fit | Does the provider support the requested data shape? |
| Adapter certification | Has the route or generic manifest passed required certification checks? |
| Runtime credential | Is the upstream credential configured server-side? |
| Account gate | Does the caller have PubFi auth, scope, fresh active admission, and sufficient allocation? |
| Execution gate | Can the request be validated and attempted safely now? |
Certification
Adapter certification is evidence, not procurement authority. A provider cannot be presented asgateway_available unless its current adapter, readiness catalog, route cases, auth shape,
environment requirements, smoke evidence, usage facts, and public-claim basis align.
Generic HTTP/OpenAPI Manifests
Generic manifests can make low-risk routes easier to certify, but they fail closed unless:- the provider and operation are within PubFi’s crypto/Web3/on-chain data scope;
- manifest state is runtime-enabled;
- certification run passed;
- required operation, auth, parameter, timeout, response, usage, and fixture checks passed;
- supplier procurement and payment authority remain disabled unless separately approved.