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.
1 endpointsGoogle's API Discovery Service is the meta-API that describes every other Google API. Two endpoints expose the directory of supported APIs and the machine-readable Discovery REST description for each one — methods, parameters, schemas, scopes, and base URLs. Client library generators, IDE tooling, and Jentic itself use this surface to bootstrap integrations against the entire googleapis.com surface without hand-written specs.
2 endpointsThe Apigee API is the control plane for Google Cloud's enterprise API management platform. It exposes operations to develop and secure API proxies, deploy and undeploy proxy revisions, monitor traffic, configure environments and instances, manage developer apps and API products, and run analytics and monetization workflows. Resources include organizations, environments, API proxies, shared flows, target servers, key value maps, and developer portals.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"find live events near a location"
# → Jentic returns the GET /events tool with parameter schema, agent executes.