Exaexa.ai

Can an AI agent use Exa (exa.ai)?

As of 15 Oct 2026, an AI agent gets into Exa on its own and does 20% of the core work.

Level 2 · Gets inAn agent gets in on its own but does less than half the core work.

Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
Access: No key needed, pay per call.
Use: 20% of the work.
Pay: Pays per call for part of it: Paid $0.001 a call (x402), 15 Oct.
Leave: Leaves on its own: Nothing to cancel, made nothing to delete.

Ways in: No key needed, 2 of 10 core tasks · Pay per call, 3 of 10 core tasks

To reach L3 · Does the work: do half of the core work (now 20%).

With an account set up by a person: not measured yet.

Got in on 2 of 3 drives: the bot check let it through in some and not in others.

What the levels mean

Visit Exa Follow changes

Driven 15 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

Agents on a serverGet in on their own.
Signed agentsThe site opens.
Agents in a person's browserNot measured yet.

Sign-up page checked 15 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Exa (exa.ai).

On its own

Search the web and read web pages with no sign-up at all
Pay small amounts per search using a crypto wallet, without an account

What it can't, and why

Create an Exa account or get an API keyA 'prove you are human' puzzle blocks the sign-up form
Get direct answers, run research agents, build datasets, or set up monitoringAll of these need an account, which could not be created

Not needed

Not needed: our agent paid per call without an account (x402).

Every way in it offers, as our agent tried them

Ways in
Way in	What happened
No key needed	Got in, 2 min
Pay per call	Got in, under a minute
A payment opens the account	Not tried: over our payment cap
Email and code	Stopped by a CAPTCHA
Stripe Projects	Not tried: no account yet
Sign‑in for apps (OAuth, MCP)	Stopped by a CAPTCHA
Added by an admin	Not tried: needs a person's account
A key from a person	Not tried: needs a person's account

Official server · 9 of 14 calls worked

Does Exa (exa.ai) have an MCP server, and can an agent connect to it?

Yes. Exa has an official MCP server.

A new agent can get in on its own: in the drive of 15 Oct 2026, our agent got working access without signing up. Through the MCP server, 9 of our agent's 14 attempts worked.

What the drive found

APIOpenAPIMCP · official–CLIllms.txtWebhooks–Sandbox

No key needed

How does an AI agent get an Exa (exa.ai) API key?

In the drive of 15 Oct 2026, our agent needed no key. Not needed: our agent paid per call without an account (x402).

No account to delete

Can an AI agent delete its Exa account?

Not applicable: our agent used Exa without an account, and it made nothing to delete.

Pays per call for part of it

Can an AI agent pay for Exa?

Pays per call for part of it: paid $0.001 a call (x402), 15 Oct.

Plan and price: pay per call /search.

No CAPTCHA at checkoutOffers x402 payment

Paid on its own: $0.001 in USDC through x402 on Base, 15 Oct 2026. 0x58e56c54…c50814

Stripe Projects on its own domain
x402 on its own domain · Base, Solana, World Chain, Arc
MPP on its own domain · Tempo

It has a free plan.

What would let agents pay on their own

Sell the plan or credits over the rail, not only side endpoints. Let the paid call buy what the product sells, so the rail covers the whole product.

We paid one x402 v2 call each for /search, deep /search and /contents on Exa's own api.exa.ai (Base, settled, 2xx; pay_tx.json). /answer, agent runs, websets and monitors have no per-call rail (401 without a key), so the rail is partial. The dashboard billing page could not be reached (no account, Vercel checkpoint).

Ways to pay checked 15 Oct 2026.

For the team behind Exa.

Where agents stop in Exa (exa.ai) today, and the fixes that get them further, highest impact first.

In on its own; 20% of the work done

The fixes, highest impact first

Let signed agents through the sign-up checkStep-by-step guide
Offer a headless account and key routeStep-by-step guide
Sell more endpoints over x402 and MPP

2 more fixes

