Interzoid Global Page Load Performance API

Name: Interzoid Global Page Load Performance API API
Brand: Interzoid Global Page Load Performance API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey1 EndpointsREST

For Agents

Connect the Interzoid Global Page Load Performance API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Interzoid Global Page Load Performance 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Interzoid Global Page Load Performance API API.

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

GET STARTED

Start building with Interzoid Global Page Load Performance API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Interzoid Global Page Load Performance API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Interzoid Global Page Load Performance API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

1 endpoints — 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).

METHOD

PATH

DESCRIPTION

GET

/globalpageload

Measure page load time for a URL from a chosen global origin

GET

/globalpageload

Measure page load time for a URL from a chosen global origin

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Interzoid license API key is stored encrypted in the Jentic vault. Agents receive scoped access at execution time and the raw license value never enters the agent context.

Intent-based discovery

Agents search Jentic with an intent like 'measure page load time from a global origin' and receive the /globalpageload operation with its input schema, ready to execute.

Time to first call

Direct integration with Interzoid: half a day for auth, error handling, and a small scheduler. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Pingdom

Hosted synthetic monitoring with multi-region probes, alerting, and SLA dashboards.

Choose Pingdom when ongoing managed alerting and dashboards are required rather than ad hoc probes.

Complementary

New Relic

Full APM and synthetic monitoring platform, useful alongside on-demand global probes for deeper diagnosis.

Use New Relic for in-app traces and pair Interzoid for cheap on-demand regional checks.

Complementary

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.

Use to convert probe timestamps to the locale of the chosen origin before reporting.

FAQs

Specific to using Interzoid Global Page Load Performance API API through Jentic.

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.