Can Microlink Screenshot an Indian Government Website with CAPTCHA?

Short answer: Microlink can take a screenshot of an Indian government website, but it does not guarantee that the page content behind a CAPTCHA will be accessible. Its headless browser may capture the requested page, a CAPTCHA or bot challenge, or an error. Microlink documents antibot detection and proxy routing on Pro; its documentation does not claim that it solves CAPTCHA challenges. No specific Indian government portal or test result was provided, so the outcome for a particular site is unknown.

What Microlink does when you request a screenshot

A screenshot request gives Microlink a URL and screenshot options. Its managed headless browser renders the page, captures the current viewport (or the full page when requested), stores the image on a CDN, and returns asset metadata. That describes the capture process; it does not mean the browser has passed a site’s access challenge. Microlink’s screenshot guide documents the request and screenshot options.

If the browser receives a CAPTCHA or challenge page, the screenshot can show that page. This follows from the documented capture flow and Microlink’s distinction between detecting antibot protection and solving it; it is not a reported test of a particular portal.

What the CAPTCHA and proxy documentation means

Microlink’s API page says requests on the free endpoint that encounter detected antibot protection return EPROXYNEEDED. It describes automatic proxy routing for blocked requests on Pro. Its antibot documentation says detection can identify CAPTCHA and bot-protection providers, while explicitly distinguishing detection from solving: the detector identifies who blocked a request; it does not solve the challenge. The API’s proxy details are on Microlink’s API page.

Proxy routing changes the route used to reach a site. The documentation does not promise that a CAPTCHA will be completed, that every Indian government site will allow access, or that a particular page will be returned. Only access pages you are permitted to access, and follow the target site’s rules.

How to try a screenshot and inspect the result

Use the exact public URL you are permitted to access. Avoid adding credentials or personal data to a request URL.
Send a screenshot request. Microlink’s guide documents screenshot as a boolean or an options object; the example below uses the boolean form.
Inspect the returned asset in a browser or image viewer. Confirm that it contains the intended page rather than a CAPTCHA, challenge, login screen, or error.
If the response reports EPROXYNEEDED, consult Microlink’s current plan and proxy documentation. A proxy retry is not a CAPTCHA-solving guarantee.
For repeatable monitoring, record the request outcome and inspect the image or returned metadata. Do not treat a successful image response alone as proof that the intended page loaded.

curl --get 'https://api.microlink.io' \
  --data-urlencode 'url=https://example.gov.in/' \
  --data-urlencode 'screenshot=true'

Replace https://example.gov.in/ with the permitted target. The API returns response data describing the screenshot asset; use the response format in Microlink’s current documentation rather than assuming a fixed image URL or a successful page load.

Python example

import requests

response = requests.get(
    "https://api.microlink.io",
    params={
        "url": "https://example.gov.in/",
        "screenshot": "true",
    },
    timeout=90,
)
response.raise_for_status()
print(response.json())

This prints the API response so you can inspect its status and screenshot asset metadata. Replace the example URL and handle API errors according to the response you receive.

Node.js example

const params = new URLSearchParams({
  url: 'https://example.gov.in/',
  screenshot: 'true',
});

const response = await fetch(`https://api.microlink.io?${params}`);
if (!response.ok) {
  throw new Error(`Microlink request failed: ${response.status}`);
}

const result = await response.json();
console.log(result);

These examples demonstrate the screenshot request. They do not bypass or solve a CAPTCHA. Microlink’s screenshot guide also describes an options object for settings such as full-page capture and image type; check its current guide for the exact supported values.

How to tell what happened

Observed result	What it means	Next step
The intended page is visible	The browser received and rendered the content visible in the screenshot.	Check that the relevant content is present and that the page was not partially loaded.
A CAPTCHA or challenge is visible	The browser captured the challenge response it received; capture did not complete the challenge.	Use an authorized access method supported by the site. Do not assume retries or a proxy will solve it.
`EPROXYNEEDED` appears	Microlink says its free endpoint returns this for detected antibot protection.	Review Microlink’s Pro proxy behavior and terms, then check whether the returned result actually contains the needed content.
An error, blank page, or incomplete render appears	The target may have blocked access, failed to load, or returned content the browser could not render as expected.	Check the URL and response, retry later if appropriate, and verify the page manually through an authorized route.

Options, timing, and practical limits

Microlink’s screenshot guide documents viewport capture, full-page capture, and image type through the screenshot option. The screenshot captures the browser’s rendered state, so timing and the content actually served to that browser matter. A target can return different pages based on access controls, session state, location, or automated-traffic detection. The reviewed documentation does not establish how any specific government portal will behave.

The screenshot guide states an allowance of 25 free requests per day; this is a vendor-stated limit that can change, so verify the current API page before planning usage. The reviewed sources provide no success rate for Indian government CAPTCHA pages and no performance benchmark for this use case. Plan around the response and inspect the actual image rather than estimating success from request completion.

Troubleshooting

Problem	Likely cause	What to do
`EPROXYNEEDED`	Microlink detected antibot protection on the free endpoint.	Review the documented Pro proxy option. Proxy routing may change access, but does not promise CAPTCHA completion.
The image shows a CAPTCHA instead of the page	The target served a challenge to the headless browser.	Treat the screenshot as a capture of the challenge. Use an access path the site permits; do not present this as a successful content capture.
The response contains an error	The URL may be invalid, the site may be unavailable, or access may be blocked.	Check the URL and response details, then retry only when appropriate. Confirm the page is accessible through a permitted method.
The screenshot is blank or incomplete	The rendered page may not have loaded its useful content before capture, or the site may have returned an empty/error state.	Inspect what the browser received and compare with the page reached through an authorized browser session. The reviewed sources do not promise a CAPTCHA-specific wait or completion option.
A retry gives a different result	Site responses and protection behavior can vary between requests.	Record the response and inspect each image. Do not infer a stable pass rate from a small number of attempts.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Its clean-shot flow accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses say which outcome occurred. That does not mean it solves a CAPTCHA or guarantees access to a protected government page: use it only for content the target serves to the capture request.

It also provides an MCP server with take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Every feature is on every plan.

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

See the ScreenshotNeo API documentation for options and response details. Sign up for 1,000 free screenshots a month with no card.

FAQ

Will Microlink capture the CAPTCHA page?

It may. If the browser receives a CAPTCHA page, the screenshot can show that rendered page. The sources do not report a test against a named government site.

Can Microlink get past the CAPTCHA?

Its documentation describes antibot detection and Pro proxy routing, not CAPTCHA solving. Neither feature is a universal guarantee that a challenge will be completed.

Does a Pro proxy guarantee access to an Indian government portal?

No such guarantee appears in the reviewed documentation. The result depends on the site and its protection; inspect the returned screenshot and response.

How many free Microlink requests are available?

The screenshot guide states 25 free requests per day. Check Microlink’s current documentation because plan limits can change.