Credits and rate limits

OpenRush uses credits for tool calls. MCP, Dashboard sessions, and API keys share the same account balance. Most users should check credits in Billing. Developers can also read the balance through the API.

Tool credit costs

Credit deduction happens before provider work for billed REST tool calls.

Tool	Credits
`inspect_domain`	3
`discover_competitors`	5
`research_keywords`	3
`compare_keyword_coverage`	5
`inspect_serp`	2
`inspect_search_visibility`	3
`audit_site`	10
`inspect_keyword`	2
`inspect_page`	2
`export_dataset`	0

Backlink tools are feature-gated. If your account has access, they appear in /v1/capabilities with their current credit costs.

Check balance

curl "https://api.openrush.io/v1/me/credits" \
  -H "Authorization: Bearer $OPENRUSH_KEY"

Response:

{
  "balance": 500
}

Buy credits

Buy credits in Billing. The current app flow supports $10 increments, where $10 buys 1,000 credits. The API exposes your balance through /v1/me/credits. Purchases are handled by the OpenRush app.

Rate limits

Protected endpoints use account-level minute, hour, and day windows. Successful protected calls include the most constrained window:

Header	Meaning
`X-RateLimit-Limit`	Limit for the current constrained window
`X-RateLimit-Remaining`	Remaining requests in that window
`X-RateLimit-Reset`	Unix timestamp when the window resets
`Retry-After`	Seconds to wait after a `429`

Default limits:

Window	Default
Minute	60
Hour	1000
Day	10000

Some accounts may have custom credential limits.

​Tool credit costs

​Check balance

​Buy credits

​Rate limits

Tool credit costs

Check balance

Buy credits

Rate limits