Question 1

Is there a free tier?

Accepted Answer

Yes. The free tier includes 1,000 API credits per month, enough for 1,000 standard scrapes, plus 10K one-time Logo Link requests, with no credit card required.

Question 2

How do API credits work?

Accepted Answer

Scrape starts at 1 credit, or 2 with browser actions. Structured JSON extraction against your schema adds 4 when it succeeds, so 5 credits per page. Highlights and Product add 1, and PDF OCR adds 1 per recovered page. Brand and Styleguide cost 10 credits. Answers costs 10 in Fast mode or 100 in Ultra. Web and news search cost 1 credit per 10 results; web search adds 1 per 10 results for highlights and 1 per page returned as Markdown. People Search costs 10 per call and People Enrich 20 per match. Logo Link has a separate quota.

Question 3

Are there extra fees for JS rendering, anti-bot bypass, or premium proxies?

Accepted Answer

JS rendering, anti-bot bypass, and proxies are included in the base scrape price. Browser actions raise the base to 2 credits. Successful JSON extraction adds 4 credits. Highlights and Product add 1, and PDF OCR adds 1 per recovered page.

Question 4

Can I crawl an entire website?

Accepted Answer

Yes. Crawl discovers and scrapes up to 500 pages into Markdown in one call, with controls for depth, page count, URL patterns, and subdomains. For larger sites, run Batches in crawl mode and collect results through pagination or a completion webhook. Use Map when you only need the URLs.

Question 5

Am I billed for failed requests?

Accepted Answer

Most failed requests are not billed. Not-found responses (404) are billed at the request’s base price. Scrape can return a 200 with failed outputs: it charges when at least one output succeeds or the target page is missing. Check key_metadata.credits_consumed for the amount charged.

Question 6

What pricing plans are available, and can I make one-time lookups instead of subscribing?

Accepted Answer

Context.dev offers Developer ($20/mo), Pro ($90/mo), Growth ($300/mo), Scale ($500/mo), and Scale 2.5M ($950/mo), plus Enterprise for teams that need more than 2.5M credits a month, volume discounts, or security and procurement support. We currently do not support one-time lookups, however you can contact us to discuss options for one-time projects at hello@context.dev.

Question 7

Which plan should I choose?

Accepted Answer

Start with Free for testing or Developer for your first workflow. Pro suits steady production usage; Growth adds capacity between Pro and Scale. Scale supports high-volume traffic and self-serve SSO / SAML. Choose Enterprise for custom volume, limits, procurement, or support. Upgrades apply immediately; downgrades apply at renewal.

Question 8

Do you offer annual billing?

Accepted Answer

Yes. Annual billing saves two months compared with monthly billing on every paid plan.

Question 9

Do you offer discounts for startups or nonprofits?

Accepted Answer

Eligible startups and nonprofits can apply for 30% off an annual paid plan for 12 months, plus private Slack Connect with our team. Existing customer deals stay unchanged. Apply at https://www.context.dev/startups.

Question 10

What happens when my API credits run out?

Accepted Answer

The Free plan includes 1,000 API credits that renew every month. Paid plans can use Auto-Topup in 1K-credit blocks: Developer $3.00, Pro $2.00, Growth $1.50, Scale $1.00, and Scale 2.5M $0.75 for new subscriptions. Existing subscriptions keep their rates. With insufficient credits and no available top-up, any plan returns 401 USAGE_EXCEEDED. Logo Link has a separate quota.

Question 11

What are the rate limits, and how can I increase them?

Accepted Answer

Core API limits cap concurrent requests per organization: Free allows 2; Developer 10, Pro 100, Growth 250, and Scale 500. Plans have no per-minute cap by default. Existing accounts keep their current allowances until they change plans; custom overrides can apply to either limit or both. The dashboard shows your effective limits. Batches, Monitors, webhook deliveries, logs, and feedback have separate organization limits. Enterprise can have custom limits; Logo Link has a separate quota.

Question 12

Why am I getting timeout errors?

Accepted Answer

Scrape waits up to 90 seconds by default. For slow or heavily protected pages, raise timeoutOpts.milliseconds (up to 300,000), set timeoutOpts.behavior to return-partial to keep the outputs that finished, and give your HTTP client a longer timeout than the request. Use Batches for large URL lists, and Prefetch to warm uncached domains before a Brand request.

Question 13

What SDKs are available?

Accepted Answer

We provide official SDKs for TypeScript, Python, Ruby, Go, and PHP.

Question 14

How can my agent sign up?

Accepted Answer

AI agents can register and obtain API credentials programmatically using our agent authentication guide (auth.md). You will still need to sign in or verify your email. Share the link with your agent:

Question 15

When should I talk to sales?

Accepted Answer

Talk to sales if you need high-volume pricing beyond 2.5M credits/month, custom rate limits, annual invoicing, or help with a security or procurement review. Review our published compliance status, policies, controls, and subprocessors at https://trust.context.dev/. Reach us at hello@context.dev or through the contact page.

Question 16

What's the difference between API credits and Logo Link?

Accepted Answer

They are separate products with separate quotas. API credits meter the documented API endpoints. Logo Link returns a square logo through a direct image URL and does not consume API credits. Core API requests use the plan concurrency limit; Logo Link image delivery follows its separately documented quota and delivery policy.

Question 17

How fresh is the brand data? How often is it updated?

Accepted Answer

Brand Retrieve may reuse cached data up to its documented maxAgeMs, which defaults to about 90 days and is clamped to 0 through one year. A value of 0 requests a fresh Brand retrieval. For a specific correction or rebrand, use https://www.context.dev/update and treat returned media URLs as external resources that your application should handle defensively.

Question 18

Do you support subdomains?

Accepted Answer

Yes, subdomains are fully supported.

Question 19

What if I need additional data points?

Accepted Answer

We are constantly adding new data points to the API and have more data under the hood that we don't surface yet. If you need a specific data point, please contact us at hello@context.dev and we will be happy to surface it.