# discatch

discatch watches the internet for a brand, a competitor, a topic, or a forum.
When someone talks about it, discatch catches the post and hands it to the
agent that asked. Usually that is you.

## The manifest

One call explains every surface. It also comes back for any unknown route.

    GET https://api.discatch.com/v1/doctor

The same JSON, rendered for humans: https://discatch.com/doctor

## Get a key

No email, no card. A small allowance on free sources, rate-limited by IP.

    POST https://api.discatch.com/v1/keys/trial

Claim it later with `POST /v1/keys/claim { email }` to keep the key and raise
the allowance. Trial keys and claims arrive with roadmap phase 1b; the doctor
manifest says what works today.

## Two calls to try

    curl -X POST https://api.discatch.com/v1/quote -d '{"query":"your product"}'
    curl -X POST https://api.discatch.com/v1/search -H 'Authorization: Bearer <key>' -d '{"query":"your product","since":"7d"}'

Every endpoint that consumes units accepts `dry_run: true` and returns the
quote alone. The quote is a ceiling with locked unit prices; the charge never
exceeds it. Every error is `{ code, message, next_action }`; act on
`next_action`.

## Rules

- You name sources, never providers. Sources: hackernews, discourse, web,
  news, stackexchange, github in phase 1b; bluesky, mastodon, youtube,
  producthunt planned; reddit, x, linkedin reserved until a cleared path
  exists. The manifest lists what is live.
- Planned means planned. The REST API serves the doctor manifest today.
  Search, catches, and the MCP server land in later roadmap phases. The
  manifest and every page say what is live.
- discatch never posts on your behalf. Reply drafting is your job, or your
  human's.
- Every call that costs units can be quoted first. The quote is a ceiling.
  The charge never exceeds it.
- Every error carries a next_action. Act on it.

## Pages in reading order

1. https://discatch.com/doctor — the manifest
2. https://discatch.com/docs/quickstart — first search, first catch
3. https://discatch.com/pricing — five units, a quote before every call, free to start
4. https://discatch.com/sources — what you can name in a request, and what is planned
5. https://discatch.com/api — the REST surface, endpoints, result shape, error envelope
6. https://discatch.com/mcp — the MCP server, 20 tools, copy-paste configs
7. https://discatch.com/push — catch destinations that wake you
8. https://discatch.com/for/agents — the full agent page
9. https://discatch.com/free/hackernews-alerts — free Hacker News keyword alerts
10. https://discatch.com/free/reddit-alerts — free Reddit keyword alerts, planned
11. https://discatch.com/about — who builds it and why
12. https://discatch.com/llms.txt — every page, one line each
13. https://discatch.com/llms-full.txt — every page, in full

## What is not live yet

The remote MCP server with OAuth 2.1 is roadmap phase 3. Until then the REST
API with a trial key is the surface. Sources marked planned are refused with
`source_unavailable` and a `next_action` naming the sources that are live.