PageVitals API
Official vendor OpenAPI document · agent-readyDeveloper ToolsPackage RegistryapiKey7 EndpointsREST
For Agents
PageVitals provides website performance monitoring. The REST API allows accessing websites, pages, tests, multistep tests, budgets, field testing data, opportunities, and settings.
Use for: I need to access PageVitals API, How do I use the pagevitals.com API?, Get data from pagevitals.com
Not supported: Provides access to PageVitals API functionality as defined in the OpenAPI specification.
PageVitals provides website performance monitoring. The REST API allows accessing websites, pages, tests, multistep tests, budgets, field testing data, opportunities, and settings.
Install Jentic One Beta
Connect the PageVitals API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PageVitals API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpagevitals.com%2Fpagevitals" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpagevitals.com%2Fpagevitals" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with PageVitals API.
List all websites
Add website
Delete website
List pages
Get page detail
Use Cases
Patterns agents use PageVitals API for, with concrete tasks.
★ Basic PageVitals API Integration
Integrate PageVitals API into your application to access its core functionality.
Use the PageVitals API API to access vendor services and data.
Key Endpoints
7 endpoints — pagevitals provides website performance monitoring.
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
FAQs
Specific to using PageVitals API through Jentic.
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.
GET STARTED