canonical: https://jentic.com/apis/screenshotbase.com/screenshotbase

# Screenshotbase API

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.

## For AI agents

Programmatically check API status and quota, take a website screenshot. Covers 2 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'check API status and quota', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/status` | Check API status and quota |
| GET | `/take` | Take a website screenshot |

## Key resources

- **Screenshots** — Capture website screenshots
- **Account** — Account status and quota information

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 69 / 100
- **View full report:** https://jentic.com/apis/screenshotbase.com/screenshotbase/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 <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.