Accelerated Mobile Pages (AMP) URL API

Name: Accelerated Mobile Pages (AMP) URL API API
Brand: Accelerated Mobile Pages (AMP) URL API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring Observabilitynone1 EndpointsREST

For Agents

Resolve canonical URLs to their AMP and AMP Cache equivalents in one batch call, so an agent can route mobile traffic to the lighter AMP version where available.

Quickstart

Get started with Accelerated Mobile Pages (AMP) URL API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"find amp version of a list of urls"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Accelerated Mobile Pages (AMP) URL API API.

Resolve a batch of up to 50 canonical URLs into their AMP equivalents in a single request

Return the Google AMP Cache URL alongside each AMP URL for direct CDN-served fetching

Surface a structured error per URL when no AMP version exists, separating not-found from invalid input

Pre-fetch AMP pages for top-of-funnel content to feed mobile search and discovery surfaces

GET STARTED

Start building with Accelerated Mobile Pages (AMP) URL API API

Explore with Jentic

View OpenAPI Spec

Use for: Find the AMP version of a list of news article URLs, Get the AMP Cache URL for a canonical blog post URL, Resolve 50 canonical URLs to AMP URLs in one call, Check whether an AMP version exists for a given web page

Not supported: Does not validate AMP markup, render AMP pages, or report AMP indexing errors — use for resolving canonical URLs to AMP equivalents only.

The Accelerated Mobile Pages (AMP) URL API resolves a batch of canonical web URLs into their AMP equivalents and the corresponding Google AMP Cache URLs. It returns the AMP variant for each input URL when one is published or an explanatory error when no AMP version exists. Search teams and content distributors use it to programmatically pre-fetch or display AMP pages from a list of canonical URLs.

Use Cases

Patterns agents use Accelerated Mobile Pages (AMP) URL API API for, with concrete tasks.

★ Mobile Email Link Rewriting

An email platform rewrites article links in mobile newsletters to AMP equivalents so they load faster on phones. The ampUrls.batchGet endpoint accepts up to 50 URLs per call and returns the AMP URL plus the AMP Cache URL for each match, which the platform substitutes back into the email body.

Given a list of 50 article URLs, call ampUrls.batchGet and return a map from canonical URL to AMP Cache URL, falling back to the canonical URL when no AMP version exists.

Pre-fetching for Mobile Search

A mobile search experience pre-fetches AMP pages for the top results before the user taps through. The AMP URL API resolves canonical search results into AMP and AMP Cache URLs in a single request, letting the client warm its cache from Google's CDN rather than the origin server.

Take the top 10 search result URLs, call ampUrls.batchGet, and issue HEAD requests against each returned cdnAmpUrl to warm the AMP Cache.

AI Agent Mobile Content Optimisation

An AI agent that summarises web articles for a mobile reader uses Jentic to call the AMP URL API. When an AMP version is available, the agent fetches the lighter page for faster summarisation, and falls back to the canonical URL when no AMP variant is published.

For each canonical article URL, call ampUrls.batchGet and pick the cdnAmpUrl when the response contains an ampUrl entry, otherwise keep the canonical URL.

Key Endpoints

1 endpoints — the accelerated mobile pages (amp) url api resolves a batch of canonical web urls into their amp equivalents and the corresponding google amp cache urls.

METHOD

PATH

DESCRIPTION

POST

/v1/ampUrls:batchGet

Resolve a batch of canonical URLs to AMP and AMP Cache URLs

POST

/v1/ampUrls:batchGet

Resolve a batch of canonical URLs to AMP and AMP Cache URLs

Why though Jentic?

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

Credential isolation

The Google API key is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution rights — the raw key is never injected into the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'find amp version of a url') and Jentic returns the ampUrls.batchGet operation with its input schema, so the agent can submit a list of URLs without reading the discovery doc.

Time to first call

Direct integration: a few hours to provision an API key and parse the batch response shape. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Search Console API

Read AMP indexing status and crawl errors for the same domains

Use Search Console alongside the AMP URL API to confirm that resolved AMP URLs are actually indexed by Google Search.

Complementary

PageSpeed Insights API

Measure mobile performance for canonical and AMP variants

Call PageSpeed Insights after resolving an AMP URL to compare load metrics against the canonical page.

Alternative

Custom Search API

Programmatic search that returns canonical URLs across the web

Use Custom Search to discover URLs in the first place, then resolve them to AMP variants with the AMP URL API.

FAQs

Specific to using Accelerated Mobile Pages (AMP) URL API API through Jentic.

What authentication does the AMP URL API use?

The endpoint accepts requests with an API key passed as the key query parameter. No OAuth scope or user consent is required because the data is public. Jentic stores the API key in its encrypted vault and injects it at request time.

How many URLs can I resolve in a single call?

ampUrls.batchGet accepts up to 50 canonical URLs per request. Larger lists must be chunked client-side. The response returns one ampUrl entry per matched input and a separate urlErrors array for any URLs without an AMP equivalent.

What are the rate limits for the AMP URL API?

Google's default quota is 1,000 requests per 100 seconds per project, with a per-user limit of 100 requests per 100 seconds. Each batchGet call counts as one request regardless of how many URLs are inside it, so batching aggressively keeps quota usage low.

How do I resolve a URL to its AMP version through Jentic?

Run jentic search 'find amp version of a url', load the ampUrls.batchGet operation, and execute it with a list of canonical URLs. The agent receives a typed response with ampUrls and urlErrors arrays so it can branch on whether an AMP version was found.

Is the AMP URL API free?

Yes. The API is free under Google's standard API terms with the default project quota. There is no per-call charge.