canonical: https://jentic.com/apis/geoscreenshot.com/geoscreenshot # GeoScreenshot API 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. ## For AI 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. ## Scope Does not handle video recording, full-site crawling, or DOM scraping - use for still screenshot capture from geographic locations only. ## Capabilities - 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 - Compare how the same URL renders across multiple geographic locations in a single workflow ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Screenshot** — Capture a screenshot of a URL from a chosen geographic location. - **Locations** — List the available capture regions worldwide. - **Account** — Retrieve account information and remaining credits. ## Why Jentic - **Setup:** Wiring the GeoScreenshot API by hand means registering your apikey, appending it as a query parameter on every request, and passing the location and target-URL parameters yourself. Through Jentic you install once, import GeoScreenshot from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** GeoScreenshot's operations like /screenshot and /location take their input in the query string rather than the URL path, so scope the agent to the operations it needs, such as capturing a screenshot from a chosen location. You choose the operations it may call, so anything beyond capture and location lookup is not included unless you add it. - **Credential handling:** Your GeoScreenshot apikey is stored once, encrypted, by your own Jentic One instance and attached as the apikey query parameter at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'capture a screenshot of a website from a specific country', and Jentic returns the GeoScreenshot screenshot operation with its input schema so the agent calls it directly without browsing the reference docs. ## Related APIs - **Urlbox** — General-purpose website screenshot API with rendering options but without dedicated geographic exit nodes. - **Browshot** — Screenshot service offering multiple browser instances and locations for visual capture. - **ApiFlash** — Website screenshot API often paired with geo-capture for combined visual QA pipelines. ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the GeoScreenshot API? Yes. Because you run Jentic One yourself, your own rules decide which GeoScreenshot operations the agent may call, so you can scope it to just capturing a screenshot with GET /screenshot and listing regions with GET /location. Anything beyond that, such as the GET /me/ account and credit lookup, stays out of reach unless you explicitly grant it. Your API key is held by your own instance and attached as the apikey query parameter at call time, never entering the agent's prompt.