Chrome Verified Access API
analytics:googleapis-verifiedaccess · developers.google.com/chrome/verified-access ↗
API for Verified Access chrome extension to provide credential verification for chrome devices connecting to an enterprise network
About the Chrome Verified Access API API
Chrome Verified Access API API on Apizie: 2 endpoints (Generates a new challenge., Verifies the challenge response.) returned as clean JSON through one API key. Send your own provider key in the x-upstream-key header. Call it over REST at https://zieapi.vercel.app/v1/analytics:googleapis-verifiedaccess/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.
| Project key | analytics:googleapis-verifiedaccess |
|---|---|
| Status | Your key |
| Endpoints | 2 |
| Category | Analytics |
| Source | developers.google.com/chrome/verified-access |
| Base URL | https://zieapi.vercel.app/v1/analytics:googleapis-verifiedaccess/{endpoint} |
| For AI tools | OpenAPI spec · Markdown (what is this?) |
Chrome Verified Access API API FAQ
How do I call the Chrome Verified Access API API?
Create a free Apizie key, then send POST https://zieapi.vercel.app/v1/analytics:googleapis-verifiedaccess/verifiedaccess-challenge-generate with the header x-api-key. Every endpoint returns { project, data, timestamp }.
Is the Chrome Verified Access API API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. Chrome Verified Access API itself also needs your own key from googleapis.com.
Can AI agents use the Chrome Verified Access API API?
Yes. Add the Apizie MCP server (https://zieapi.vercel.app/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key analytics:googleapis-verifiedaccess.
What is the status of the Chrome Verified Access API API?
Needs your own provider key (bring your own key)