Skip to main content
Every plan gets the developer platform. Start free, no card needed: pay-as-you-go includes the full REST API and the full MCP toolset, and you pay only for the credits you spend. Subscribing adds the things a team needs around it.

​
What pay-as-you-go includes

  • Every read: product search, the full pain-point report (every theme, quote, and trend), competitors, your opportunities with filters, individual opportunity detail, your watchlist, credit balance, and a consolidated account overview.
  • Safe write actions: follow / unfollow products, mark opportunities viewed, set status.
  • Credit-spending actions: unlock a buyer’s email or 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). Buy credits in packs when you need them; see credits and unlocks for what each action costs.
  • Both ways to connect: an API key from Settings → API keys, or OAuth Connect from your MCP client.
  • Rate limit: 60 requests/minute per key or connection.

​
What subscribing adds

  • Seats: bring your team into one workspace.
  • Webhooks and integrations: every new opportunity pushed to your CRM, Slack, or automation tool from Settings → Integrations.
  • Higher limits on bigger plans: 300 requests/minute on Scale, 1000 on Agency.
  • Social sources: LinkedIn and Reddit opportunities on Scale and up.

​
At a glance

A team still on a plan from before pay-as-you-go pricing gets three read tools (search_products, a pain-points taste, and get_competitors) until it moves to pay-as-you-go or subscribes.

​
Spend caps on credit actions

The 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: an API key with no cap 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 (it cannot be added to an existing key later). For OAuth connections, the consent screen has an optional credit budget: leave it empty for no limit, or set one (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.

​
Get started

Create a key under Settings → API keys, or connect your MCP client with OAuth. See pricing for plans, and the authentication guide to start using a key.

Get your API key

Settings → API keys