pricing
Pay for what your job did.
One meter, one unit, published numbers. Every quote on GoFundNode is computed against the rate card on this page — the same card the API serves at GET /v1/rate-card.
One compute-unit meter for every job.
Every job is priced in universal compute-units: credits, denominated at half a US cent, metered by what the job actually did — difficulty times runtime. The meter opens at a per-job start fee and then charges per second on the node, per browser action, and per byte in and out. Before anything runs, every submission is pre-quoted with an estimated cost (quote.estimated, the p50 for each metered dimension) and a hard maximum (quote.max, the p95, capped by the tier’s ceiling). The maximum is held against your balance at submit time; at settlement you are charged for the compute the job actually consumed and the unused remainder of the hold is refunded. No flat per-job fee, no surprise bills, no minimum commit.
credits = base[tier] + Σ metered[d] × rate[d] // per second, per action, per byte
credits = clamp(credits, min[tier], max[tier])
credits ×= tier_multiplier × surge // surge ∈ [0.8, 2.0], default 1.0
credits = round_half_up(credits)The surge multiplier tracks operator-pool utilization inside a fixed [0.8, 2.0] band and defaults to 1.0; the current value is always visible in GET /v1/rate-card, so a quote is never computed against a number you cannot see.
ats.application, transcribed from the source.
The numbers below are the authoritative rate card for the ats.application job type — the one apply.fun dispatches today. Source of truth is server/billing/rate-card.ts, locked by tests so the published numbers cannot drift silently from the billed ones.
Per-tier envelope
| Field | standard | priority | instant |
|---|---|---|---|
base — start fee, credits | 5 | 7.5 | 12.5 |
| Start fee at $0.005/credit | $0.025 | $0.0375 | $0.0625 |
min (pinned equal to base) | 5 | 7.5 | 12.5 |
max — hard cap, credits | 75 | 112.5 | 187.5 |
| Tier multiplier | ×1.0 | ×1.5 | ×2.5 |
The start fee is where the meter starts — never at zero — and is what a certified failed attempt charges. min equals base, so a near-zero-compute job floors at exactly the start fee. max is the anti-abuse ceiling applied before the tier multiplier and surge; the hold can never exceed it.
Metered dimensions (identical across tiers)
| Dimension | Meters | Credits per unit | Anti-fraud ceiling |
|---|---|---|---|
node_seconds | Wall-clock seconds on the operator node | 0.05 | 1,800 |
cpu_seconds | CPU-seconds consumed | 0.0625 | clamped to node_seconds |
mem_mb_seconds | MB of memory held × seconds | 0.0000625 | — |
bw_in_mb | MB of bandwidth in | 0.0625 | 50 |
bw_out_mb | MB of bandwidth out | 0.0375 | 50 |
actions | Browser actions performed | 0.0375 | 300 |
llm_in_tokens | LLM input tokens metered on the job | 0.0025 | 50,000 |
llm_out_tokens | LLM output tokens metered on the job | 0.0125 | 10,000 |
captcha_solves | Third-party captcha solves | 6.25 | 0 (solver default-off; 5 when enabled) |
Ceilings clamp any operator-reported value before actuals are computed; a value above its ceiling is clamped and flagged for review. The captcha dimension bills only if the third-party solver — which ships default-off behind an environment flag — actually ran; the cost is never added otherwise.
When a job fails
A certified failure (a whitelisted reason such as form_unreachable or ats_blocked) charges the start fee only, and the rest of the hold is refunded. A failure outside the certified list charges nothing. Cancellation — whether before dispatch or mid-run — refunds in full: the entire hold is released and you are charged nothing.
The typical submission, line by line.
The observed p50 profile for a successful Ashby or Greenhouse ats.application submission from the operator network, priced at the standard tier with surge at 1.0:
| Component | Metered | Rate | Credits |
|---|---|---|---|
Start fee (base) | — | — | 5 |
node_seconds | 90 | 0.05 | 4.5 |
cpu_seconds | 20 | 0.0625 | 1.25 |
mem_mb_seconds | 25,000 | 0.0000625 | 1.5625 |
bw_in_mb | 6 | 0.0625 | 0.375 |
bw_out_mb | 2 | 0.0375 | 0.075 |
actions | 25 | 0.0375 | 0.9375 |
llm_* tokens | 0 | — | 0 |
captcha_solves | 0 | — | 0 |
| Total | 13.7 credits ≈ $0.0685 |
LLM inference runs server-side, not on the node, so token dimensions meter to zero on a typical submission; the captcha solver is default-off. This ~13.7-credit, roughly seven-cent p50 is the same number behind the earnings example on the front page.
The meter scales with what actually happened: a long p95-style fill — 300 seconds, 60 actions, 15 MB in — meters to about 31.8 credits, roughly $0.16, still under the standard-tier hold cap of 75 credits.
Prepayment, not a currency.
Credits are bought with fiat and are a consumptive, single-issuer, non-transferable prepayment used only to obtain GoFundNode’s service — there is no token, wallet, self-custody, or stored value. Every purchase, every settlement, and every change to a tenant balance is one row in an append-only ledger, and every credit transaction visible to you is HMAC-signed, so you can reconcile your charges independently against signed events.
How to get credits today.
During the pilot beta, credits are granted through ops: email us, and we provision your tenant and top up your balance. Self-serve checkout arrives with general availability.
You can integrate before you ever talk to us: the staging sandbox at api.staging.gofundnode.com has open signup, the console at console.gofundnode.com works against either environment, and the wire is byte-identical to production — the only things that change are the base URL and the secret. Live system health is at status.gofundnode.com.