Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the screenshot.fyi 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fscreenshot.fyi%2Fscreenshot-fyi" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fscreenshot.fyi%2Fscreenshot-fyi" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with screenshot.fyi API.
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
GET STARTED
Patterns agents use screenshot.fyi API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'take screenshot', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — screenshot.
METHOD
PATH
DESCRIPTION
/api/take
Take Screenshot
/api/take
Take Screenshot
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using screenshot.fyi API through Jentic.
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.
For Agents
Programmatically take screenshot. Covers 1 operations with apiKey authentication.
Use for: I need to take screenshot, Find available developer tools operations, Get the current status of screenshot.fyi API resources, List all records from screenshot.fyi API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
screenshot.fyi provides an API to generate screenshots of web pages with customizable options. The API exposes 1 endpoints secured with apiKey authentication.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>