Skip to main content
The platform is useful with zero setup and gets a lot more capable with a key.
“Free vs paid” is about your plan, not how you connect. For MCP you can also Connect with OAuth - log in instead of pasting a key - and the tools follow your team’s plan either way: a free team connected over OAuth still gets the 3-tool taste, a paid team gets the twelve read + action tools - or all fifteen if you allow an optional credit budget on the consent screen. Without a budget, credit spending over OAuth is blocked.

​
Free - anonymous

No signup, no key. Built so anyone can ask about any product’s pain points from their AI client and get a real answer. Every response points back to the full report on Reechee.
  • Tools / endpoints: search_products, get_pain_points (a taste - summary, top themes, a couple of quotes), get_competitors.
  • Access: read-only, rate-limited by IP (15/min, 100/day).
  • Great for: quick research, embedding “what do people dislike about X” into an agent, evaluating the data before you commit.
A paid-team key (Starter and up) turns the same REST API and MCP server into something your agents can operate.
  • Deeper reads: the full pain-point report (every theme, quote, and trend), your opportunities with filters, individual opportunity detail, your watchlist, credit balance, and a consolidated account overview (subscription, credits, and watchlist usage).
  • Safe write actions: follow / unfollow products, mark opportunities viewed, set status.
  • Credit-spending actions: unlock a buyer’s email/phone, unlock the buying committee, and generate a full pain-points report. These spend Reechee credits and require a spend budget on the credential (see below).
  • Higher limits: 60-1000 requests/minute by plan.

​
At a glance

​
Spend caps on credit actions

The three credit-spending actions require a spend budget on the credential - a rolling 30-day ceiling on the credits it can spend. It’s the safety guardrail for autonomous agents: with no budget the credential can’t spend at all (it gets 403 spend_cap_required), so an agent can never burn more than you allowed. For API keys, set the spend cap when you create the key in Settings → API keys. For OAuth connections, allow the optional credit budget on the consent screen (paid teams; the budget is fixed per connection - reconnect to change it). Two distinct 402s tell spend failures apart: spend_cap_reached (the key hit its cap) vs out_of_credits (the team is out of credits). See the errors guide.

​
Upgrade

Create a key under Settings → API keys (paid teams). See pricing for plans, and the authentication guide to start using a key.

Get your API key

Settings → API keys