Skip to main content
Jobo bills per delivered job, not per request. Your plan’s coverage applies first, and your prepaid wallet pays for the rest at the pay-as-you-go rate: $3.00 per 1,000 jobs.
These are list prices. Accounts on their original pricing see their own prices and rate under Billing in the dashboard. To compare plans, see the pricing page.

​
How metering works

Every job that Search, Feed, Export, or Outbound delivers counts once, including a job you already received on an earlier page. Empty pages and empty polls cost nothing. Each delivered job is covered in this order:
  1. The Unlimited plan, for Feed, Export, and Outbound.
  2. Your Job Search plan’s included jobs.
  3. The wallet, at the pay-as-you-go rate.

​
Plans

Job Search plans (Lite to Scale) give you one pool of included jobs:
  • The pool is shared by Search, Feed, Export, and Outbound. Feed covers the job feed, managed feeds, and saved feeds. MCP search and GET /api/companies/{id}/jobs count as Search.
  • Once the pool is used, every product continues at the pay-as-you-go rate while the wallet has funds.
  • Included jobs reset each billing month.
  • An upgrade applies immediately. You pay the prorated difference, your billing date stays the same, and usage already recorded this month still counts.
A canceled subscription stays active until the end of its billing period. Approved startups get 50% off Unlimited for 12 months through jobo.world/startups.

​
Metered endpoints

Search and Feed bill only for the jobs a page delivers: a page with fewer results than page_size costs less. Geocode and Company Enrichment are flat endpoints. They debit before the work begins and refund any 4xx or 5xx. A geocode 200 with succeeded: false is still charged. Company Enrichment is in beta, available on activation through support@jobo.world. Cached profiles are billed like fresh ones. What a profile costs explains when a 202 and its status poll are charged. Auto Apply pricing will be announced at launch. Sandbox applications are free and need no approval; live ones need live access.

​
Worked example: a 100-job page

POST /api/jobs/search with "page_size": 100 returns 100 jobs. What it costs depends on your coverage: If the same request returns only 30 jobs and you have no plan, it costs 90 credits ($0.09). The wallet must still cover a full page before the request runs. See Request flow.

​
Wallet and credits

Your wallet is a prepaid balance, always shown in dollars first.
  • Add funds with Top up wallet on the dashboard’s Billing page, from $5 to $1,000 per top-up. Contact support for higher limits or volume pricing.
  • The balance never expires and updates within a few seconds of payment.
  • New accounts get a $5 free starting balance, no credit card required, when they verify their email address.
  • Your card is only ever charged the subscription price. Usage beyond your included jobs comes from the wallet, which you top up yourself.
  • When the wallet reaches $0, requests that need it return 402 until you top up. Requests fully covered by included jobs or the Unlimited plan keep working.
The API meters the wallet in credits: 1,000 credits = $1.00. The pay-as-you-go rate is 3 credits per job. Every credit figure in an API header or error converts to dollars this way.

​
Free endpoints

​
Always free

These endpoints never charge the wallet or use included jobs. All except GET /api/companies/{id} still count toward your rate limits. An idempotent replay (X-Idempotent-Replay: true) is not billed again.

​
No per-job charge on the Unlimited plan

On the Unlimited plan, the job feed, managed feeds, saved feeds, Export, and Outbound use no included jobs and never charge the wallet. The metered endpoints table lists their endpoints and dashboard pages. Search is not covered: it uses a Job Search plan’s included jobs if you also hold one, and is pay as you go otherwise. Geocode and Company Enrichment are charged as usual, and rate limits still apply.

​
Request flow

Every metered request passes these checks in order: For Search and Feed, the wallet check debits nothing but assumes a full page: page_size jobs on Search (default 25, max 100) or batch_size jobs on Feed (default and max 1,000), minus your remaining included jobs. With no plan, a default feed request needs a balance of 3,000 credits ($3.00), even if it then delivers fewer jobs. On a low balance, send a smaller page_size or batch_size. Feed on the Unlimited plan skips the check. Flat endpoints (Geocode and Company Enrichment) debit their price at this step instead. Settlement fails only when parallel requests or another spend used the credits after the check. Top up and retry the same request. Failed requests are free: authentication failures, validation errors, rate-limited requests, and server errors never charge the wallet. See 402 Payment Required for the error body. Metered Search and Feed responses report the charge in X-Credits-Deducted and the balance in X-Credits-Balance. A rare X-Billing-Status: Unconfirmed means the jobs were delivered but settlement could not be confirmed: do not replay that page automatically. See Response headers for when each header appears.

​
Spend alerts

Jobo emails Wallet and billing alerts about a low balance, an empty wallet, your included jobs, and plan payments. Turn them on or off under Account → Settings → Notifications in the dashboard. To track spend against your own budget, read X-Credits-Deducted and X-Credits-Balance on metered responses.

​
Wire names vs customer terms

Headers, JSON fields, and enum values keep their historical names. This table maps them to the terms these docs use:

​
Business billing details

Stripe Checkout collects your billing address. Businesses can also add a company name and a VAT/GST/tax ID, and both appear on every invoice. To edit them later, use Manage billing in Stripe on the dashboard’s Billing page, shown while you have an active subscription.