Credits

RankParse is prepaid. Each billable API call deducts credits from your workspace balance, and there is no subscription. New accounts start with 100 free credits and no card. Credits never expire.

How billing works

• One balance per workspace. Everyone in a workspace, and every API key it owns, spends from the same balance. See Shared credits.
• Charged before the work. The credit is deducted in a single atomic step before the query runs, so parallel requests cannot spend the same credit twice.
• Cache hits cost the same as misses. Caching only makes the answer faster. See Response format.
• Failures are refunded automatically in the cases listed under Refunds.
• Every response tells you what happened. credits_used is the amount billed for that call (after any refund) and credits_remaining is your balance afterwards.

{
  "data": { "score": 94 },
  "domain": "github.com",
  "credits_used": 1,
  "credits_remaining": 99
}

Check your balance

GET /v1/credits is free and returns the balance:

curl "https://api.rankparse.com/v1/credits" \
  -H "X-API-Key: rp_your_key"

import os
import requests

resp = requests.get(
    "https://api.rankparse.com/v1/credits",
    headers={"X-API-Key": os.environ["RANKPARSE_API_KEY"]},
)
print(resp.json()["credits"])

const resp = await fetch("https://api.rankparse.com/v1/credits", {
  headers: { "X-API-Key": process.env.RANKPARSE_API_KEY },
});
const { credits } = await resp.json();
console.log(credits);

{ "credits": 842 }

You can also read credits_remaining from any billable response, or open Billing, Credits in the dashboard.

Cost per endpoint

Billed endpoints

The backlink and authority endpoints are documented under API reference.

Free endpoints (0 credits)

Variable-cost endpoints

Refunds

Not refunded:

• Empty results. A domain with no data returns 200 with data: [] and is billed normally.
• Partial results, except the domain-authority case above.

Buying credits

Credits are sold as one-time purchases. Buy any amount from 100 to 500,000 credits in the dashboard. The price per credit depends on the size of the purchase:

Buy from the pricing page or Billing, Credits in the dashboard. The live tiers are also available from the public, free GET /v1/pricing, which is the source of truth if prices change:

curl "https://api.rankparse.com/v1/pricing"

{
  "tiers": [
    { "min": 0, "price_per_credit": 0.01 },
    { "min": 10000, "price_per_credit": 0.008 },
    { "min": 100000, "price_per_credit": 0.006 }
  ]
}

Vouchers can be redeemed on the same page. Only workspace owners and admins can buy credits.

Auto recharge

Auto recharge buys credits for you when your balance runs low, so calls never fail on an empty account. Configure it under Billing, Credits:

Defaults when you first save a card: threshold 500 credits, top-up 5,000 credits.

• Turning it on sends you to Stripe to save a card. Nothing is charged at that point.
• A top-up is checked after each successful charge, and runs in the background without slowing the response.
• At most one recharge runs at a time, with at least five minutes between recharges.
• If a payment is declined, auto recharge turns itself off and the dashboard shows why. Add a card to turn it back on. One decline is enough to disable it.
• Auto recharge never overrides your spend cap. A recharge that would exceed the cap does not run.
• Free routes never trigger a recharge, because they spend no credits.

Spend cap

A spend cap limits the credits a workspace can spend per calendar month (UTC). Set it under Billing, Credits, or leave it blank for unlimited.

• When a call would take you past the cap, it fails with 402 and code spend_cap_reached.
• Refunded calls do not count toward the cap.
• It is a soft limit. The check happens before the charge, so requests running at the same moment can take spend slightly past it.
• The month-to-date figure in the dashboard is the same counter the cap is enforced against.
• Only the workspace owner can change the cap.

Shared credits in a team workspace

Everyone in a workspace spends from the same balance and the same monthly cap.

When auto recharge is on, a teammate's usage can trigger a recharge on the owner's saved card. Members create their own API keys, and owners and admins can manage all of them.

Low balance alerts

RankParse emails the workspace owner once a week when the balance drops under 1,000 credits, and when credits run out.

Insufficient credits

When the balance cannot cover a call, the API answers 402 and does not run the request:

{
  "error": "Payment Required",
  "code": "insufficient_credits",
  "message": "Add credits at https://rankparse.com/pricing"
}

No credits are deducted for the failed call.

Related