Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Screenshotbase 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%2Fscreenshotbase.com%2Fscreenshotbase" | 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%2Fscreenshotbase.com%2Fscreenshotbase" | 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 Screenshotbase API.
Check API status and quota
Take a website screenshot
Integrate Screenshotbase API into automated workflows
Query and filter Screenshotbase API records by parameters
Monitor Screenshotbase API operational status and events
GET STARTED
Patterns agents use Screenshotbase API for, with concrete tasks.
★ Developer Tools Operations
Use the Screenshotbase API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including check API status and quota, take a website screenshot.
Call GET /status to check API status and quota
Data Retrieval and Monitoring
Query Screenshotbase 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 Screenshotbase API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Screenshotbase 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 'check API status and quota', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — screenshotbase is an api to capture full-page website screenshots as png, jpeg, or webp.
METHOD
PATH
DESCRIPTION
/status
Check API status and quota
/take
Take a website screenshot
/status
Check API status and quota
/take
Take a website screenshot
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Screenshotbase API by hand means sending your key in the apikey header against api.screenshotbase.com and building your own retry handling for capture requests. Through Jentic you install once, import Screenshotbase from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Screenshotbase exposes a status check and a screenshot-capture operation, so you limit the agent to the operations it needs, such as taking a screenshot or checking status. You choose the operations it may call, and any you leave out stay unavailable to the agent.
Credential isolation
Your Screenshotbase API 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 'check API status and quota' or 'take a screenshot', and Jentic returns the matching Screenshotbase 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 Screenshotbase API through Jentic.
What authentication does the Screenshotbase API use?
The Screenshotbase API uses an API key passed in the `apikey` header. 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 check API status and quota with the Screenshotbase API?
Yes. Use the GET /status endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Screenshotbase 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 check API status and quota through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check API status and quota'. Jentic returns the matching Screenshotbase API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Screenshotbase API have?
The Screenshotbase API exposes 2 endpoints covering screenshots, account operations.
Can I limit what my agent is allowed to do with the Screenshotbase API?
Yes. The Screenshotbase API exposes just two operations, the status-and-quota check (GET /status) and the screenshot capture (GET /take), and because Jentic One is self-hosted your own rules decide which of them the agent may call. You can allow only the capture operation, or only the status check, and any operation you leave out stays unavailable to the agent. Jentic One also holds and injects your API key at execution time, so the agent can only act within the operations and credentials you grant it.
For Agents
Programmatically check API status and quota, take a website screenshot. Covers 2 operations with apiKey authentication.
Use for: I need to check API status and quota, I want to take a website screenshot, Get the current status of Screenshotbase API resources, List all records from Screenshotbase API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Screenshotbase is an API to capture full-page website screenshots as PNG, JPEG, or WEBP. Check API status and quota, and take website screenshots with extensive customization options. The API exposes 2 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>