canonical: https://jentic.com/apis/screenshot.fyi/screenshot-fyi # screenshot.fyi API screenshot.fyi provides an API to generate screenshots of web pages with customizable options. The API exposes 1 endpoints secured with apiKey authentication. ## For AI agents Programmatically take screenshot. Covers 1 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - Take Screenshot - Manage developer tools data programmatically - Integrate screenshot.fyi API into automated workflows - Query and filter screenshot.fyi API records by parameters - Monitor screenshot.fyi API operational status and events ## Use cases ### Developer Tools Operations Use the screenshot.fyi API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including take screenshot. Example prompt: Call GET `/api/take` to take screenshot ### Data Retrieval and Monitoring Query screenshot.fyi API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed. Example prompt: Poll the primary screenshot.fyi API endpoint, compare response to last known state, and alert if changed ### AI Agent Integration via Jentic AI agents discover and call screenshot.fyi API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually. Example prompt: Search Jentic for 'take screenshot', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/take` | Take Screenshot | ## Key resources - **Take** — Operations for take ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 49 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 52 / 100 - Agent Usability: 94 / 100 - Security: 15 / 100 - AI Discoverability: 75 / 100 - **View full report:** https://jentic.com/apis/screenshot.fyi/screenshot-fyi/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the screenshot.fyi API by hand means passing your accessKey in the query string against www.screenshot.fyi and building your own retry handling for capture requests. Through Jentic you install once, import screenshot.fyi from the API Directory, store the access key once, and your agent calls it. - **Permission scoping:** The screenshot.fyi API exposes a single screenshot-capture operation, so you limit the agent to the operation it needs. You choose what it may call, and nothing else in the directory is reachable unless you add it. - **Credential handling:** Your screenshot.fyi access key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'take a screenshot of a page', and Jentic returns the matching screenshot.fyi operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Github** — Alternative developer tools API - **Gitlab** — Alternative developer tools API ## FAQ ### What authentication does the screenshot.fyi API use? The screenshot.fyi API uses an API key passed in the `accessKey` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I take screenshot with the screenshot.fyi API? Yes. Use the GET `/api/take` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the screenshot.fyi API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I take screenshot through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'take screenshot'. Jentic returns the matching screenshot.fyi API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the screenshot.fyi API have? The screenshot.fyi API exposes 1 endpoints covering take operations. ### Can I limit what my agent is allowed to do with the screenshot.fyi API? Yes. The screenshot.fyi API exposes a single operation, the GET `/api/take` screenshot-capture call, and because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. You can grant the agent just that capture operation and nothing else in the directory is reachable unless you add it. Your screenshot.fyi access key is held by your own instance and injected only at execution time, so the agent never sees the raw secret.