CAPTCHA API Pricing: Reservations, Refunds and Safe Retries

Read live prices in integer USD micros, understand reserved funds and completed-task charges, and avoid duplicate requests.

For authorized QA automation and browser integration. Use only on websites and workflows you have permission to test.

Charge and reservation are different

A task reserves funds at creation using its frozen priceMicros. A successful completion settles the charge. A definitive failure or cancellation releases the reservation. An uncertain task can keep funds reserved until its outcome is reconciled; a local timeout is not a refund.

Read live prices before scheduling work

GET /v1/prices is public. Check available separately from price. Disabled entries may omit priceMicros; a missing price is not zero. Contract customers can query GET /v1/me/prices using their own Key. The create response is authoritative for the task's frozen price.

Amounts are integer USD micros: 1 USD is 1,000,000 micros. A display price per thousand is a convenience, not the unit to use in accounting. Use integer arithmetic and persist taskId with the frozen price.

Prevent duplicate spending

Retrying the same logical request with a new idempotency key can create an additional task. Save the key before sending, reuse the exact body on retry and poll the existing task once its ID is known. Keep your own task record beyond the approximately 25-hour idempotency window.

Funding and proxy costs

Check the recharge method currently offered in your console. When self-service USDT recharge is enabled, its order flow specifies a minimum of 0.50 USD; use the current network, address and exact order amount, including any network fees. Recharge Keys and contractual arrangements can have different terms. Do not transfer funds to an old address without a current order.

If a type requires your own proxy, its provider bills that separately under your proxy agreement. SolveHub's price endpoint reports the task price and does not quote your external proxy bill.

Estimate a budget

Start with planned completed tasks × current effective priceMicros, then allow room for active reservations and price changes before new tasks. Historical success rates or processing times are not promised here. Check live prices and retry behavior, and use Key spending limits as documented in the API reference.