canonical: https://jentic.com/apis/interzoid.com/interzoid-global-page-load-performance-api

# Interzoid Global Page Load Performance API

The Interzoid Global Page Load Performance API measures the time taken to load a URL or perform an HTTP call from a chosen geographic origin (Paris, Tokyo, Mumbai, Frankfurt, London, Seoul, California, Sao Paulo, and others). It returns the elapsed Seconds, the Origin used, the PageResponseStatus, and the response body, so an agent can compare regional performance without provisioning probes in each region. The single GET endpoint is designed for ad hoc geographic latency checks and lightweight scheduled probing.

## For AI agents

Measure how long a URL takes to load from a chosen global origin so an agent can compare regional latency, run availability probes, or flag CDN regressions.

## Scope

Does not run browser-rendering audits, capture filmstrips, or replace a full RUM stack - use for single-call timed page-load probes from named global origins only.

## Capabilities

- Measure end-to-end page load time for a URL from a specified global origin
- Compare load times for the same URL across origins like Paris, Tokyo, and Sao Paulo
- Capture PageResponseStatus alongside Seconds to distinguish slow loads from outright failures
- Probe a JSON or HTML endpoint from a remote geography for compliance or SLA reporting
- Read the returned response body to verify content presence as part of a synthetic check

## Use cases

### Regional Performance Comparison

Compare how long the same URL takes to load from several geographic origins so an engineering team can decide where to add a CDN edge or relocate a regional service. The Global Page Load Performance API takes an origin and a url parameter and returns Seconds and PageResponseStatus, which can be tabulated into a regional latency matrix. The endpoint is well suited to manual investigations and lightweight scheduled jobs.

Example prompt: Call /globalpageload three times with origin set to Tokyo, Frankfurt, and Sao Paulo for url=https://example.com and report the three Seconds values.

### Synthetic Availability Probe

Run a synthetic probe against a public URL from a remote geography to verify both reachability and response correctness. The API returns PageResponseStatus and the response Contents, so an agent can confirm that the page loaded and that an expected token appears in the body. This complements a status-page integration that only checks from the home region.

Example prompt: Call /globalpageload with origin=London for url=https://example.com/health and fail the check if PageResponseStatus is not 200 or Seconds exceeds 3.

### CDN Regression Watch

Detect regressions in CDN-cached pages by sampling load time from several origins on a regular cadence and alerting when the median Seconds value crosses a threshold. The API's geographic origins make it possible to detect a single bad PoP without paying for a full RUM stack. PageResponseStatus is recorded alongside each sample for diagnosis.

Example prompt: Call /globalpageload every 10 minutes from origins Tokyo, Frankfurt, and Sao Paulo for url=https://example.com and raise an alert when the median Seconds value crosses 4.

### Agent-Driven Performance Audit via Jentic

An AI performance agent uses Jentic to call the Interzoid Global Page Load Performance API across a list of origins for a target URL, then summarizes the results in plain text for a stakeholder. Through Jentic the Interzoid license key is held in the credential vault and never enters the agent context. The agent does not need any prior knowledge of Interzoid's auth scheme.

Example prompt: Use Jentic to search for 'measure page load time from a global origin', load /globalpageload, and execute it from five origins for url=https://example.com to produce a comparison table.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/globalpageload` | Measure page load time for a URL from a chosen global origin |

## Key resources

- **Page Load Performance Time** — GET endpoint that accepts a global origin and a url and returns Seconds, PageResponseStatus, Origin, and the response Contents.

## Why Jentic

- **Setup:** Wiring the Interzoid Global Page Load Performance API by hand means obtaining a license key, appending it as a license query parameter on each call to /globalpageload, and handling the request plumbing yourself. Through Jentic you install once, import this API from the API Directory, store the license key once, and your agent calls it.
- **Permission scoping:** This API exposes a single read-only GET /globalpageload operation that takes a target URL and a named origin in the query, with no resource id in the URL path, so scoping is at the operation level: you limit the agent to the timed page-load probe it needs. It only measures load time and writes nothing, so there is no destructive operation to include.
- **Credential handling:** Your Interzoid license key is stored once, encrypted, by your own Jentic One instance and injected as the license parameter at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'measure page load time from a global origin', and Jentic returns the Global Page Load Performance operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Pingdom** — Hosted synthetic monitoring with multi-region probes, alerting, and SLA dashboards.
- **New Relic** — Full APM and synthetic monitoring platform, useful alongside on-demand global probes for deeper diagnosis.
- **Interzoid Get Global Time API** — Looks up the current local time for an origin, useful when timestamping probe results in the user's local timezone.

## FAQ

### What authentication does the Interzoid Global Page Load Performance API use?

The API uses an Interzoid license key passed as the required `license` query parameter on /globalpageload. Through Jentic the license key is held in the credential vault and injected at execution time, so the raw key never enters the agent context.

### Can I run the test from any global origin?

The origin parameter accepts a curated list of geographies including Paris, Tokyo, Mumbai, Frankfurt, London, Seoul, California, and Sao Paulo. Refer to the Interzoid service page for the current full list of supported origins.

### What are the rate limits for the Interzoid Global Page Load Performance API?

The OpenAPI spec does not declare a numeric rate limit. Each successful call decrements a credit balance returned in the Credits response field, and a 402 status is returned when credits are exhausted. Refer to interzoid.com for current per-license-tier throughput.

### How do I measure page load time from a specific country through Jentic?

Install the SDK with `pip install jentic`, search for 'measure page load time from a global origin', load /globalpageload, and execute it with origin and url. The Seconds and PageResponseStatus fields can be plotted directly.

### Does the API return the response body?

Yes. The 200 response includes a Contents field with the body of the fetched URL, alongside Seconds, PageResponseStatus, and Origin. This is useful for synthetic checks that need to verify a content marker.

### What does a 404 mean on this endpoint?

A 404 status from /globalpageload indicates that either the origin or the url parameter was not recognized or could not be reached. Validate the origin against the supported list before retrying.

### Can I limit what my agent is allowed to do with the Interzoid Global Page Load Performance API?

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use, and this API exposes only the single read-only GET /globalpageload operation. You can scope the agent to just that timed page-load probe, which takes a target URL and a named origin and returns Seconds, PageResponseStatus, and the response Contents. Since it only measures load time and writes nothing, there is no destructive operation to grant, and your Interzoid license key is injected at execution time without entering the agent's context.