Credits & Pricing

Every account has one credit balance. Calls deduct credits atomically at execution time; failed calls are refunded — you only pay for calls that return results.

Costs per call

/match examples: both sides passed as already-parsed JSON → 2 credits. resume_file + parsed role → 3. resume_file + jd_url → 4. Parsing once and reusing the JSON across many matches is the economical pattern for screening pools.

One balance, every surface

REST calls, MCP connector tool calls, and OAuth-connected clients all draw from the same balance and appear in the same usage log. credits_used in every response envelope tells you what the call cost; the dashboard shows remaining balance and per-period usage.

Starter credits

New accounts start with 100 free credits — enough to parse and match a real pipeline before paying anything. The free normalize endpoints stay free on every plan.

Plans

Monthly subscriptions grant credits on each billing cycle and raise your rate limit. The per-credit price falls as tiers rise.

Upgrades take effect within about a minute of payment — no key changes needed; existing keys automatically inherit the new plan’s limits.

Credit packs (pay as you go)

One-time top-ups, no subscription required. Packs are deliberately priced above the subscription per-credit rate — if you buy regularly, a plan is always the better deal.

Purchased credits never expire and survive plan changes, including cancelling a subscription.

Running out

A call that would exceed your balance fails fast with 402 insufficient_credits before any processing happens — no partial charges, no surprise work.