verifiedaccess.googleapis.com
Chrome Verified Access lets enterprise network services verify that ChromeOS or Chrome browser clients are genuine, managed, and policy-compliant. It is used in enterprise access scenarios such as VPNs, intranet pages, and certificate-based network access.
verifiedaccess.googleapis.com exposes one REST API, the Chrome Verified Access API, authenticated with either a Google OAuth 2.0 access token for the Verified Access scope or a Google Cloud API key.
- Chrome Verified Access APIdiscovered
In the Google Cloud Console Credentials page, create or select a Google Cloud project, enable the Chrome Verified Access API, then create an API key. The developer guide explicitly says to enable the API and create an API key for your application.
Create or use a Google Cloud project in the Google API Console, enable the Chrome Verified Access API, then obtain a Google OAuth 2.0 access token for the scope https://www.googleapis.com/auth/verifiedaccess. The discovery document lists this OAuth scope for the API. For server-to-server use, the developer guide says to create a service account after enabling the API.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing