Eby Exa
Monitor the web for new results
Creates a monitor that reruns an Exa search on a schedule and sends only new, deduplicated results to your webhook.
Description
Use it to follow signals such as funding rounds, competitor announcements or news. Write the query around the ongoing signal rather than a date range: each run only fetches content from after the previous run. Store the `webhookSecret` from the response, which is returned only once and verifies webhook signatures.
create-monitor.md
Monitor the web for new results
Creates a monitor that reruns an Exa search on a schedule and sends only new, deduplicated results to your webhook.
Use it to follow signals such as funding rounds, competitor announcements or
news. Write the query around the ongoing signal rather than a date range:
each run only fetches content from after the previous run. Store the
webhookSecret from the response, which is returned only once and verifies
webhook signatures.
Set up
Use the first option your agent supports.
API (official)
- Base URL: https://api.exa.ai
- Endpoint:
POST /monitors - Auth: send the header
Authorization: Bearer $EXA_API_KEY - Get a key: https://dashboard.exa.ai/api-keys
- Docs: https://exa.ai/docs/get-started/quickstart
Before doing anything else, make one read-only call to confirm access.
Rules
- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.
Built from these files in the repository
The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.
Ways in
| Route | Source | Call | Required | Docs |
|---|---|---|---|---|
| Official | POST /monitors | API key in $EXA_API_KEY | Docs |