well known agent discovery
hold your voice exposes machine-readable discovery files under well-known paths so agents can find api, mcp, auth, and capability metadata without scraping marketing pages.
quick answer
agents should read the well-known discovery files before assuming which endpoints or tools exist.
use this for
- agent onboarding
- api catalog discovery
- checking current mcp tool metadata
steps
- open the site root or a documented api page.
- follow the link headers for api catalog and mcp metadata.
- read the well-known api catalog for endpoint shape.
- read the mcp server card for tool names and limits.
- fall back to the human wiki pages for explanation.
details to know
- the discovery files describe public contracts, not private admin tools.
- oauth metadata is used as api-key auth metadata for agents that expect protected-resource documents.
- server link headers help automated clients discover the same documents from normal pages.
limits and edge cases
- agents should not treat discovery metadata as permission to call endpoints without a user key.
- well-known pages must stay in sync with api and mcp behavior.
ready to use the product instead of reading about it?
open app