How Agents Match Intent to Capability
Capability matching is the step where an agent turns an intent into a provider and a verb: given "refund this order", find an organisation that exposes a callable refund, is authorised to perform it, and sits within policy. It depends on machine-readable capability declarations at discovery time, verifiable authority, and a price and policy the agent can read before it commits. Without a declared capability surface, matching degrades to scraping and guessing.
Matching is a discovery problem
An agent can only match against what organisations publish. A capability index — verbs an org offers, under what terms — is what turns matching from a scrape into a lookup. The estate’s directory and front door exist so an agent can answer "who can do this, and are they allowed to" without a human assembling a list by hand.
Questions
How is this different from search?
Search ranks documents for a human to read. Capability matching resolves an intent to an authorised, callable action a machine can invoke directly.
What if two providers match?
The agent chooses on the intent’s constraints — price, policy, reputation — and records why, so the choice is auditable.
Where this lives in the estate
FlashyOS — the capability index and front door agents match against
Keep reading
By Michael Gord · published 2026-10-04 · part of the Agentic Encyclopedia. Dates are the day of publication; events are cited at their own dates.