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

# Rasterwise GetScreenshot API

Screenshot-as-a-service API for capturing webpage screenshots programmatically. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically take a screenshot of a url. Covers 1 operations with apiKey authentication.

## Scope

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

## Capabilities

- Take a screenshot of a URL
- Access GetScreenshot API communications resources via REST API
- Query GetScreenshot API endpoints with structured JSON responses
- Authenticate requests with apiKey credentials managed by Jentic
- Access GetScreenshot API resources programmatically via REST

## Use cases

### Communications Operations

Use the GetScreenshot API to perform communications operations programmatically. The API provides 1 endpoints covering core functionality including take a screenshot of a url.

Example prompt: Call GET /screenshot to take a screenshot of a url

### Data Retrieval and Monitoring

Query GetScreenshot API endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows.

Example prompt: Query the GetScreenshot API API to retrieve current data and verify the response structure

### AI Agent Integration via Jentic

AI agents discover and call GetScreenshot 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 a screenshot of a url', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/screenshot` | Take a screenshot of a URL |

## Key resources

- **Screenshots** — Operations related to Screenshots

## Why Jentic

- **Setup:** Wiring the GetScreenshot API by hand means setting its X-API-Key header on every request, encoding the URL and capture options as query parameters, and handling timeouts and retries yourself when a page is slow to render. Through Jentic you install once, import the GetScreenshot API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The GetScreenshot API exposes a single read GET /screenshot operation, so you limit the agent to the operations it needs, in this case just capturing a screenshot of a URL. It only calls the operations you allow, so nothing beyond screenshot capture is available unless you add it.
- **Credential handling:** Your GetScreenshot 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 'take a screenshot of a url', and Jentic returns the matching GetScreenshot API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the GetScreenshot API use?

The GetScreenshot API uses an API key passed in the `X-API-Key` 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 take a screenshot of a url with the GetScreenshot API?

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

### What are the rate limits for the GetScreenshot 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 a screenshot of a url through Jentic?

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

### How many endpoints does the GetScreenshot API have?

The GetScreenshot API exposes 1 endpoints covering screenshots operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use. The GetScreenshot API exposes a single read operation, GET /screenshot, so you can restrict the agent to just capturing a screenshot of a URL. It only calls the operations you allow, so nothing beyond screenshot capture is available unless you grant it.