Route Planning

Route planning turns an agent data need into a route decision, candidate list, rejection, abstention, or procurement preview.

Default Flow

Normalize the request into a route intent.
Retrieve source and capability candidates.
Apply hard filters before ranking.
Score remaining candidates with deterministic evidence.
Preserve optional semantic/model scores as diagnostics, not hidden authority.
Return an explainable plan.
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

Hard filters can include:

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

Outcome	Meaning
callable route	execution may proceed after immediate preflight checks
abstention	PubFi should not select a route from available evidence
unsupported	request is outside current product boundary
procurement preview	demand exists, but supplier/commercial review is required
contract-ready	schema shape exists, but live routeability is not promised

Non-Goals

Route planning must not silently call suppliers, create payment payloads, grant credentials, or hide rejected candidates and policy reasons.

​Route Planning

​Default Flow

​Example Intent

​Hard Filters

​Outcomes