Credits and billing

How metering works

One credit per tool call, including failed calls (the forensic failure report is usually enough to fix the task in one more turn). reflex_auth is free and unmetered. The balance is decremented against a local cached value, and usage syncs in the background with an offline buffer. Metering never blocks or slows a call: your key is validated when the server starts, and everything after that runs locally.

Free pack terms

Signup grants 30 free credits that expire 14 days after issuance. They exist so you can evaluate Reflex properly, not as a permanent free tier.

Packs and prices

PackPriceCreditsTasks (2-3 credits each)
Starter$9150~50-75
Pro$19500~165-250
Power$491,800~600-900

Paid credits never expire, and balances stack: buy a second pack any time and the credits add to your existing balance. Full pricing is at /pricing.

Refunds

If a pack isn't working out, email support within 14 days and we refund the unused balance, no interrogation. Refunds for consumed credits are case by case, biased toward yes.

Reading the usage table

Your dashboard shows a daily table of date, total calls, and per-tool counts for the last 30 days. We only know which tool ran, never what page it touched.

What is and isn't sent to the server

The only things that cross the network are your API key and counts of tool calls. Page content, URLs, credentials, and sessions never leave your machine.

Your machine stays here
Claude Desktop
or Cursor, Claude Code, any MCP client
Reflex MCP server
runs locally
Your Chrome
your real browser and logins
Pages, sessions, passwords
read and acted on locally
API key + call count
pages never cross
Reflex servers
  • Is this key valid?
  • Credit balance
  • Usage counts
  • Paddle payments

No path exists for your pages, logins, or sessions to reach us.


Stuck? nitaiaharoni1@gmail.com