canonical: https://jentic.com/apis/savepage.io/savepage

# SavePage.io API

SavePage.io provides web page archiving and screenshot capture services. Save complete web pages with all assets for permanent archival. The API exposes 5 endpoints secured with apiKey authentication.

## For AI agents

Programmatically save web page, list archives. Covers 5 operations with apiKey authentication.

## Scope

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

## Capabilities

- Save web page
- List archives
- Get archive details
- Delete archive
- Capture screenshot

## Use cases

### Developer Tools Operations

Use the SavePage.io API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including save web page, list archives, get archive details.

Example prompt: Call POST /save to save web page

### Automated archives Management

Automate archives operations by combining multiple SavePage.io API endpoints. Agents can list archives and then get archive details in a single workflow.

Example prompt: Call GET /archives to list archives, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SavePage.io 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 'save web page', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/save` | Save web page |
| GET | `/archives` | List archives |
| GET | `/archives/{id}` | Get archive details |
| DELETE | `/archives/{id}` | Delete archive |
| POST | `/screenshot` | Capture screenshot |

## Key resources

- **archives** — Operations related to archives
- **save** — Operations related to save
- **screenshot** — Operations related to screenshot

## Why Jentic

- **Setup:** Wiring the SavePage.io API by hand means passing your key in the X-API-Key header and coordinating the save, archive listing, and screenshot calls yourself. Through Jentic you install once, import the SavePage.io API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** SavePage.io puts the archive id in the URL path (`/archives/{id}`), so a rule can pin your agent to one archive. You choose the operations it may call, so a destructive one like deleting an archive is not included unless you add it alongside the read.
- **Credential handling:** Your SavePage.io 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 'save a web page' or 'capture a screenshot', and Jentic returns the matching SavePage.io API 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 SavePage.io API use?

The SavePage.io 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 save web page with the SavePage.io API?

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

### What are the rate limits for the SavePage.io 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 save web page through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'save web page'. Jentic returns the matching SavePage.io API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SavePage.io API have?

The SavePage.io API exposes 5 endpoints covering archives, save, screenshot operations.

### Can I limit what my agent is allowed to do with the SavePage.io API?

Yes. Jentic One is self-hosted by you, so your own rules decide which SavePage.io operations and credentials the agent may use. You pick the exact endpoints it can call, so a destructive action like DELETE `/archives/{id}` stays out unless you explicitly grant it alongside reads such as GET /archives. Because the API puts the archive id in the URL path (`/archives/{id}`), a rule can also pin the agent to a single archive rather than your whole account.