Expand AI logo
DocsDocs
Glow Active
API Reference
Login

Documentation

Get started

IntroductionWhy ExpandQuickstartAuthenticationConnect your agent (MCP)

Products

OverviewFetching a URLBatched Fetch
API reference

SDKs & tools

TypeScript SDK
MCP tools & resourcesDocs for agents

Reference

API referenceErrors & retriesPricing & UsageLimitsConcurrency tiersFAQ
Browse docs

Get started

IntroductionWhy ExpandQuickstartAuthenticationConnect your agent (MCP)

Products

OverviewFetching a URLBatched Fetch
API reference

SDKs & tools

TypeScript SDK
MCP tools & resourcesDocs for agents

Reference

API referenceErrors & retriesPricing & UsageLimitsConcurrency tiersFAQ

Pricing & Usage

What each operation costs in credits, how credits are bought and spent, what is never charged, and how browser concurrency is priced.

Expand runs on prepaid credits. You buy credits up front, and delivered work draws them down. 1,000 credits cost $1, so one credit is $0.001. One successful Fetch costs 1 credit.

Credits and balance

Start with 10,000 welcome credits and buy more in packs of 1,000.

Credit costs

A Fetch is 1 credit. Highlights, document pages, and transcripts add credits on top.

Browser concurrency

Your tier sets how many browsers you can run at once. Provisioned browsers add more, at $1 per browser per month.

What you are charged for

Failed, blocked, and empty work costs 0 credits. You pay for content you received.

Your balance and the Buy credits button are in your dashboard under Settings, Billing. Request activity over time is in your dashboard under Usage. How tiers are reached is on Concurrency tiers.

Credit costs

Every priced operation is quoted in credits.

OperationCreditsDefinition
Fetch1One delivered page, file, or video. The base unit. Every other row is added on top of it.
Highlights1One Highlights request, inline with a Fetch or on a Snapshot you already have. See Two ways to highlight.
Converted document page
Note
Browser concurrency is not priced in credits. Your tier includes a number of browsers, and provisioned browsers cost $1 per browser per month on your card. See Browser concurrency.

Expand bills per delivered output, not per token. For a committed monthly allowance, bulk rates, or enterprise terms, email support@expand.ai.

Credits and balance

Your organization holds one prepaid credit balance. Delivered work draws it down, and buying credits tops it up.

Your first organization starts with 10,000 welcome credits, worth $10. Welcome credits expire 365 days after they are granted. Purchased credits stay on your balance until you spend them.

Billing shows your balance as two numbers:

  • Available credits. Credits you can spend now.
  • Expiring soon. Credits set to expire within 30 days.

Buy more with Buy credits. Choose a number of credits, any multiple of 1,000 up to 10,000,000, and pay by card in a hosted checkout. The credits land on your balance as soon as the payment is confirmed.

Note
Anonymous use of the landing page and the Playground runs on separate demo credits. It does not touch your balance.

Usage metering

A Fetch costs 1 credit. Highlights on the same request add 1 more. If the URL serves a file rather than a page, the pages it converts are added on top.

Fetch request

Expand checks your balance covers it.

Credit hold

Credits are held up front.

Delivered outputs

Each output you asked for and got is counted.

Credits settled

You pay for what was delivered. The rest of the hold is released.

Each requested output is charged on its own:

What you fetchCredits
A page1
A page with Highlights2
An office file, ebook, CSV, JSON, XML, or text file1. These convert without a page count.
A PDF with a text layer, plus per converted page

Document conversion is charged only on a delivered result. A Fetch refused for exceeding a limit, for an unconvertible format, or because the origin returned no file is charged nothing.

Recommendation
Set documentConfig.maxPages to cap the pages a Fetch may convert, and documentConfig.ocr to "never" to skip the vision model. There is no default page limit. See Limiting what gets converted.

The JSON object reports what each Fetch was charged for in data.usage: documentPages, ocrPages, audioSeconds, and videos. The Usage view in your dashboard shows request activity over time.

What you are charged for, by outcome

