Tool credit costs
Credits are deducted when a tool call starts.
Backlink tools are enabled by default. A deployment can temporarily remove both tools with an operational kill switch. Check
/v1/capabilities for the live tool surface and current costs.
get_search_performance needs a connected Search Console property, get_website_analytics needs a connected Google Analytics property, and get_ad_performance needs a connected Google Ads account with an activated ad account. Each is charged only once a connected website or ad account is resolved, so a call that has nothing to read is not charged. Listing connections and the connection endpoints are always free.
Monitors
A monitor check costs the normal price of each tool it runs, charged as each step runs. Creating, listing, changing, and deleting monitors, reading their history, and logging changes are free.create_monitorreturns the cost per check and per month. Use/v1/me/monitoring/estimateto see it without creating anything.- Asking for a monitor that already exists returns it with no charge.
- A check never charges into a negative balance. When the balance can’t cover the next check, the monitor pauses and keeps its history. It resumes by itself once credits are added.
list_monitorsreturnscredits.runway_weeks: how many weeks the balance lasts at the current monitor spend.
Buy credits
Buy credits in Billing. The current app flow supports $10 increments, where $10 buys 1,000 credits. Purchases are handled by the OpenRush dashboard.For developers
Check balance
Rate limits
Protected endpoints use account-level minute, hour, and day windows. Successful protected calls include the most constrained window:
Default limits:
Some accounts may have custom credential limits.