canonical: https://jentic.com/apis/googleapis.com/acceleratedmobilepageurl

# Google Accelerated Mobile Pages (AMP) URL API

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.

## For AI 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.

## Scope

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

## Capabilities

- 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
- Power link rewriters that swap canonical URLs for AMP URLs in mobile email and chat contexts

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/ampUrls:batchGet | Resolve a batch of canonical URLs to AMP and AMP Cache URLs |

## Key resources

- **AMP URLs** — Batch-resolve canonical URLs to their AMP and AMP Cache equivalents

## Why Jentic

- **Setup:** Wiring the AMP URL API by hand means calling acceleratedmobilepageurl.googleapis.com and batching your canonical URLs into the ampUrls:batchGet request body yourself. Through Jentic you install once, import the AMP URL API from the API Directory, and your agent calls it with unified logging alongside your authenticated APIs.
- **Permission scoping:** The AMP URL API exposes a single POST ampUrls:batchGet operation, so the agent's scope is that one operation: resolving canonical URLs to their AMP equivalents. You choose whether the agent may call it, and no other operation is reachable.
- **Credential handling:** This endpoint needs no stored secret, so your Jentic One instance holds no credential for it. Any key you do configure is stored encrypted and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find the amp version of a url', and Jentic returns the ampUrls.batchGet operation with its input schema so the agent submits a list of URLs without reading the discovery doc.

## Related APIs

- **Google Search Console API** — Read AMP indexing status and crawl errors for the same domains
- **PageSpeed Insights API** — Measure mobile performance for canonical and AMP variants
- **Custom Search API** — Programmatic search that returns canonical URLs across the web

## FAQ

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

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

Yes. Because Jentic One is self-hosted, your own rules decide what the agent can reach, and this API exposes just one operation: the ampUrls:batchGet call that resolves canonical URLs to their AMP equivalents. You choose whether to allow that single operation and which credentials it uses, and no other operation is available to the agent.