BrowserCat Pricing in India for Website Screenshot APIs

BrowserCat does not publish a verified India-specific price in the official pricing material reviewed. Its published prices are in US dollars: the Hobby plan is free with 1,000 credits per month, and Business costs $50 per month with a selectable included-credit allowance. Extra credits cost $0.0025 on Hobby and $0.00175 on Business. Those are USD figures; the reviewed sources do not establish an INR total, India tax treatment, or local payment terms. BrowserCat’s pricing page is the source for current plan amounts, which may change.

BrowserCat pricing in India at a glance

Plan or purchase	Published price	Credits and metering
Hobby	$0/month	1,000 credits/month; $0.0025 per extra credit
Business	$50/month	Included monthly credits are selectable; $0.00175 per extra credit
Credit pack	$20	10,000 credits
Credit pack	$87.50	50,000 credits
Credit pack	$300	200,000 credits

The pricing page says credit packs can be purchased with USDC on Base through Stripe. It does not confirm that an India-based account will see the same checkout options or an INR charge. Check checkout and the applicable payment terms before budgeting a local total.

How many credits does a screenshot use?

There is no separate screenshot-only rate listed. The cost depends on the BrowserCat API path used:

• Utility API: one credit for each successful request. The vendor FAQ says, “For every 1 successful API request, you’re billed exactly 1 credit.”
• Websocket API: one credit for each 30 seconds of active session, rounded up. A 31-second session therefore consumes two credits. BrowserCat summarizes this as, “Every 30 seconds of activity is worth 1 credit.”

A screenshot made through a successful Utility API request uses one credit under that model. With a Websocket workflow, include browser startup, navigation, waits, and capture time in the active session estimate; the published rule meters session activity, not just the final screenshot action. Confirm the exact API behavior and any current exceptions in BrowserCat’s documentation.

How much does BrowserCat cost in India?

The official figures reviewed are USD-denominated. They do not provide a rupee price, conversion rate, India GST or other tax treatment, foreign-exchange fee, or confirmation of India-specific payment eligibility. A precise India-local total cannot be derived from those facts alone.

For a rough pre-tax estimate, calculate expected credits first, then apply the published plan and overage amounts in USD. Your payment provider’s exchange rate and fees, any applicable taxes, and checkout eligibility determine what you ultimately pay. Verify those items in your account or with BrowserCat before committing to a budget; do not treat a currency conversion as BrowserCat’s official India price.

Estimate your monthly BrowserCat spend

1. Choose the API path. Count successful Utility API requests, or estimate Websocket session duration.
2. For Websocket activity, round each session duration up to the next 30-second block, then total the credits.
3. Compare the total with Hobby’s 1,000 monthly credits or the selected Business allowance.
4. Apply the appropriate overage rate to credits beyond the allowance: $0.0025 for Hobby or $0.00175 for Business.
5. Separately verify payment currency, tax, exchange fees, and whether credit packs are available to your account.

For example, 1,200 successful Utility API requests in a month are 1,200 credits under the one-credit-per-successful-request rule. On Hobby, that is 200 credits above the included 1,000, or $0.50 in overage at the published rate, subject to the vendor’s billing rules and any applicable charges outside that calculation. This example is arithmetic from the listed rate, not a quote for an India checkout.

For Websocket usage, calculate per session because each session rounds up independently. Ten sessions lasting 31 seconds each use 20 credits, not the 11 credits you would get by summing their durations first and rounding once.

Overages, billing, and spending limits

BrowserCat says the base plan fee is charged at the beginning of the month. Remaining overages are billed at month end, although it may charge earlier if overage fees exceed the plan’s base fee. Its published default soft limit is the monthly subscription amount, with a hard limit at twice that amount. For free plans, the defaults are $10 and $20. BrowserCat says it requests approval to raise a limit after the soft limit and rejects requests at the hard limit without approval.

These limits affect reliability as well as cost: if usage reaches a hard limit, requests may be rejected until the limit is raised. Review current account settings and the vendor’s billing documentation, especially before a batch run or sustained production workload.

What matters for India-based teams

• Currency and taxes: USD is the published currency in the sources reviewed. INR billing and India tax handling are unconfirmed.
• Payment method: the credit-pack page mentions USDC on Base through Stripe. It does not establish India-specific checkout eligibility or card billing terms.
• Session region: BrowserCat’s configuration documentation says sessions currently run near the request and explicit region routing is on its roadmap. This does not show that sessions run in India and is not a latency guarantee.
• Usage model: request-based Utility API consumption is easier to forecast when each successful request is a discrete unit. Websocket costs also depend on how long each active session lasts and its 30-second rounding.

For geographic or latency-sensitive work, measure from the actual deployment environment and confirm the supported region behavior with BrowserCat. Do not infer India hosting from the “near the request” description.

Choosing a plan

