Add Andi to your agent
Your agent installs and configures the Andi Search API itself — paste one line:Paste into Claude Code, Cursor, or Codex
andiai.com, follows it to the install guide at api.andiai.com, then gets an API key from the API Console, connects the MCP server, and verifies the setup.
Are you an AI agent? Fetch https://api.andiai.com/install.md and follow it to configure Andi Search — MCP server, API key, and verification.
Andi Search MCP server
Use Andi as your agent’s web search and page fetch tool over the Model Context Protocol. Server URL:https://api.andiai.com/mcp
Transport: Streamable HTTP
Authentication: Pass your API key in the x-api-key header. Get a key from the API Console.
Your API key is account-level, not project-level, so a system-wide install works everywhere at once. Each client below notes how to choose between project and system-wide scope.
Claude Code
For the current project:Cursor
Add to.cursor/mcp.json in your project, or to ~/.cursor/mcp.json for all projects:
Claude web and desktop
Add this as a custom connector in your MCP server settings:VS Code
Add to your VS Code settings (JSON):Codex CLI
Add to~/.codex/config.toml (system-wide — Codex config applies to all projects), with ANDI_API_KEY exported in your shell:
Other MCP clients
Any client that supports the Streamable HTTP transport can connect: server URLhttps://api.andiai.com/mcp, with your API key in the x-api-key request header.
Stdio-only clients
For MCP clients that only support the stdio transport, the Andi CLI runs a local server exposing the same tools:MCP tools
andi_web_search
Searches the web and returns LLM-ready markdown. Wraps GET /api/v1/search with format=context and metadata=full.
The MCP tool caps
limit at 50. The REST endpoint allows up to 100.metadata=full fields — content_type, word_count, lang, publisher, summary — in each result’s frontmatter when available (see response format), plus a per-call cost_dollars. Results default to extracts; set content=true or follow up with andi_fetch_url only when extracts aren’t enough.
andi_fetch_url
Fetches a web page and returns its content as LLM-ready markdown. Wraps GET /api/v1/fetch.
See content retrieval for the full fetch endpoint reference.
Error handling
MCP tool errors come back as a text result withisError: true, not a raw HTTP status — the message is written for the calling agent to act on:
Agent Skill
The API hosts an installable Agent Skill that gives agents a description of the search tool, its parameters, and usage guidance. Agents that support skills can install it directly:https://api.andiai.com/.well-known/agent-skills/andi-web-search/SKILL.md, with an index at /.well-known/agent-skills/index.json.
Claude Code plugin
Theandisearch/andi-agent-skills repository doubles as a Claude Code plugin marketplace. The andi plugin installs the andi-web-search skill and connects the hosted MCP server in one step:
ANDI_API_KEY in your environment before first use.
Install from the GitHub repo
The same repository works with the skills CLI —npx skills add andisearch/andi-agent-skills — and with Codex’s skill installer. See the repo README for the full install matrix, including the Codex plugin.
Agent-native output
The API supportsformat=context, which returns search results as markdown with YAML frontmatter — sized for LLM context windows and ready to use without JSON parsing. See response format for the full contract.
Keyless pay-per-call
Agents can also pay per call via x402 through Orthogonal without signing up for an API key. See the auth guide for details.API discovery files
The API publishes these files for automated agent and tool integration:Docs Q&A MCP server (searches this documentation only)
This docs site runs its own Model Context Protocol server, separate from the Andi Search MCP server above. It lets AI tools search and read this documentation — it does not perform web search. Server URL:https://docs.andiai.com/mcp
Claude Code
Claude web and desktop
Add this to your MCP server settings:Cursor
Add to your.cursor/mcp.json:
VS Code
Add to your VS Code settings (JSON):llms.txt
The site publishes llms.txt files that list all documentation pages with direct markdown URLs.
Use
/llms.txt for discovery and navigation. Use /llms-full.txt when you need the complete documentation in a single request.
Markdown content negotiation
Any docs page returns clean markdown when requested with theAccept: text/markdown header. The markdown response includes YAML frontmatter.
Link headers pointing to /llms.txt and /llms-full.txt, and an X-Llms-Txt header.
AI crawler access
The site’srobots.txt explicitly allows AI crawlers including GPTBot, ClaudeBot, and PerplexityBot.
Next steps
AI agent tool example
Search and fetch workflows for AI agents.
Content retrieval
Full fetch endpoint reference.
Quickstart
Make your first API call.
Response format
JSON and context format output.

