Docs / machine catalog
One registry drives every surface.
Capabilities, claims, lifecycle, prices, packages and discovery are all generated from the probed release candidate. Private qualification and customer availability stay different fields.
Generated surface
Two fields per family, never merged.
Observed at 2026-08-11T08:48:34.576Z from packages/catalog/live-registry.json. Lifecycle says whether a family serves requests now; proof says what has been demonstrated.
- AIlivepaid outcome verified
- Crypto Intelligencelivequote observed, unpaid
- Prediction Intelligencelivequote observed, unpaid
- Multi-chain RPCunavailablenothing demonstrated
- Secure Sandboxlivepaid outcome verified
- Researchlivepaid outcome verified
Frozen interface
What these guides describe.
- Release candidate
- clervo-private-core-2026-08-02.2
- Interface hash
- sha256:2773690eda2ed6c89461c98f1537fccc5ae648f37845eb7a5a620952647a39b4
- Public callable
- yes