​

Route Planning

​

Default Flow

1. Normalize the request into a route intent.
2. Retrieve source and capability candidates.
3. Apply hard filters before ranking.
4. Score remaining candidates with deterministic evidence.
5. Preserve optional semantic/model scores as diagnostics, not hidden authority.
6. Return an explainable plan.
7. Execute only if the selected route is supported and callable.

​

Example Intent

{
  "objective": "Need token balances for a Polkadot wallet.",
  "chains": ["polkadot"],
  "categories": ["on_chain_state"],
  "required_capabilities": ["wallet.token_balances"],
  "expected_calls_per_day": 10,
  "allow_paid": true
}

​

Hard Filters

• supported capability id;
• required chain or network;
• configured provider credential;
• source freshness;
• caller API-key scope;
• active billing admission and sufficient request allocation;
• privacy and redaction policy;
• payment/procurement policy;
• route availability.

​

Outcomes

​

Non-Goals