Core concepts
Credits & pricing
One credit balance per account powers REST, the App and MCP. Credits are metered per endpoint tier — and failed, empty and blocked calls are always free.
You pay for data delivered, not attempts
Failed, empty, blocked and not-found calls charge
0 credits. In a fan-out, each failed platform is free and only the successful, non-empty legs are billed. See the failed-calls-free rule.Credit tiers by endpoint
Credits are tiered by call type, because a cross-platform search costs far more than a cached detail lookup. These are the launch defaults (1 credit ≈ $0.01 nominal retail).
| Endpoint | Credits | Billing unit |
|---|---|---|
/v1/listing | 1 | per platform |
/v1/price | 1 | per platform |
/v1/reviews | 2 | per 20-review block, per platform |
/v1/availability | 3 | per listing-window, per platform |
/v1/search | 5 | per platform |
/v1/price-compare | 5 | per call (one property, many OTAs) |
/v1/jobs/{jobId} | 0 | polling is always free |
Plans & top-ups
| Plan | Price / mo | Credits / mo | Rate limit |
|---|---|---|---|
| Free / Sandbox | $0 (no card) | 100 one-time | 30 / min |
| Starter | $19 | 3,000 | 60 / min |
| Pro | $99 | 20,000 | 120 / min |
| Scale | $499 | 120,000 | 300 / min |
| Enterprise | Custom | Custom | Custom |
Top-up packs: $10 → 1,000, $50 → 5,500, $200 → 24,000. See the pricing page for the full breakdown and a credit calculator.
How credits behave
- One balance per account. REST keys, the App and the MCP/Connectors channel all draw from the same ledger.
- Cache hits still bill at the full endpoint tier — caching is our margin lever, not a customer discount. Polling
/jobsis the one exception (always 0). - Charge on success only, pre-authorized via a reservation: a low balance is rejected with
402 insufficient_creditsbefore any upstream spend. - Subscription credits reset monthly; top-up credits never expire. Usage spends the soonest-to-expire credits first, so you never lose top-up value to a reset.
Read your usage
meta.creditsCharged reports the total for a request, and meta.platformResults[].creditsCharged breaks it down per platform. The dashboard shows the full ledger and per-endpoint usage over time.