For AI agents
Where an agent finds everything it needs to use typesearch on its own.
typesearch publishes machine-readable guides so an agent — or the assistant writing your code — can learn the API without a human in between. All of them are generated from the same source as the API and this site, so prices, modes and endpoints stay current.
| File | What it is |
|---|---|
/.well-known/skill.md | The API guide for agents: what typesearch covers, which endpoint to use, what it costs, a request for every endpoint, errors and limits. |
/.well-known/skills/index.json | The same guide as an Agent Skill, for agents that discover and install skills. |
/llms.txt | An index of the site and the docs (llmstxt.org). |
/llms-full.txt | All the docs as one Markdown file. |
/openapi.json | Every request and response field, with types and defaults. The authority on details. |
Every page of these docs is also available as Markdown: Copy Markdown at the top of the page, or open it straight in ChatGPT, Claude or Cursor from the menu next to it.
Give it to your agent
- Coding assistants (Claude Code, Cursor, Codex…): point them at
https://typesearch.ai/.well-known/skill.mdbefore they write code against the API. - Agents that call the API at runtime: add the skill to the agent's instructions, and the key as
TYPESEARCH_API_KEY(Authentication). - MCP clients: connect the MCP server instead — the tools describe themselves.
Rules we ask agents to follow
- Cite the link of every fact taken from a result.
- Quote only the excerpts the API returned, verbatim and short. Never reconstruct article text.
- Treat results with a
scorebetween 0.35 and 0.65 as leads, not facts. - Start with
fast, and say so when escalating to a more expensive mode.