Most agent demos skip the uncomfortable part. They show a model deciding to use a tool, then jump straight to a successful API call. In production, the missing step is usually the whole problem: what capability is actually supported; which provider path can execute it; what the call is likely to cost; and what credential boundary applies before the agent spends anything. Rhumb splits that into two jobs: Index ranks services so agents and operators can compare what exists. Resolve routes supported capabilities into governed calls. For search.query (web search), the useful preflight is two open reads and one paid / authorized continuation. 1. Resolve the supported provider paths API = "https://api.rhumb.dev/v1" curl " ${ API } /capabilities/search.query/resolve" Enter fullscreen mode Exit fullscreen mode For search.query , this open preflight read shows supported provider paths and routing context. It is a way to ask: “what can Resolve do for this capability before I hand it money or credentials?” 2.…