Workload pattern	What to examine
Small or exploratory use	Whether the Hobby plan’s 1,000 credits cover expected monthly successful requests or session time.
Steady recurring volume	Business included-credit selection versus likely usage, plus its lower published overage rate.
Uneven monthly demand	Expected peak months, overage exposure, and hard-limit behavior; do not plan only around an average month.
One-off large workload	Whether a credit pack fits the workload and is available through the account’s checkout options.

BrowserCat’s own general guidance is to choose a plan just above average costs for consistent usage, and just below average usage when demand varies substantially. Estimate with your real request count or session durations, then check the live terms and limits.

BrowserCat screenshot API: a minimal workflow

BrowserCat documents opening a page with Playwright and capturing a screenshot, with a cloud browser endpoint used in place of a local browser launch. It also describes compatibility with Playwright, Puppeteer, and CDP clients. The following sketch shows the local Playwright capture step; use BrowserCat’s current quick start for its endpoint, authentication, and connection details, which are not reproduced here to avoid guessing configuration values.

import { chromium } from 'playwright';

const browser = await chromium.launch();
try {
  const page = await browser.newPage({ viewport: { width: 1440, height: 900 } });
  await page.goto('https://example.com', { waitUntil: 'networkidle' });
  await page.screenshot({ path: 'shot.png', fullPage: true });
} finally {
  await browser.close();
}

This local example demonstrates the browser steps only; a local browser launch does not itself use BrowserCat credits. To run through BrowserCat’s hosted browser, follow the official quick start and configuration documentation and connect the supported client to the documented cloud endpoint. Metering then depends on the chosen Utility API or Websocket path.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. Its one-call API returns an image or PDF, and its options include full-page capture, element capture, device and viewport settings, waits, and custom CSS or JavaScript. See the ScreenshotNeo API docs for parameters.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));

• Cookie banners and more than 60 known consent platforms, newsletter popups, and chat widgets are removed before capture; each step can be turned off.
• Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Responses include X-Page-Verdict and X-Billed headers.
• An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents.
• 1,000 screenshots per month are free with no card; paid plans start at $5 for 3,000. All features are on every plan.

Create a free ScreenshotNeo account for 1,000 screenshots a month with no card.

Troubleshooting BrowserCat cost estimates

My screenshot cost is higher than one credit

Check whether the integration uses Websocket sessions rather than the Utility API. Websocket usage is metered in 30-second increments, rounded up, so session duration drives credit use.

My estimate does not match the invoice

Check successful request counts, session rounding, the plan’s included allowance, overages, and whether an early overage charge occurred. Compare the invoice period and account usage records with the current pricing terms.

Requests stopped during a run

A hard spending limit can reject requests absent approval to raise it. Review the account’s soft and hard limits before a workload and monitor remaining usage during execution.

I cannot find an INR amount

The reviewed official pricing material lists USD amounts and does not verify India-specific billing or tax treatment. Use checkout or ask BrowserCat for the account-specific payment and tax details rather than assuming a rupee conversion is the final price.

Latency from India is unclear

The configuration documentation describes sessions running near the request and says explicit region routing is on the roadmap. It does not promise India hosting. Measure from your own environment and confirm current region behavior.

Performance, reliability, and cost planning

• Keep session time bounded: for Websocket work, avoid unnecessary idle time and waits; every additional 30-second block can add a credit.
• Use the correct unit in forecasts: count successful Utility API requests or round each Websocket session upward separately.
• Protect long jobs from spend limits: estimate the entire run, check account limits, and handle rejected requests so a hard limit does not silently leave a partial screenshot set.
• Budget in the published currency: keep the vendor’s USD amount separate from your estimate of conversion, taxes, or payment fees until checkout confirms them.
• Validate regional assumptions: a cloud browser workflow can have different network paths from a local browser; test from the deployment location when response time matters.

The sources do not provide an India-specific latency guarantee or a screenshot benchmark. Treat performance as workload- and route-dependent, and use a representative sample before setting production expectations.

FAQ

Does BrowserCat charge in INR?

The official material reviewed does not confirm INR pricing or billing. Published plan and pack amounts are in USD.

Is BrowserCat Hobby free?

The published Hobby plan is $0 per month and includes 1,000 credits monthly; successful usage beyond that is listed at $0.0025 per credit.

Does every screenshot cost one credit?

Only a successful Utility API request is explicitly priced at one credit. Websocket API use is metered by active session time in 30-second blocks.

Are BrowserCat sessions hosted in India?

The configuration source reviewed does not say that. It describes sessions running near the request and explicit region routing as planned.

Can I calculate a final India price from the listed USD rate?

No. The reviewed sources do not establish the exchange rate, taxes, fees, or checkout terms for an India-based account.

Sources

• BrowserCat pricing — plans, credit packs, rates, and billing details.
• BrowserCat documentation — API workflow, quick start, configuration, and region notes.