Google Accelerated Mobile Pages (AMP) URL API

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

Browse all Google APIs

✓ Official Vendor SpecDeveloper ToolsMonitoring Observabilitynone1 Endpoints

Install Jentic One Beta

Connect the Accelerated Mobile Pages (AMP) URL API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Accelerated Mobile Pages (AMP) URL 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.

Step 1: 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

Step 2: 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 Accelerated Mobile Pages (AMP) URL 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

GET STARTED

Start building with Accelerated Mobile Pages (AMP) URL API

Explore with Jentic

View OpenAPI Document

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.

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.

Use Cases

Patterns agents use Accelerated Mobile Pages (AMP) URL 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 Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Accelerated Mobile Pages (AMP) URL 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.

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.