Route planning resolves an exact path and HTTP method against the currently installed Registry v2 generation. It can return a match, candidate list, rejection, or abstention without executing an upstream provider.

​
Default Flow

  1. Read the current Registry generation.
  2. Supply an exact raw_path and method, or a bounded provider-neutral objective or query.
  3. Apply the Registry matcher and readiness rules.
  4. Return the generation-bound route decision and reason.
  5. Execute only an exact ready path and method from that generation.

​
Example Intent

​
Hard Filters

Hard filters can include:
  • exact canonical path and method;
  • current Registry generation and matcher;
  • operation readiness;
  • request query and body bounds;
  • configured provider credential when required;
  • response content and status policy;
  • caller API-key environment, admission, and allocation for authenticated execution; and
  • x402 eligibility for an accountless HTTP or MCP request.

​
Outcomes

​
Non-Goals

Route planning must not call providers, create x402 payment payloads, consume allocation, grant credentials, or hide rejected candidates and policy reasons. After planning, use Registry Gateway Examples for HTTP or MCP Client Setup for agent execution.