Account types

An account type in JobFront is not one setting. It is three independent dimensions, and they compose freely — which is why two customers on the same named plan can behave completely differently through the API.

Find out what you are

One call answers every question below, and it is free on every plan and in every billing mode:

curl https://api.jobfront.com/v4/me \
  -H "Authorization: Bearer YOUR_API_TOKEN"

{
  "organization_id": "O_abc",
  "rate_limit": 600,
  "period_seconds": 60,
  "remaining": 593,
  "rate_limit_5h": 50000,
  "period_seconds_5h": 18000,
  "remaining_5h": 49821,
  "billing_mode": "subscription",
  "fields": {
    "tier": "default",
    "jobs":    ["categories", "commitment", "created_at", "description", "..."],
    "sources": ["brand_name", "id", "industry", "jobboard_format", "..."],
    "filters": ["categories", "cbsa", "commitments", "industries", "..."],
    "facets":  ["categories", "cbsas", "commitments", "industries",
                "jobboard_formats", "levels", "types"]
  }
}

The four lists are alphabetical and complete for your tier — the "..." above is this page eliding, not the API. Read them rather than hard-coding a list: a field moving tier changes this response and nothing you would have to be told about.

Your product plan is deliberately not in this response: it governs the dashboard product, not the API. Read it in the dashboard under Settings → Billing.

Everything that is in this response — rate tier, field tier, billing mode, and any balance — is shown together in the dashboard under API → Billing (app.jobfront.com/api/billing ↗). The two are separate purchases: changing one never changes the other.

1. Product plan

The named plan on your organization, and the one the pricing page is organised around.

Your plan governs product features and workspace limits — how many active jobs and sources you can hold, how many collections and admin accounts, how many leads and subscribers, and which surfaces (data, hiring signals, job boards, sales agent) are switched on for you.

It is a separate axis from your API plan. An organization can be on a paid product plan with no API access at all, or hold API access as an add-on. Feature access is granted per capability rather than bundled rigidly into a plan name, so jobfront.com/pricing ↗ is the authority on what a given plan includes today.

2. Rate tier — how fast you can read it

REPORTED AS rate_limit AND rate_limit_5h

Four tiers, each carrying two independently enforced windows — a 1-minute burst floor and a 5-hour budget that is your real allowance.

Limits are enforced per organization, shared across every token it holds, so minting more tokens does not buy more requests.

Full detail — the two windows, the X-RateLimit-* headers, and how to self-throttle — is on rate limits & billing.

The same tier also sets your data tier

Your rate tier carries a data tier with it — how much of each record you get back. One plan dimension, not two to provision:

Tiers are cumulative — default includes everything in min, max everything in default. GET /v4/me reports yours as fields.tier, with the exact field lists alongside it.

Field by field, on the Job object:

Two fields span tiers by child, exactly as they do in the collection exports — the two ladders are one:

The max step is the large one — 24 fields — and most of it is the AI enrichment layer: the structured requirement family, the schedule / contract / experience blocks, and the visa and relocation signals. The max filters that read those fields come with it.

Fields outside your tier are omitted, not null — the response is self-describing about what your plan includes, and a filter your tier cannot justify is rejected with an explanation rather than silently ignored.

3. Billing mode — how you pay for it

REPORTED AS billing_mode

Your plan carries a monthly included allowance of credits, and you can top up with credit packs whenever you need more. One record returned costs one credit; discovery is free.

To start, talk to your JobFront representative — begin at jobfront.com/pricing ↗. Once you are on a plan, managing it (changing tier, buying credits, cancelling, invoices) is self-serve under API → Billing in the dashboard.

subscription — unmetered

What an account reads as before an API plan has been applied to it. Nothing counts records and there is no balance to run out of; the only thing that can stop a call is a rate limit. If this is your billing_mode, the credit sections below are informational.

credits — prepaid

You buy a balance in advance, and each returned record costs 1 credit. Discovery is free, which is the point: you can always find out how much something will cost before paying for it.

Two protections come with prepaid mode:

• A page is capped to what you can afford. 10 credits left and limit=25 returns 10 records, not a 402. You are never served more than you can pay for.
• X-Credit-Balance rides on every response, and X-Credit-Low appears before you hit zero, so you can top up without polling a separate endpoint.

At 0, metered calls return 402 — but GET /v4/me, GET /v4/usage, the …/options facets and ?count=true on the list endpoints that support it keep working, so you can always inspect your account and size your next pull before topping up. (count is ignored on routes that do not return a list, and those calls are metered as usual — so at 0 they return 402 too.)

Where a balance comes from

Two sources, and they behave differently at the end of a billing period:

Your balance is the two combined, and spending draws down the allowance first — so a pack you bought is still there next period. API → Billing shows the split, along with the history of every grant and purchase.

MCP is billed identically to /v4 — a JSON-RPC batch is charged per operation, each call is capped at 25 records, and initialize, tools/list, ping and account_usage are free. Going through MCP is never cheaper or more expensive than the equivalent HTTP calls.

Roles inside an account

Distinct from everything above: the people in your organization each have a role, and it is a permission, not a billing type.

Roles do not affect API scope or quota. Any token, created by any admin, resolves to the same organization plan.

How they combine

Three dimensions, so an account is described by a combination rather than a single word:

The shapes above are illustrative combinations, not a fixed catalog — the dimensions are set independently, so anything sensible is possible.

Changing your account type

Your API tier, billing mode and balance are shown in the dashboard under API → Billing (app.jobfront.com/api/billing ↗). Organization admins can change tier, top up credits, or cancel there; enterprise terms go through your JobFront representative. (Settings → Billing is a different screen — it manages your product plan, not your API access.) Three things are worth knowing:

• Changes propagate within about a minute — plans are cached briefly, so a new tier or mode is live across every one of your tokens within roughly 60 seconds, with no redeploy and no new credential.
• Rotating a token does not change any of this. All of an organization's tokens share one plan, one quota and one billing mode, so a new token inherits everything immediately. See authentication.
• Your API plan and your product plan are independent. Cancelling one leaves the other untouched, and you can hold either without the other.

For what each of these costs today, see jobfront.com/pricing ↗.

Related

• Authentication & tokens — how a token resolves to an organization and its plan.
• Rate limits & billing — the windows, the headers, the credit costs.
• Conventions — scoping, pagination and the response envelope.
• Error catalog — 402 and 429 in full.