Pricing / Plans & credits

RunHarvester pricing and credits

Compare the live plan catalog, credit allowances, and account limits. Use response billing metadata to track actual credit usage.

Plans from the live billing catalog

Plans for every workload.

Compare request limits, concurrency, and support options before choosing a plan.

Live plan prices loaded.

Individual developers and small teams

Developer

For production integrations

Practical limits for growing applications.

  • Monthly credits: 300,000 credits
  • Trial credits: 10,000 credits
  • Structured output included
  • Support: developer
  • API keys: 10
  • Batch size: 250

High-volume teams and platforms

Scale

Best Value

High-throughput scraping with larger batches.

  • Monthly credits: 4,200,000 credits
  • Trial credits: 0 credits
  • Structured output included
  • Support: scale
  • API keys: 100
  • Batch size: 5,000

Very high-volume scraping operations

Advanced

For advanced workloads

Maximum self-serve throughput and capacity.

  • Monthly credits: 12,000,000 credits
  • Trial credits: 0 credits
  • Structured output included
  • Support: advanced
  • API keys: 250
  • Batch size: 10,000

For mission-critical workloads.

Enterprise

A plan designed around your infrastructure.

Custom

Contact
  • Custom request limits
  • Custom concurrency settings
  • Private proxy network
  • Custom integrations by agreement
  • Dedicated account support
Current allowancesSee your selected plan
Billing controlsReview your subscription
Scoped API keysKeep credentials server-side
Request visibilityTrack jobs and retries

All plans include access to the Data API and client cabinet. Prices in USD. Taxes may apply.

Keep costs clear

Understand your bill

Billing contract and current charge rules
What determines the cost of a request?

Request cost depends on the active route and caching behavior. Auto serves as a routing policy, not a fixed price. Rely on response billing metadata and the current pricing version as the definitive source; plan prices and allowances are sourced from the live catalog.

Read the documentation
Is structured extraction billed separately?

The documented pricing model includes structured extraction in request pricing. The selected route can affect the total request cost. Check the returned billing metadata and current billing documentation before estimating a workload.

Read the documentation
What happens to credits after a failure or cancellation?

Requests that fail validation incur no fees. If a request fails completely, base debits are refunded; the final credit adjustment depends on the applicable billing rules. Cancellations in pending or running states may resolve at varying times. Cross-reference billing metadata and the returned token state to match up charges.

Read the documentation