Skip to main content

​
Credit System

**1,000 credits = 1.00∗∗—Topupanywherefrom1.00** — Top up anywhere from 5 to $10,000 in the dashboard. Credits never expire.
Credits are the universal currency for metered API calls. You purchase credits in advance, and each API request atomically deducts the appropriate amount from your wallet. There are no monthly minimums, no overages, and no surprises — you only pay for what you use.

​
Metered Endpoints

These endpoints consume credits from your wallet on each request:

Jobs Search

10 credits per request ($10/1,000 searches)Full-text search across millions of job listings with filters for keyword, location, ATS source, remote status, and posting date.GET /api/jobs + POST /api/jobs/search

Geocode

1 credit per request ($1/1,000 lookups)Convert raw location strings into structured city/state/country with coordinates. Powered by deterministic parsing + LLM fallback.GET /api/locations/geocode

Auto Apply

200 credits per session ($0.20/session)Automated job application sessions using browser automation. Each session fills and submits one application form.POST /api/auto-apply/start

​
Subscription Endpoints

These endpoints are included with your subscription at no additional credit cost:
EndpointDescription
POST /api/jobs/feedBulk feed with cursor-based pagination. Stream up to 1,000 jobs per batch.
GET /api/jobs/expiredRetrieve expired/removed job IDs (up to 7-day lookback).
If your primary use case is bulk data ingestion (e.g., syncing your own job board), the Feed API is by far the most cost-effective option since it’s unlimited with your subscription.

​
Request Flow

Every metered API request goes through a 4-step pipeline before a response is returned:
1

Authenticate

The API validates your X-Api-Key header. If the key is missing or invalid, you receive 401 Unauthorized immediately and no further processing occurs.
2

Rate Limit Check

Your request is checked against per-minute, per-hour, and per-day rate limits for your plan tier. If any window is exhausted, you receive 429 Too Many Requests with a Retry-After header. No credits are deducted on rate-limited requests.
3

Credit Deduction (Atomic)

The required credits are atomically deducted from your wallet. If your balance is insufficient, you receive 402 Payment Required with the X-Credits-Required and X-Credits-Balance headers so you know exactly how much to top up. The deduction is all-or-nothing — partial charges never occur.
4

Response with Credit Headers

On success, the response includes X-Credits-Deducted and X-Credits-Balance headers so you can track spend in real time. Your application can use these headers to implement budget alerts or automatic top-ups.

​
Credit Response Headers

Every metered API response includes credit-related headers. Which headers appear depends on the response status:
HeaderWhen ReturnedDescription
X-Credits-Deducted200 (success)Number of credits consumed by this specific request.
X-Credits-BalanceAlwaysYour current wallet balance after this request.
X-Credits-Required402 onlyNumber of credits the request would have needed to succeed.

​
Successful Request

HTTP/1.1 200 OK
X-Credits-Deducted: 10
X-Credits-Balance: 9990
Content-Type: application/json

​
Insufficient Credits

HTTP/1.1 402 Payment Required
X-Credits-Required: 10
X-Credits-Balance: 3
Content-Type: application/json

{
  "status": 402,
  "error": "Insufficient credits",
  "credits_required": 10,
  "credits_balance": 3
}
Top up your wallet in the dashboard to resume immediately — no restart or key rotation needed.

​
Cost Calculator

Estimate your monthly spend based on typical volumes:
Use CaseVolumeCredits/RequestTotal CreditsMonthly Cost
Job searches1,0001010,000$10.00
Job searches10,00010100,000$100.00
Geocode lookups5,00015,000$5.00
Geocode lookups50,000150,000$50.00
Auto-apply sessions10020020,000$20.00
Auto-apply sessions1,000200200,000$200.00
Combined (typical startup)————
5,000 searches + 10,000 geocodes + 200 auto-applies——100,000$100.00
Feed and expired-jobs endpoints are included in your subscription — no credit cost regardless of volume.

​
FAQ

1,000 credits = 1.00.EachAPIrequesttoameteredendpointatomicallydeductscreditsfromyourwallet.Creditsneverexpireandtherearenomonthlyminimums.Youcantopupanywherefrom1.00. Each API request to a metered endpoint atomically deducts credits from your wallet. Credits never expire and there are no monthly minimums. You can top up anywhere from 5 to $10,000 in a single transaction.
Metered endpoints return HTTP 402 Payment Required. The response includes X-Credits-Required (credits the request needed) and X-Credits-Balance (your current balance). Top up your wallet and retry — no restart needed.
No. Credits are only deducted on successful (2xx) responses. If your request fails due to rate limits (429), bad parameters (400), authentication errors (401), or server errors (5xx), no credits are consumed.
Yes. Safety-cap rate limits apply per minute, per hour, and per day to prevent abuse and protect service quality. Paid subscribers get significantly higher limits. Credits are deducted only after rate limit checks pass. See the Rate Limits page for details.
Credits are non-refundable but they never expire, so there’s no urgency to use them. Contact support for exceptional circumstances.
No. The Jobs Feed (POST /api/jobs/feed) and Expired Jobs (GET /api/jobs/expired) endpoints are fully covered by your monthly subscription with no per-request credit cost.
Yes. You can configure low-balance alerts in the dashboard. You can also programmatically monitor spend by reading the X-Credits-Balance header on every metered response.
For high-volume usage (over $1,000/month), contact our sales team at enterprise@jobo.world for custom pricing.