Exa

Search and data

Exa for AI agents. One API key, ready-made tools.

Search the web by meaning, read page contents and find similar pages, reached with your Agent200 API key.

About Exa

With the Exa connector, your agent searches the web by meaning, reads the full text of the pages it finds, finds pages like one it already has and gets cited answers. It is reached with your project’s Agent200 API key, so there is no separate Exa key to collect, store or rotate.

Exa is a search engine built for AI, with neural search that matches a query to pages by meaning rather than keywords alone.

Tools

What your agent can do in Exa.

Each tool is a capability the model can call. You decide which ones a project allows, and your Agent200 API key reaches them.

  • Search the web

    Read
    exa_search_web

    Find pages that match a query, with filters for domain, date and category.

  • Get page contents

    Read
    exa_get_contents

    Read the text, highlights or summary of chosen pages.

  • Find similar pages

    Read
    exa_find_similar

    Find pages similar to a given URL.

  • Get an answer

    Read
    exa_get_answer

    Answer a question from search results, with citations.

Control

Limits you can set.

You decide what your agent may do in Exa, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Allow exa_search_web and exa_get_contents, and switch off the tools your agent does not need.

  • Restrict what the agent reaches

    Choose the endpoints a project may use. A call outside them is refused.

Get started

Connect Exa
in two steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Run with the Exa tools

    Name the model and the tools. The model decides which Exa tools to call, and Agent200 executes them with your Agent200 API key.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Find recent papers on retrieval for long documents",
        tools: ["exa"],
      });
    
    console.log(result.output);

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Exa connector and how to use it.

Agent brief
Connector: Exa, through Agent200. In code: "exa".
What it does: Search the web by meaning, read page contents and find similar pages, reached with your Agent200 API key.
Page: https://www.agent200.com/tools/exa/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Agent200 reaches Exa with the project's Agent200 API key. No separate Exa key is needed.
3. Read tools: exa_search_web, exa_get_contents, exa_find_similar, exa_get_answer. Name "exa" in the tools of a request; the model decides which tool to call.
4. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
5. Before a write, confirm with the user, unless they asked for that exact change.
6. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/exa/framework/claude/
   https://www.agent200.com/tools/exa/framework/chatgpt/
   https://www.agent200.com/tools/exa/framework/claude-code/
   https://www.agent200.com/tools/exa/framework/muse/
   https://www.agent200.com/tools/exa/framework/grok-bot/
   https://www.agent200.com/tools/exa/framework/openai-dots/
   https://www.agent200.com/tools/exa/framework/claude-duet/
   https://www.agent200.com/tools/exa/framework/hermes-agent/
   https://www.agent200.com/tools/exa/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /tools/exa.md

Guides

Use Exa with the AI you build on.

Step-by-step setup for Exa with a specific model, assistant or agent framework.

FAQ

Exa and Agent200, answered.

Do I need my own Exa API key?

No. Your Agent200 API key reaches Exa, so there is no separate provider key to collect, store or rotate.

Can I limit what my agent can do in Exa?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • Tavily

    Tavily

    Web search built for agents, reached with your Agent200 API key.

    Agent200 API key Search and data
  • Firecrawl

    Firecrawl

    Scrape pages into Markdown, crawl and map sites, and extract structured data, reached with your Agent200 API key.

    Agent200 API key Search and data
  • Brave Search

    Brave Search

    Search the web, news, images and videos from Brave's independent index, reached with your Agent200 API key.

    Agent200 API key Search and data
  • Perplexity

    Perplexity

    Get web-grounded answers with cited sources, or ranked search results, reached with your Agent200 API key.

    Agent200 API key Search and data
200 OK

Start with Exa.
Your agent does the rest.

Your agent reaches Exa with your Agent200 API key. No provider key to collect, store or rotate.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)