Skip to main content
FetchFox uses cost plus pricing, which means we charge a fixed fee on top of our underlying costs. The underlying costs for each scrape are network traffic through proxies, and the cost of AI usage. We pass on these costs directly, and add a FetchFox fee based on API usage. Your Price=Network Traffic+AI UsageAI Surcharge+FetchFox FeesYour\ Price = Network\ Traffic + AI\ Usage * AI\ Surcharge + FetchFox\ Fees In metrics:
  • cost.network = proxy bandwidth cost
  • cost.ai = model token cost
  • cost.fetchfox = operation fees + AI surcharge
Credits are USD-denominated (1000 credits = $1.00).

Viewing cost metrics

Every call you make to FetchFox has a metrics field. This field includes a cost breakdown, showing how much of the cost for that call was for network traffic, AI usage, and FetchFox fees. Below is an example cost breakdown.

Summary

In this example, you can see a summary of costs for network, AI, and FetchFox usage. You can also see a detailed breakdown showing which proxies were used for how much data, which AI models were used for how many tokens, and which FetchFox calls were used.

FetchFox fees

FetchFox operation fees are: FetchFox also applies a surcharge equal to 20% of AI usage cost. A scrape call does not have its own charge, but it will incur costs from all the underlying operations.

Underlying cost

There are two sources of underlying cost for each call to FetchFox: network traffic and AI usage.

Network costs

Network traffic is billed per byte and depends on proxy tier. Costs vary significantly by tier. Read more about proxies:

AI costs

AI usage is billed by token usage. Larger context means higher AI cost. Two practical ways to control AI cost:
  1. Use a lower-cost model.
  2. Let repeated extractions get boosted over time.
Read more about boosted extraction behavior: