GeoScreenshot API

Name: GeoScreenshot API
Brand: GeoScreenshot API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage ProcessingapiKey3 EndpointsREST

For Agents

Capture website screenshots from specific geographic locations and confirm what real users see in different countries. List available capture regions and check account credit before issuing requests.

Connect the GeoScreenshot API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GeoScreenshot API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with GeoScreenshot API.

Capture a website screenshot from a specified country or city to verify geo-targeted rendering

List the available global capture locations before issuing a screenshot request

Check remaining account credit and plan details before running a batch capture

Generate evidence of localised ad creative for compliance and ad verification reports

GET STARTED

Start building with GeoScreenshot API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for GeoScreenshot API, keeping it validated and agent-ready. GeoScreenshot captures full-page screenshots of websites from real geographic locations around the world, letting teams verify how a page renders for users in specific countries or regions. The API exposes a single screenshot capture endpoint plus helpers to list available locations and inspect account quota. It is most often used for ad verification, geo-targeted QA, SEO localisation checks, and compliance evidence.

Use Cases

Patterns agents use GeoScreenshot API for, with concrete tasks.

★ Geo-Targeted Ad Verification

Advertising teams need to confirm that geo-targeted creative is actually being served to users in the intended region. GeoScreenshot captures the rendered page from a real exit node in the target country, producing an image that can be filed as proof of delivery. A typical verification run takes seconds per location and runs unattended.

Capture a screenshot of https://example.com/promo from location code 'us-ny' and store the resulting image URL alongside the location label.

Localised SEO QA

SEO teams running international campaigns need to see what Google or a target site renders for users in specific markets, since localisation, currency, and language vary by region. GeoScreenshot captures the page exactly as a regional user would see it, so teams can audit hreflang behaviour, currency display, and content swaps without travelling or using VPNs.

Capture screenshots of https://shop.example.com/product/123 from locations 'fr-paris' and 'de-frankfurt' and report which currency is displayed in each.

Compliance Evidence Capture

Regulated industries need timestamped visual evidence that disclosures, pricing, or warnings appeared correctly in specific jurisdictions. GeoScreenshot returns a screenshot from a real network exit point in the chosen region, giving compliance teams an artefact suitable for audit logs without operating their own proxy infrastructure.

Capture a screenshot of https://broker.example.com/disclosures from location 'uk-london' and save the image URL with a UTC timestamp.

Agent-Driven Visual Monitoring

An AI agent can monitor a list of URLs across multiple geographies on a schedule, capture screenshots through Jentic, and flag visual regressions or missing localisation. The agent uses Jentic to discover the screenshot operation, supplies the URL and location code, and receives the image link without managing GeoScreenshot credentials directly.

For each URL in a watchlist, request a screenshot from three locations via the Jentic-managed GeoScreenshot operation and report any URL whose response was not a successful image.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for geoscreenshot api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/screenshot

Capture a screenshot of a URL from a specific location

GET

/location

List available screenshot locations

GET

/me/

Get account information and remaining credit

GET

/screenshot

Capture a screenshot of a URL from a specific location

GET

/location

List available screenshot locations

GET

/me/

Get account information and remaining credit

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The GeoScreenshot API key is stored encrypted in the Jentic vault. Agents call the screenshot operation via Jentic and the platform injects the `apikey` query parameter — the raw key never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'capture a screenshot of a website from a specific country'), and Jentic returns the GeoScreenshot screenshot operation with its input schema so the agent can call it directly.

Time to first call

Direct GeoScreenshot integration: a few hours to wire up auth, retry handling, and location lookup. Through Jentic: under 15 minutes — search, load, execute.

FAQs

Specific to using GeoScreenshot API through Jentic.

Why is there no official OpenAPI spec for GeoScreenshot API?

GeoScreenshot does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call GeoScreenshot API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the GeoScreenshot API use?

The GeoScreenshot API uses an API key passed as the `apikey` query parameter on every request. Through Jentic, the key is stored in the encrypted vault and never enters the agent's prompt — the agent only receives a scoped execution token at call time.

Can I capture a screenshot from a specific country with the GeoScreenshot API?

Yes. Call `GET /screenshot` with the URL and a location code; supported locations are returned by `GET /location`, so an agent can list locations first and then pick one before capturing.

How do I check my remaining screenshot credits?

Call `GET /me/` to retrieve account information including remaining credit balance. Agents typically check this before running a batch to avoid mid-run failures.

How do I capture a geo-targeted screenshot through Jentic?

Search Jentic for `capture a website screenshot from a specific location`, load the schema for the GeoScreenshot screenshot operation, and execute with the URL and location code. The result is an image link the agent can store or pass downstream.

Does the GeoScreenshot API capture videos or full-site crawls?

No. The API captures still screenshots only. For video recording or multi-page crawling, combine GeoScreenshot screenshots with a separate crawler or video capture service.