Connect
Streamable HTTP
- MCP URL: https://api.fetch.li/mcp (also https://fetch.li/mcp)
- Auth: Demo GET without a key. Bearer key for higher limits. No OAuth.
- Catalogue:
GET /v1lists every endpoint machine-readably.
Agent builders
UK facts your agent
can read aloud.
fetch.li speaks MCP over streamable HTTP. Every successful GET leads with ok, answer, and say. Point a client at the MCP URL, or call REST with format=prompt when you want LLM-ready text.
- 8 / 10s burst
- 12 / minute
- 60 / hour
MCP
Same contract, agent-native transport
One tool per catalogue GET id. Named fetch_<id>. Families: sky, weather, life, uk, money, tools, check.
Not tools
On purpose
Vibe classify, account routes, and mail routes stay off the MCP surface. Agents get UK facts, not billing or inbox plumbing. Use REST with a Bearer key when you need those.
Machine context lives in llms.txt on the apex host. Registry submission is planned; this page is the human landing spot until then.