Skip to main content
Every call is made as a Reechee account. Start free, no card needed: pay-as-you-go includes the full REST API and MCP server. There are two ways to authenticate, both against the same base URL and MCP endpoint.
  • Connected (OAuth) - log in with your Reechee account in the browser, nothing to paste. Best for MCP clients like Claude that support it. Tools follow your team’s current plan.
  • API key - a bearer token you generate and manage. Best for scripts, servers, and agents that spend credits.

​
Connected (OAuth)

For MCP, you can connect with your Reechee account instead of a key. Point the client at:
A call with no credential gets a 401 carrying the OAuth discovery challenge (WWW-Authenticate), so the client discovers the OAuth flow by itself, opens a browser to log in, and shows a short consent screen (“Connect to Reechee”). Approve it and the client holds a token - nothing to copy or paste. This is the recommended way to connect Claude and other clients that support it; see Connect Claude. The /mcp/auth URL. Older setups point at https://mcp.reechee.io/mcp/auth. It keeps working and behaves exactly like the bare /mcp URL: same login, same server, same data. Tools follow your plan. The connected token exposes exactly what your team’s current plan allows, evaluated on every request: pay-as-you-go and every subscription get the full read + action set (sixteen tools, including the credit tools). A team still on a plan from before pay-as-you-go pricing gets three read tools until it moves over; the full set lights up on the next connect or tool refresh. The four credit-spending tools spend your credits. The consent screen has an optional credit budget, a rolling 30-day ceiling on what the connection can spend. Leave it empty for no limit. The budget is fixed for the life of the connection; to change it, disconnect and reconnect with a new one. Token lifetime and disconnect. Access tokens are short-lived (1 hour) and the client refreshes them automatically in the background. The connection stays alive as long as the client refreshes at least once every 30 days. Disconnect from the client’s own connector settings whenever you like - it revokes the token immediately, and the next request with it gets a 401. Reconnect any time by approving the consent screen again.
OAuth Connect and API keys are independent. Connecting an MCP client doesn’t create or need a key, and revoking one never affects the other. Pick per client: Connect for a browser login, a key for headless use.

​
API key

Every REST endpoint except GET /health needs a credential: an API key, or a Connected token. The REST API accepts either one in the same Authorization: Bearer header. Keys are the way in for scripts, servers, and clients without OAuth.

​
Create a key

In the app, go to Settings → API keys and create one. Keys are available on every plan, starting with pay-as-you-go. The full key is shown once, at creation - copy it then; it can’t be retrieved later. If the key will spend credits, set its spend cap now: the cap is set when the key is created and cannot be added later. A key looks like:
We store only a SHA-256 hash and a short display prefix - never the key itself.

​
Use a key

Send it as a bearer token. For the REST API:
For the MCP server, send the same header - see the per-client quickstarts. With a valid key, the MCP exposes the full toolset and get_pain_points returns the full report.

​
Revoke a key

Revoke a key any time from Settings → API keys. Revocation is immediate - the next request with that key gets a 401.

​
Errors

A missing key, or an invalid, revoked, or expired key, returns 401 unauthorized. A missing key gets a pointer to sign up:
Keep keys server-side. Anyone with a key can act as your team within its limits. Treat it like a password; rotate it (create a new one, revoke the old) if it leaks.