Skip to content
EN
Get API key
Browse documentation

Get started

Credits and pricing

See what a request costs, how far your balance goes and how to add credits.

On this page

How usage is charged

WorkBilling basis
Google Search / YouTube DataPer request. Each page or batch item is a request; search hits are not.
YouTube DownloadPer byte delivered to your storage.
Balance, pricing, limits and usage readsNo query credits. Read limits still apply.

Check balance and pricing

Use Billing in the console, or run these free checks. This example prices five Google Search requests without submitting them.

Use your saved CLI access. For a named profile, append --profile NAME to each command. These reads do not spend query credits.

Free account reads
flashdata account balance
flashdata account pricing --source google_search --request-count 5

Read the estimate

Use availableCredits from balance. In pricing, require available: true and read estimatedCredits. CLI JSON wraps each account response in data. The following price is illustrative; use the value returned for your account.

Pricing response · relevant fields
{
  "requestCount": 5,
  "prices": [
    {
      "source": "google_search",
      "available": true,
      "creditsPerRequest": 0.02,
      "estimatedCredits": 0.1
    }
  ]
}

How many requests is 1 credit?

At 0.02 credits per search, 1 credit covers up to 50 Google searches. At 0.01 per metadata request, it covers up to 100 YouTube Metadata requests. These are alternative uses of one balance; use your returned prices when estimating.

Example workloadCostRemaining
50 Google searches50 × 0.02 = 1 credit0 credits
100 YouTube Metadata requests100 × 0.01 = 1 credit0 credits
20 Google searches + 30 metadata requests0.4 + 0.3 = 0.7 credits0.3 credits
Calculate with the returned price
task cost = request count × creditsPerRequest
affordable requests = floor(availableCredits ÷ creditsPerRequest)

YouTube Download uses bytes

With youtube_download permission, read creditsPerTb and bytesPerUnit. Cost = delivered bytes ÷ bytesPerUnit × creditsPerTb. estimatedCredits is null because a request count cannot predict delivered bytes.

Read the download rate · free
flashdata account pricing --source youtube_download

Credits after claiming

Check the owner balance after credential handoff. Approval lets the agent spend that shared balance; it does not buy credits, authorize checkout or create a separate per-agent spending cap.

StageWhich balance pays?
Temporary trialIts own time-limited trial balance, for eligible sources.
Claimed by an existing accountFuture requests use the owner's shared balance. Unused trial credits do not transfer.
Claimed after new signupNormal signup eligibility applies. Claiming does not add another signup credit grant.

Add credits

  1. In Billing, review the plan or top-up, total and renewal terms before completing checkout.
  2. After payment, check payment status and balance in Billing. A checkout redirect alone is not confirmation.
  3. Compare saved task usage with the same account date range and sources. Other keys may spend from this balance too.

If the numbers do not match

A balance or price read does not reserve credits. Check the actual query usage, other account activity and in-flight work. Usage summaries can lag behind recent queries or refunds; compare the same time range and source permissions. On 402, pause work and review the balance instead of creating another trial.