Social listening for AI agents

Yes. POST /v1/keys/trial returns a key with no email and no card, rate-limited by IP and fingerprint. The key has a small allowance on free sources, enough to prove the product on your own brand. POST /v1/keys/claim attaches an email and raises the allowance. The agent can hand the magic link to its human or, with mailbox access, follow the link itself.

Planned for roadmap phase 3, with OAuth 2.1 and PKCE at mcp.discatch.com. Until it ships the REST API with a trial key is the surface. Both reach the same account once claimed. Catches push independently of MCP because MCP is pull-only by spec.

Send the same body with dry_run: true, or call POST /v1/quote. The response is a ceiling with locked unit prices, a breakdown by unit kind, and a quote_id valid for 60 seconds. Lock the real call to the quote_id and the charge never exceeds the ceiling. If the ceiling exceeds your remaining allowance or a budget_usd you set, the call is refused before anything runs.

A search unit is $0.002 base, plus $0.0005 per result returned. These are placeholder rates that will change when provider costs and terms are settled. The quote at call time is the real price and depends on sources requested, coverage depth, and which providers are available for the call. Free sources are cheaper than waterfall sources.

Yes. DELETE /v1/catches/{id} removes a catch immediately. You can also pause a catch with POST /v1/catches/{id}/pause and resume it later. Catches that fire nothing cost nothing, so a dormant catch is free to keep. But if you want it gone, delete it and nothing further is charged.

A search runs once and returns results now. A catch is a search that stands: it re-runs on an interval (5 minutes, 15 minutes, 1 hour, 6 hours, or 24 hours), compares to what it already delivered, and pushes only what is new. A search consumes search and result units. A catch consumes an alert unit per firing plus result units per item delivered.

No. discatch delivers mentions from public online conversation: posts, comments, threads, and pages. It does not track whether ChatGPT, Gemini, or any other AI model mentions your brand in its answers. If you want that, you need an AI-visibility tool like Beamtrace or Cognizo. That is a neighboring category, not what discatch does.

REST API with a Bearer key today: every endpoint documented in the API reference. The CLI is npx discatch doctor to orient and npx discatch search to try a query. The remote MCP server with OAuth is planned for roadmap phase 3. Every page on the site shows the exact curl and MCP tool call side by side.

The next quote whose ceiling exceeds what remains is refused before anything runs. The 402 error carries the exact unit price that was refused, the remaining allowance, and a next_action that says how to add funds or narrow the query. discatch never truncates results and never overdraws. You set budget_usd on any call to cap it further.

Web, news, Hacker News, Discourse forums, Stack Overflow, and GitHub are the first set, roadmap phase 1b, which has not shipped yet; the doctor manifest’s sources_now list says what is live on any given day. Bluesky, Mastodon, YouTube, and Product Hunt are planned. Reddit, X, and LinkedIn are reserved until a cleared path exists. Indexed posts from those three networks arrive as web results with a domain field today.

No. discatch does not run agents and does not ship a local runner. It calls out, and the thing it calls starts the agent. Destinations include a signed webhook, a Claude Code or Codex command, a Doozy todo, a GitHub dispatch, email, and Slack. The webhook payload carries the events, the cursor, and a suggested action.