You pay for delivered content, not for attempts. Every Fetch holds credits up front and releases the hold when the request settles, so a request that produced nothing costs nothing.

OutcomeChargedWhy
The page was capturedYesContent was delivered.
The origin answered with an HTTP error status (400 and above) and the page was capturedYesError pages are still content, such as a soft 404, a maintenance notice, or a status page. You receive the page plus originError with the status.
The origin could not be reached
Warning
An origin's 404 or 500 page is a real capture, so it costs 1 credit like any other page. Check originError before you treat the content as the page you asked for.

Highlights are charged on the same basis. Delivered snippets cost 1 credit, and a request that never produced a capture costs nothing. Which errors are charged, and which to retry, is on Errors & retries.

Browser concurrency

Browser concurrency is how many browser captures your organization can run at once. It has two parts:

Total browser concurrency = tier concurrency + provisioned browsers

Tier overview

Your tier sets the browsers included with your account, from 2 at Tier 0 to 100 at Tier 5. Tiers rise on their own as you spend credits and time passes. The table, and how tiers are reached, is on Concurrency tiers.

Provisioned browser concurrency

If you need more browsers before your next tier, add provisioned browsers in Billing. Each one costs $1 per month, billed to the card on file. The price is a fixed subscription, not a credit cost, and the browsers are added on top of your tier. You can provision up to 1,000.

ChangeWhen it takes effectWhat you pay
Adding browsersImmediatelyA prorated charge for the rest of the current month right away, then $1 per browser per month
Removing browsersAt the end of the month you paid forNothing more. The browsers you paid for stay until the month ends, and nothing is refunded
Setting the count to zeroAt the end of the month you paid for
Note
If your organization has no card on file, Billing sends you to a hosted checkout first. The browsers appear once the payment is confirmed.

At your limit, a single Fetch is refused with 429 FetchConcurrencyLimitExceeded and Batched Fetch queues instead. See Limits.

Enterprise organizations get their browser concurrency from their contract and do not buy browsers here.

Access when credits run out

Expand checks your balance before it admits a request. With credits on your balance, the request runs. With none, the request is refused before any work starts, so you are never charged for a request Expand declined to run. Buying credits clears the block immediately.

Next steps

  • Concurrency tiers: the tier table, how tiers are reached, and worked examples.
  • Limits: concurrency, time, and size limits in one place.
  • Errors & retries: which errors are charged, and which to retry.
  • FAQ: short answers to billing questions.
PreviousErrors & retries
NextLimits

On This Page

Credit costsCredits and balanceUsage meteringWhat you are charged for, by outcomeBrowser concurrencyTier overviewProvisioned browser concurrencyAccess when credits run outNext steps
1 per page
Every page a PDF or other file converts. An image counts as one page.
Vision-model page5 per pageA page read by a vision model instead of a text layer, such as a scanned PDF or any image. On top of the converted page.
Video5 per videoA YouTube video that delivered a transcript, whatever its length.
Transcribed audio10 per minuteAudio files, and videos with no caption track. Rounded up, one-minute minimum.
Crawl page render1 per pageA page Crawl renders in a browser. A freshness check that does not render is free.
Failed, blocked, or empty work0Nothing was delivered, so nothing is charged.
1
1
A scanned PDF, or any image1, plus 1 per page, plus 5 per vision-model page
An audio file1, plus 10 per transcribed minute
A YouTube video with captions6, the Fetch plus the video
A YouTube video with no captions6, plus 10 per transcribed minute
No
No page was delivered. The response is 200 with a FetchOriginError in place of content.
The origin refused the file, or it was missing or removedNoNo file was delivered. The error is FetchOriginHttpError at 404 or 410 for a missing or removed file, and 502 otherwise.
The page blocked the capture (403 FetchBlocked)NoExpand did not deliver the page.
The page exceeded a size limit (413 FetchPageTooLarge)NoExpand did not deliver the page.
Expand failed (500, 503)NoOur problem, not your charge.
A crawl freshness check that did not renderNoAn internal check, never a delivered page.
Nothing more