Pricing

Pay per call. No subscription, no minimum, no commitment. Per-page ops bill the page count (min one page); CSV, archive, data, and the utils hash/hmac/base64 ops bill per MB of input (min 1 MiB) — the data/sql engine at a higher tier; image ops bill per megapixel (min one); QR, barcode, metadata, UUIDs, JWT decode/verify, and the generate ops are flat per-call; the pipeline bills the sum of its steps. Calls debit your Relaystation balance — one balance funds cputools and every other Relaystation product.

These are the launch defaults. The live 402 challenge is always authoritative — an unauthenticated POST to any op returns the exact price for that call before you pay.

PDF /v1/pdf/<op>

Office /v1/office/<op>

CSV /v1/csv/<op>

Image /v1/image/<op>

Codes /v1/{qr,barcode,codes/<op>}

Utils /v1/utils/<op>

Generate /v1/generate/<op>

Archive /v1/archive/<op>

Data /v1/data/<op>

Text /v1/text/<op>

Pipeline /v1/pipeline

The pipeline runtime composes a chain of transforms in one call and bills the sum of its steps — each step at its normal per-op rate — plus a $0 orchestration fee. A three-step pipeline on a 5 MB file is Σ (step rate × 5 MiB). An unauthenticated POST returns the exact summed price as a 402 quote, and a failed step refunds the whole run.

Limits

• Inputs: inline base64 up to 4 MB, or up to 50 MB by storage reference (mint a presigned upload via POST /v1/cputools/upload-url).
• OCR is synchronous and capped at 5 pages per call — larger asynchronous OCR jobs are coming. render is capped at 40 pages and 300 DPI. QR/barcode data is capped at 4096 characters. uuid is capped at 1000 per call; mock-data at 1000 rows / 50 fields. Over a cap returns a 422 before any charge.
• archive/unzip is zip-bomb-guarded — and the rejection is a feature: a tiny archive that would expand past 128 MiB, an archive over 10000 entries, or a per-entry compression ratio above 1000:1 is rejected with a 422 before any charge, and the expansion is also halted in-flight if the actual output crosses the cap. Encrypted/password-protected zips are rejected; a nested .zip entry comes back as bytes (one level — never recursively extracted). jwt-verify is algorithm-pinned (no alg:none downgrade) and never logs your key.
• data/sql runs read-only on a sandboxed DuckDB — no filesystem, network, or extension access, so your query sees only your file — and is memory-, time- (≤ 25 s), and output-capped (≤ 128 MiB; a larger result returns 413). data join / union / groupby outputs are byte-capped (the cartesian-blowup guard). pipeline is capped at 10 steps and 128 MiB threaded between steps, and is atomic — a failed step refunds the whole run.

Worked examples

One call, one payment

The lodestone is a single HTTPS call carrying the files and an x402 payment authorization — no account, no signup step.

curl -X POST https://api.relaystation.ai/v1/pdf/merge \
  -H 'X-Payment: <base64 EIP-3009 auth>' \
  -H 'Idempotency-Key: merge-invoices-20260605' \
  -H 'Content-Type: application/json' \
  -d '{"files":[{"inline":"<base64 pdf>"},{"inline":"<base64 pdf>"}]}'

Top up your balance

Pay per call with a per-call x402 payment, or top up with a card via Stripe. One Relaystation balance funds cputools and every other Relaystation product. We absorb the payment-rail fees (Stripe processing, x402 gas) — they never appear in your balance. Sign in to top up via Stripe, or send an x402 payment on any call.