Billing

Job Search API costs 1 credit per verified delivered record. Purchase credits in the workspace and use them for collection.

Before execution

Validate the input, source support and spending ceiling. The quote shows the record limit multiplied by the current unit price; task acceptance reserves that amount before work begins. maxCredits must cover the estimate. Setting a higher ceiling does not increase the reservation. A quote itself reserves nothing, and a reservation is not an additional fee.

At settlement

Charge credits for the delivered quantity at the task’s published price version and release unused reserved credits. For Job Search, the unit is a delivered record. Source failure, exclusions and a completed search with no matches are not billed as delivered records.

Price transparency

Publish each operation’s credit rate and billing unit before it opens. Each operation uses one unit: result, file, media_minute or request; different operations may consume different numbers of credits. Customers purchase credit packs in USD and spend from one credit balance. There is no separate startup, platform or resource fee.

Repeated reads

Reading the same stored result does not start another collection. A new collection is a new request requiring its own authorization and budget.

See pricing for credit packs and the current rate.

A worked example

At Job Search API’s published rate of 1 credit per verified delivered record, 14 records cost 14 credits. With limit: 20 and maxCredits: 100, acceptance reserves 20 credits and settlement releases 6. The example response reports task.billing.chargedUnits: "14000000". The higher credit ceiling is not the reservation, and reservation and settlement are not two separate charges. This example does not guarantee that a query will return 14 records.

Outcomes and account defaults

Partial output is billable only when authorized in advance. An all-or-nothing task does not charge for incomplete delivery. Result-based operations charge nothing for zero records; a request-based operation may bill a successful negative answer if its contract explicitly permits it.

Prepaid credit packs start at $20 and can be purchased in the Console. Purchased credits never expire, and no subscription is required. Eligible new accounts receive 1,000 signup credits. The refund and cancellation policy allows refund requests within 14 calendar days of each purchase for that order’s unused, unreserved paid credits. New orders refund Purchased credits at $0.001 each, to the original payment method, and void the unused bonus from that order. Older orders retain their original terms. Consumed and Earned credits are not refundable under this policy; billing errors are corrected separately and applicable legal rights are preserved. Credits never expiring does not extend the cash refund window. There is no recurring subscription to cancel, and cancelling a task is separate from a cash refund.

Taxes and refunded credits

Pack prices are in USD before applicable taxes. Checkout shows tax and the total before payment. Credits are issued for the pack principal, never for tax.

For taxed orders, cumulative refunded principal is the cumulative refunded payment multiplied by the original pack principal divided by the original total paid. Round this principal to the nearest cent, with half a cent rounded up, then convert at 10 Purchased credits per cent. Each refund changes credits by the difference from the previous cumulative total. This allocation is the credit contract, not a calculation of jurisdiction-specific tax adjustments. Payment and refund records retain their actual monetary amounts; old orders retain their original terms. See the refund policy for an example.

Refund status

Refund tracking distinguishes processing, action required, processed by Stripe, failed and canceled refunds. Processing refunds hold the corresponding credits so they cannot be spent while the refund is pending. Failed or canceled refunds require support review; releasing a credit hold does not resolve the original refund request. A Stripe success status does not confirm when the customer’s bank has posted the funds. Keep the payment and refund references when contacting support.

Request idempotency

Task creation uses Idempotency-Key, scoped to the account and product. Authentication is checked before looking up a replay. Replaying the same accepted request with its key does not create another task or business charge. Reusing a key with different input must not silently create new work.

A new collection requires its own authorization and budget, even if it finds the same records. RapidAPI authentication, balances and platform request accounting are separate. Read the cost guide for the comparison method.

Account usage and limits

Send GET https://api.truefetch.io/v1/account/usage with your API key in the Authorization: Bearer <key> header. This read does not start a task, reserve credits or require remaining monthly spending allowance. Normal request rate limits still apply.

• balance reports postedUnits, task reservedUnits, refundReservedUnits, availableUnits and cumulative task chargedUnits. Available equals posted minus both reservations; a negative balance can reflect a refund or payment adjustment. A read_results key receives balance: null.
• All credit amounts are exact integer strings: 1,000,000 units = 1 credit. They are not dollar cents. asOf identifies the database snapshot.
• limits reports accepted tasks today, queued tasks and active attempts against their account limits. Daily tasks reset at midnight UTC. Cancelling a task does not erase its daily admission count.
• credential.monthly reports the current key’s cap, use and remaining units. Use combines charges for completed tasks with reservations for unfinished tasks accepted in the current UTC month. limitUnits: null means no monthly key cap; it does not remove account limits. Unused reservations are released at settlement. The reset time is explicit.
• spendingRestricted indicates an account spending hold. A balance or quota read is informational, not a promise that a later task will be accepted; source availability and other runtime checks still apply.

Console sessions read account balance and product usage at /api/console/usage; it reports Purchased and Earned separately with exact units. MCP has a truefetch_get_usage tool using the same implementation; hosted MCP remains unavailable until its release gate is enabled.