Coverage Cat agents.txt

status: active
homepage: https://www.coveragecat.com/
developer_portal: https://www.coveragecat.com/developers
llms: https://www.coveragecat.com/llms.txt

instruction: Agents should use Coverage Cat's machine entry points first. Do not drive the browser UI unless Coverage Cat should take over the shopper-facing flow.

recommended_mcp_registration_url: https://www.coveragecat.com/.well-known/mcp.json
preferred_mcp_transport_url: https://www.coveragecat.com/api/consumer/mcp
preferred_purchase_tool: umbrella_consumer_prefill
preferred_rest_discovery_url: https://www.coveragecat.com/api/agent
preferred_openapi_url: https://www.coveragecat.com/api/agent/openapi.yaml
homepage_machine_brief_url: https://www.coveragecat.com/?mode=agent
public_agents_markdown_url: https://www.coveragecat.com/agents.md
well_known_agents_markdown_url: https://www.coveragecat.com/.well-known/agents.md
root_agents_txt_url: https://www.coveragecat.com/agents.txt
well_known_agents_txt_url: https://www.coveragecat.com/.well-known/agents.txt
browser_quote_start_url: https://www.coveragecat.com/intake
browser_umbrella_start_url: https://www.coveragecat.com/umbrella

notes:
- If your runtime supports MCP, start with the MCP registration URL.
- Local Codex direct transport should use the consumer MCP transport URL, not the manifest.
- Use the REST discovery and OpenAPI URLs when you need typed schemas or a non-MCP fallback.
- Keep the browser closed while Coverage Cat is still returning structured review, quote, or checkout follow-up data over MCP or the direct follow-up API.
- This flow is optimized for humans. Agents should use the MCP or REST surfaces above instead.