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

# Screenshotmachinecom Screenshot Machine API

Website screenshot capture API. Capture screenshots of any website as PNG, JPG, or GIF images. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically capture a website screenshot. Covers 1 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for media and content only.

## Capabilities

- Capture a website screenshot
- Manage media data programmatically
- Integrate Screenshot Machine API into automated workflows
- Query and filter Screenshot Machine API records by parameters
- Monitor Screenshot Machine API operational status and events

## Use cases

### Media and Content Operations

Use the Screenshot Machine API to perform media operations programmatically. The API provides 1 endpoints covering core functionality including capture a website screenshot.

Example prompt: Call GET / to capture a website screenshot

### Data Retrieval and Monitoring

Query Screenshot Machine 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 Machine API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Screenshot Machine 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 'capture a website screenshot', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/` | Capture a website screenshot |

## Key resources

- **screenshots** — Operations related to screenshots

## 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:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 0 / 100
- **View full report:** https://jentic.com/apis/screenshotmachinecom/screenshotmachinecom/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 Screenshot Machine API by hand means passing your key in the query string against api.screenshotmachine.com and building your own retry handling for capture requests. Through Jentic you install once, import Screenshot Machine from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Screenshot Machine 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 Machine 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 'capture a website screenshot', and Jentic returns the matching Screenshot Machine operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

### What authentication does the Screenshot Machine API use?

The Screenshot Machine API uses an API key passed in the `key` 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 capture a website screenshot with the Screenshot Machine API?

Yes. Use the GET / endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Screenshot Machine 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 capture a website screenshot through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'capture a website screenshot'. Jentic returns the matching Screenshot Machine API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Screenshot Machine API have?

The Screenshot Machine API exposes 1 endpoints covering screenshots operations.

### Can I limit what my agent is allowed to do with the Screenshot Machine API?

Yes. The Screenshot Machine API exposes a single screenshot-capture operation (GET /), and because Jentic One is self-hosted, your own rules decide whether the agent may call it. You grant access to just that capture operation and nothing else in the API Directory is reachable unless you add it. The stored API key is injected only at execution time for the operations you have allowed.
