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

# PageVitals API

PageVitals provides website performance monitoring. The REST API allows accessing websites, pages, tests, multistep tests, budgets, field testing data, opportunities, and settings.

## For AI agents

PageVitals provides website performance monitoring. The REST API allows accessing websites, pages, tests, multistep tests, budgets, field testing data, opportunities, and settings.

## Scope

Provides access to PageVitals API functionality as defined in the OpenAPI specification.

## Capabilities

- List all websites
- Add website
- Delete website
- List pages
- Get page detail

## Use cases

### Basic PageVitals API Integration

Integrate PageVitals API into your application to access its core functionality.

Example prompt: Use the PageVitals API API to access vendor services and data.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/websites` | List all websites |
| POST | `/account/websites` | Add website |
| DELETE | `/{websiteId}` | Delete website |
| GET | `/{websiteId}/pages` | List pages |
| GET | `/{websiteId}/pages/{pageId}` | Get page detail |
| GET | `/{websiteId}/testseries` | List test series |
| GET | `/{websiteId}/tests` | List tests |

## Key resources

- **Main API** — Primary PageVitals API resources and operations

## Why Jentic

- **Setup:** Wiring PageVitals by hand means handling its X-API-Key auth against api.pagevitals.com, shaping website and test requests, and building your own retry and error handling. Through Jentic you install once, import the PageVitals API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** PageVitals puts the website id in the URL path (/{websiteId}/pages and /{websiteId}/tests), so a rule can pin your agent to one website: it can read that website's pages and tests and nothing else. You choose the operations it may call, so deleting a website is not included unless you add it.
- **Credential handling:** Your PageVitals key is stored once, encrypted, by your own Jentic One instance and injected as the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list PageVitals websites' or 'get test results for a site', and Jentic returns the matching PageVitals operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## FAQ

### What authentication does the PageVitals API use?

The PageVitals API uses apiKey authentication.

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

The PageVitals API has 7 endpoints available.

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

Yes. Because you run Jentic One yourself, your own rules decide which PageVitals operations and credentials the agent may use. Since PageVitals puts the website id in the URL path, such as /{websiteId}/pages and /{websiteId}/tests, you can pin the agent to a single website so it only reads that site's pages and tests. You also choose the exact operations it can call, so a destructive action like deleting a website stays off limits unless you explicitly allow it.