Outcome infrastructure for AI agents
Clervo finds the right capability, qualifies route and policy, controls cost, executes within the current contract, and keeps result, evidence, and receipt boundaries legible.
ClervoRouter
The locked operating model stays constant while current public availability remains a separate observed fact.
ClervoRouter routes bounded tasks across six permanent capability families and refuses paths that cannot satisfy the current contract.
Extract the intended outcome, constraints, risk, latency, and evidence requirement.
Search by task rather than by vendor or integration trivia.
Check current lifecycle, policy, price boundary, network/asset context, and proof requirements.
Run only an eligible operation; refuse or pause when the contract breaks.
Keep normalized result, evidence, receipt, and reconciliation state separate.
Six permanent families
Family identity is permanent. Lifecycle and proof below come from the canonical observed registry and can change independently.
Permanent family identity · current operation and route state is registry-bound.
AIPermanent family identity · current operation and route state is registry-bound.
SBPermanent family identity · current operation and route state is registry-bound.
RPPermanent family identity · current operation and route state is registry-bound.
PRPermanent family identity · current operation and route state is registry-bound.
CIPermanent family identity · current operation and route state is registry-bound.
Qualification and result contract
This structure is the operating contract. Current availability, prices, and settlement readiness remain registry/runtime facts rather than design claims.
The agent should understand why a route is eligible before meaningful action occurs.
A useful result stays separate from evidence, payment state, and replay decisions.
Interfaces
These cards preserve the locked information architecture. They do not assert unsupported client compatibility or package publication.
/skill.mdAvailability is bound elsewhere and is not inferred from this design surface.
MCPAvailability is bound elsewhere and is not inferred from this design surface.
TypeScriptAvailability is bound elsewhere and is not inferred from this design surface.
PythonAvailability is bound elsewhere and is not inferred from this design surface.
HTTP / OpenAPIAvailability is bound elsewhere and is not inferred from this design surface.
Trust boundary
Gold is earned only after verification. Refused and unresolved states never borrow proof color.
The required checks resolved and proof material exists for that outcome.
Policy, lifecycle, availability, cost, or approval prevents execution. No verified-gold state appears.
The result or settlement cannot yet be proven. Retry remains blocked until reconciliation is safe.
Operate from current truth
Search canonical observed routes by task, family, lifecycle, proof, and capability without promoting design fixtures into live claims.