Signal rate limits with 429 and Retry-After
Support MCP (the 28 Jul 2026 spec) server/discover

Claim it free and reply next to the result.
A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

Get a Drive Claim it free

See the example report

Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

<a href="https://agentdrives.com/tools/exa" rel="nofollow"><img src="https://agentdrives.com/badge/exa.svg" alt="AgentDrives · Driven · L2 · Gets in" height="24"></a>

Behind the level.

The part scores and the measures behind them.

Part scores and the measures · the docs · level history

Part scores

Holds up: 60 of 100, fair

Agent-ready setup

llms.txt: found
OpenAPI: found
MCP server: found
CLI: not found

Not measured in this drive: Docs match (part of an Audit).

The measures

Work done20
Reliability50
Crash test70

The docs

196 of 209 pages read. Complete.

A getting-started page
An auth page
Errors listed with their codes
Code examples on most pages
Newest page updated 15 Oct 2026
A page for 10 of 10 core tasks

Read on 15 Oct 2026.

Tried as documented

2 of 15 documented ways to do the core work worked when tried.

Tried as documented
What happened	Ways
Worked when tried	2
Documented, didn't work	0
Not tried (a paid plan, or no way to reach it)	13
Worked, but not in the docs	0

Level history

1 Oct 20263 drivesL1Needs a person
6 Oct 2026L1Needs a person
13 Oct 2026new driveL2Gets in
15 Oct 2026L2Gets in

How Exa handles an agent's mistakes · 3 probes · core run 3×

Malformed requests, a retry, a wrong key and a short burst of reads on our agent's own account, and how Exa answered.

Clear errors90
Recovery70
Rate limits50

API 401s name the fix and the key page; MCP validation errors name the missing field. The keyless MCP limit comes as HTTP 200 with prose and a _meta flag, no 429 or Retry-After; idempotency not testable without an account.

