How to make an API discoverable to agents

Outcome, schema, price, rail, live 402. Conformance outranks keyword stuffing.

AEO is Discover → Understand → Trust → Choose → Pay → Reuse. If an agent cannot answer those six without reading a marketing page, the product is not machine-ready.

Free discovery metadata should include outcome, description, inputSchema, outputSchema, sample, price, payment rail, network, asset, freshness, evidence model, usage rights, latency expectations, version, and endpoint.

well-known, OpenAPI, MCP tools/list, and live 402 must agree. Foundry already watched overstuffed metadata break buyer-conforming clients. More metadata is not automatically better.