Exa (legacy)
Exa (legacy) is entry 1186 on the integrations list SHAI was asked to match. SHAI has not written this tool up, so it will not describe it — what it records is the route.
needs-operator-provider
How SHAI connects to it
SHAI connects to it through Pipedream, which holds the sign-in so no token ever reaches SHAI or the model. Pipedream's own component for it is `exa`, which it shares with entry 44 of this list — connecting it here and connecting it there are the same connection.
What it needs
the operator's Pipedream project — then nothing from you but a sign-in
Exa's legacy record and its current one are one Pipedream component, `exa`. Connecting it here and connecting entry 44 (Exa) are the same connection. One click once the operator connects a Pipedream project to this deployment.
Route read from https://github.com/PipedreamHQ/pipedream@58ecb26:components/exa/exa.app.mjs · verified 2026-09-16 · entry 1186 of the integrations list
Whatever a run does with this tool goes through one door and one approval row: reading is allowed by default, anything that writes, sends or spends stops and asks first, and you can set that per tool on Connections. Plain text for this page: /integrations/exa-legacy/index.md.