Vagueburst of 8 keyless MCP searchesSearch the web with a natural-language or keyword querycalls 1-7 HTTP 200 results; call 8 HTTP 200 with result._meta ai.exa/rateLimited:true and text 'You've hit Exa's free MCP rate limit… Fix: Create API key at https://dashboard.exa.ai/api-keys'; no 429,
Cleartool call missing required urlsFetch full page text/highlights/summary for known URLsHTTP 200, result.isError true: 'MCP error -32602: Input validation error… path [urls] expected array, Required'
Clearwrong API keySearch the web with a natural-language or keyword queryHTTP/2 401 content-type: application/json; charset=utf-8 {"requestId":"6c99a4fdc75a553cac7a0a0f74aef43f","error":"Invalid API key. Provide a valid key using 'Authorization: Bearer <key>' or 'x-api-ke

For agents and builders.

The drive as data, every checkpoint and all 80 attempts.

How an agent connects · 5 tips

/api/tools/exa.json /tools/exa.mdMCP get_tool {"slug":"exa"}

Without an account, use the hosted MCP at https://mcp.exa.ai/mcp: web_search_exa, web_fetch_exa and (with ?tools=) web_search_advanced_exa need no key
The keyless limit trips after a handful of quick calls; the tool result carries _meta ai.exa/rateLimited:true and the limit clears within about a minute
With a wallet, /search and /contents take x402 v2 (Base and others) or MPP on Tempo with no account
Requesting agent_run without auth makes the whole MCP connection answer 401: leave it out of ?tools= when keyless
Docs pages come as markdown with .md or Accept: text/markdown

Every checkpoint, in detail · 9 checkpoints

DocsHeadlessllms.txt, docs/llms.txt, markdown docs (.md and Accept: text/markdown), OpenAPI 3.1.0 and a Team Management OpenAPI all fetched headless.
Sign upNot neededNot needed: our agent paid per call without an account (x402).
VerifyNot neededNot needed: our agent paid per call without an account (x402).
KeyNot neededNot needed: our agent paid per call without an account (x402).
First callHeadlessDocumented keyless hosted MCP (mcp.exa.ai/mcp): web_search_exa and web_fetch_exa answered without any account or key.
First actionNot neededNo key needed: done.
PayHeadlessWe paid one x402 v2 call each for /search, deep /search and /contents on Exa's own api.exa.ai (Base, settled, 2xx; pay_tx.json). /answer, agent runs, websets and monitors have no per-call rail (401 without a key), so the rail is partial. The dashboard billing page could not be reached (no account, Vercel checkpoint).
CancelNot neededNothing to cancel: our agent used it pay-per-call.
DeleteNot neededNo Exa account was made. Keyless searches store nothing for the caller. One unused public OAuth client from dynamic registration stays at auth.exa.ai; there is no documented way to delete it.

The attempt log · 80 attempts

Attempt log
Capability	Route	Result	Evidence
robots.txt & aipref	api	done ✓	exa.ai/robots.txt: User-Agent: * Disallow: /search?* and /hackathon/; no Content-Usage or Content-signal lines; no Content-Usage header seen. api.exa.ai/robots.txt 404 JSON; auth.exa.ai/robots.txt 404.
dashboard reachability	api	done ✓
MCP server/discover	mcp	done ✓	POST https://mcp.exa.ai/mcp server/discover 2026-07-28 -> HTTP 400 JSON-RPC -32000 'Unsupported protocol version: 2026-07-28 (supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07)' (not -32022) => legacy; initialize offering 2026-07-28 answered protocolVersion 2025-11-25, serverInfo exa-search-server 3.4.2, Mcp-Session-Id issued, SSE response
MCP server card	api	done ✓	https://mcp.exa.ai/mcp/server-card 200 application/mcp-server-card+json (name ai.exa/exa 3.4.2, remote streamable-http, x-api-key optional); /.well-known/mcp/server-card.json 404 on mcp.exa.ai; exa.ai/docs/.well-known/mcp/server-card.json 200 application/json but empty body; exa.ai/.well-known/ai-catalog.json 404
A2A agent card	api	done ✓	exa.ai/.well-known/agent-card.json 404 and agent.json 404; docs-level https://exa.ai/docs/.well-known/agent-card.json 200 application/json protocolVersion '0.3' (Mintlify-generated, linked rel=agent-card)
Markdown docs	api	done ✓	GET /docs/search/quickstart with Accept: text/markdown -> 200 content-type text/markdown, vary includes Accept; /docs/search/quickstart.md -> 200 text/markdown. Link headers rel=llms-txt, agent-card, mcp-server-card, agent-skills
OpenAPI	api	done ✓	https://exa.ai/docs/exa-spec.json openapi 3.1.0, 'Exa Public API' 2.0.0, server api.exa.ai, paths incl /search /contents /answer /agent/runs /monitors /batches /v0/websets /v0/webhooks /v0/teams/me
OAuth metadata	api	done ✓	mcp.exa.ai PRM 200 (resource https://mcp.exa.ai/mcp, AS https://auth.exa.ai, scope mcp:tools); auth.exa.ai AS metadata: client_id_metadata_document_supported true, registration_endpoint (DCR), grants authorization_code, refresh_token, jwt-bearer, PKCE S256; no device_authorization_endpoint; no agent_auth block. exa.ai/auth.md 404, /.well-known/ucp 404
Search the web: Search 'Model Context Protocol specification 2026-07-28 release' via hosted MCP without a key	mcp	done ✓	tools/call web_search_exa keyless on mcp.exa.ai returned 3 results with titles/URLs/text about MCP 2026-07-28 (SEP-837, CIMD, tasks extension)
Fetch page contents: Fetch https://agentdrives.com as markdown via keyless hosted MCP	mcp	done ✓	tools/call web_fetch_exa keyless returned page markdown starting '# AgentDrives: make sure AI agents can run your product'
sign up: Sign up via the MCP OAuth login page (auth.exa.ai) with email	browser	done	DCR POST auth.exa.ai/api/oauth/register 201-ish JSON client_id issued; authorize redirected to auth.exa.ai login: email field, Continue with Google, Sign in with SSO; no GitHub button
sign up: Submit email on auth.exa.ai sign-up/login form	browser	blocked	After Continue: 'Please complete the verification challenge.' with a visible Cloudflare Turnstile 'Verify you are human' checkbox (screenshot browser/shots/004.png). Not clicked by us.
dashboard: Open dashboard.exa.ai (sign-up entry from docs)	browser	blocked
pay per call (we): x402 v2 per-call payments on api.exa.ai	api	done ✓	pay_tx.json: settled+confirmed+entitled x402 v2 exact on Base: /search tx 0xc698fc37…, /search deep tx 0x3415b8e5…, /contents tx 0x58e56c54…; ..not_offered
Stripe Projects onboarding: stripe projects add exa/api	cli	skipped	Documented at https://exa.ai/docs/reference/stripe-projects; our agent has no Stripe account
Continue with Google: Continue with Google on auth.exa.ai	browser	skipped	Button seen on auth.exa.ai login; pw sso google: this drive has no Google account
Continue with GitHub: n/a	none	skipped	No GitHub button on auth.exa.ai login (only Google, email, enterprise SSO); route not offered
person creates a key in the dashboard	none	skipped	docs: create keys at https://dashboard.exa.ai/api-keys; a person would act; not an assisted drive
Sign in with SSO	none	skipped	auth.exa.ai 'Sign in with SSO' link (company SSO)
MCP OAuth sign-in: DCR client + PKCE authorize for https://mcp.exa.ai/mcp (?login flow)	browser	blocked	DCR worked headless (client_id issued); authorize sends to auth.exa.ai login which needs an account; creating it hits the Cloudflare Turnstile 'Verify you are human' (same wall as email). CIMD advertised but we have no hosted client metadata doc; DCR used.
402 probes: Unauthenticated POSTs on api.exa.ai	api	done ✓	POST /search -> 402 with PAYMENT-REQUIRED (x402 v2, exact, eip155:8453, amount 7000 = $0.007 USDC, payTo 0x6d6E…9192) AND WWW-Authenticate: Payment method=tempo intent=charge (MPP), body tag X402_PAYMENT_REQUIRED; POST /answer and /agent/runs -> 401 INVALID_API_KEY 'Authentication required…Create a key at https://dashboard.exa.ai/api-keys' (no 402 offer). pay_tx.json paid /search, /search deep, /contents.
Search the web: keyless MCP search 'Exa search API rate limits documentation'	mcp	done ✓	Title: N/A URL: https://exa.ai/docs/reference/rate-limits Published: N/A Author: N/A Highlights: # Rate Limits > Default rate limits for Exa API endpoints ... ? Contact us at sales@exa.ai to discuss
Search the web: keyless MCP search 'x402 protocol version 2 specification'	mcp	failed	You've hit Exa's free MCP rate limit. To continue using without limits, create your own Exa API key. Fix: Create API key at https://dashboard.exa.ai/api-keys, and then update Exa MCP URL to this htt
Fetch page contents: keyless MCP fetch https://example.com	mcp	done ✓	# Example Domain URL: https://example.com Example Domain This domain is for use in documentation examples without needing permission. This is not a service; avoid relying on it for testing and monit
Fetch page contents: keyless MCP fetch https://www.rfc-editor.org/rfc/rfc9309	mcp	done ✓	# RFC 9309: Robots Exclusion Protocol \| RFC Editor URL: https://www.rfc-editor.org/rfc/rfc9309 Published: 2022-09-09 RFC 9309: Robots Exclusion Protocol \| RFC Editor Info # RFC 9309: Robots Exclusi
Run agent: Open MCP with tools=…,agent_run keyless	mcp	blocked	initialize on https://mcp.exa.ai/mcp?tools=…,agent_run without key -> HTTP 401, WWW-Authenticate: Bearer resource_metadata="https://mcp.exa.ai/.well-known/oauth-protected-resource/mcp", -32000 'Authentication required. Use OAuth or provide an API key.' (as documented: agent_run needs OAuth or key)
Buy an API key via Nevermined x402 card delegation: POST https://admin-api.exa.ai/team-management/nevermined/purchase-key	api	skipped	Docs https://exa.ai/docs/integrations/payments/nevermined.md: 'Each $7 purchase returns an Exa API key with $7 of Exa credits'. Unauthenticated POST -> 402 PAYMENT-REQUIRED x402v2 {"x402Version":2,"resource":{"url":"/purchase-key"},"accepts":[{"scheme":"nvm:erc4337","network":"eip155:84532","planId":"27800462147494506865542649899724877617306579171265399959488097895839186996870","extra":{"version":"1","httpVerb":"POST"}}],"extensions":{}}. $7 is over our $5/drive cap and needs a Nevermined card delegation we do not have.
Docs: Read llms.txt, docs index, OpenAPI, MCP docs	api	done ✓	exa.ai/llms.txt + /docs/llms.txt; .md pages; OpenAPI 3.1.0 exa-spec.json; team-management-spec.yaml (admin-api.exa.ai /api-keys CRUD); MCP docs list keyless/OAuth/API-key modes; docs_pass verdict: getting started, auth, errors found, examples good, fresh
API key headless: Create a scoped key via POST https://admin-api.exa.ai/team-management/api-keys	api	blocked	Documented Team Management API exists (create/list/get/update/delete keys) but it needs an existing service key from an account; account creation stopped at the Cloudflare Turnstile on auth.exa.ai; dashboard.exa.ai/api-keys behind Vercel Security Checkpoint (Code 21).
verify: verify	none	blocked	Not reached: sign-up stopped at Cloudflare Turnstile 'Verify you are human' on auth.exa.ai.
The first action: The first action	none	blocked	Not reached: sign-up stopped at Cloudflare Turnstile 'Verify you are human' on auth.exa.ai.
first call: first MCP call without account	mcp	done ✓	keyless hosted MCP web_search_exa returned results (documented keyless mode: 'Free rate-limited usage without sign-in or API key')
: core task via API	api	blocked	POST /search type=deep needs an API key (or x402: we paid one, pay_tx tx 0x3415b8e5…); behind the door: no account/API key
: core task via API	api	blocked	POST /answer -> 401 INVALID_API_KEY without key; no x402 offer on /answer; behind the door: no account/API key
: core task via API	api	blocked	GET /agent/our records needs key; MCP agent_run needs OAuth/key (401); behind the door: no account/API key
: core task via API	api	blocked	POST /agent/runs needs key; behind the door: no account/API key
: core task via API	api	blocked	POST /v0/websets needs key; behind the door: no account/API key
: core task via API	api	blocked	websets enrichments need key; behind the door: no account/API key
: core task via API	api	blocked	POST /monitors needs key; behind the door: no account/API key
Search via API: POST /search with own key	api	blocked	No key: behind the door: no account/API key; keyless MCP route done instead
Contents via API: POST /contents with own key	api	blocked	No key: behind the door: no account/API key; keyless MCP route done instead
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: secondary capability via API	api	blocked	Documented in exa-spec.json/docs; needs an API key: behind the door: no account/API key
: check documented	none	blocked	Documented: POST /v0/websets/{id}/cancel in exa-spec.json; docs websets/api/websets/searches/cancel-a-running-search.md. Not callable without an account (behind the door: no account/API key)
: check documented	none	blocked	Documented: POST /batches/{id}/cancel in exa-spec.json; docs reference/batches/cancel-a-batch.md. Not callable without an account (behind the door: no account/API key)
: check documented	none	blocked	Documented: GET /v0/webhooks/{id}/attempts and /v0/events in exa-spec.json. Not callable without an account (behind the door: no account/API key)
: check documented	none	blocked	Documented: docs admin/security/zero-data-retention.md: 'ZDR is available on Enterprise plans and enabled per team. Contact sales@exa.ai'no API. Not callable without an account (behind the door: no account/API key)
: check documented	none	blocked	Documented: GET /v0/teams/me in exa-spec.json; docs admin/team-management.md (dashboard). Not callable without an account (behind the door: no account/API key)
: check documented	none	blocked	Documented: docs admin/billing.md: billing dashboard dashboard.exa.ai/billing (add credits, auto recharge, invoices); API key usage via GET admin-api /api-keys/{id}/usage. Not callable without an account (behind the door: no account/API key)
: check documented	none	blocked	Documented: team-management-spec.yaml: admin-api.exa.ai/team-management /api-keys create/list/get/update/delete; dashboard.exa.ai/api-keys. Not callable without an account (behind the door: no account/API key)
Docs claim: Search the web with a natural-language or keyword query: POST /search	api	blocked	402 x402/MPP or 401 without key; no key obtainable (Turnstile at sign-up). Our x402 payment proved it (pay_tx)
Docs claim: Search the web with a natural-language or keyword query: web_search_exa	mcp	done ✓	keyless hosted MCP returned results
Docs claim: Run deep/multi-step research search with structured output and citations: POST /search (type=deep)	api	blocked	needs key; our x402 payment proved the deep call (pay_tx)
Docs claim: Fetch full page text/highlights/summary for known URLs: POST /contents	api	blocked	needs key or x402; we paid one (pay_tx)
Docs claim: Fetch full page text/highlights/summary for known URLs: web_fetch_exa	mcp	done ✓	keyless hosted MCP returned page markdown
Docs claim: Get a direct LLM answer to a question with citations: POST /answer	api	blocked	401 INVALID_API_KEY without key
Docs claim: Run an autonomous research/enrichment/list-building agent from a single query: POST /agent/runs	api	blocked	401 INVALID_API_KEY without key
Docs claim: Run an autonomous research/enrichment/list-building agent from a single query: agent_run	mcp	blocked	401 + resource_metadata: needs OAuth or key
Docs claim: Check status of / resume a long-running agent run: GET /agent/our records	api	blocked	needs key
Docs claim: Check status of / resume a long-running agent run: agent_run (with runId)	mcp	blocked	needs OAuth or key
Docs claim: Enrich a batch of entities with structured data in one run: POST /agent/runs (input.data array)	api	blocked	needs key
Docs claim: Enrich a batch of entities with structured data in one run: agent_run	mcp	blocked	needs OAuth or key
Docs claim: Create a Webset: a verified, enriched dataset built from a query and target count: POST /v0/websets	api	blocked	needs key
Docs claim: Define enrichment fields that populate extra data per webset item: POST /v0/websets/{webset}/enrichments	api	blocked	needs key
Docs claim: Create a scheduled/recurring search that surfaces new matching results over time: POST /monitors	api	blocked	needs key
walk to last click: Open the cheapest paid option	browser	blocked	No account: sign-up stopped at Cloudflare Turnstile; billing lives at dashboard.exa.ai/billing (docs admin/billing.md: 'Add credits, configure auto recharge, and view invoices'), which answers Vercel Security Checkpoint 'Failed to verify your browser, Code 21'. Pricing is pay-as-you-go credits, free tier $10/month without a card (llms.txt). Agent rails: x402 v2 and MPP on /search and /contents (paid by us), Nevermined $7 key purchase, Stripe Projects.
cancel: Cancel what we started	none	skipped	Nothing recurring started: keyless MCP and per-call x402 payments (by us) only. Docs: pay-as-you-go credits with optional auto recharge configured in the dashboard billing page; no subscription to cancel on the free tier.
delete: Delete what the drive made	none	done ✓	No Exa account was created (sign-up blocked before submission; inbox empty). Keyless searches/fetches store nothing for the caller. One public OAuth client (DCR, mcp_10d6…) remains registered at auth.exa.ai: no documented way to delete it (no RFC 7592 endpoint advertised), no grant was ever issued to it.