Skip to main content

Overview

Exa is a neural + keyword web search engine built for agents. The Exa connection on agntdata lets you proxy search, contents, find-similar, and agentic-answer calls with your agntdata API key — Exa bills you directly for usage.

Prerequisites

Connect

  1. In the agntdata dashboard, open Integrations and click Exa.
  2. Paste your Exa API key into the configuration dialog and save.
  3. The key is encrypted at rest and only decrypted when proxying a request.

Make requests

agntdata forwards the wildcard path and JSON body to https://api.exa.ai with your stored key attached as a bearer token:

Example — neural search with contents

Example — fetch parsed contents for URLs

Example — find similar pages

Example — agentic answer with citations

Endpoints supported

  • POST /search — neural + keyword search with optional contents enrichment
  • POST /contents — parsed text, highlights, and LLM summaries for URLs or result IDs
  • POST /findSimilar — pages semantically similar to a seed URL
  • POST /answer — agentic Q&A with cited sources (supports streaming)

Rate limits

Exa applies per-key rate limits. agntdata surfaces upstream 429 responses as-is.

FAQ

Do I pay agntdata credits for Exa calls? No. Exa bills your Exa account directly — agntdata only proxies the request and doesn’t charge credits for /v1/connections/*. How is the API key transmitted to Exa? agntdata injects your stored key as an Authorization: Bearer header. Exa also accepts x-api-key; either works. Does agntdata store my Exa API key? Encrypted at rest in workspace_integrations; decrypted only when proxying a request.