For Agents
Run privacy and compliance scans on mobile app bundles, classify AI-generated content for safety, and retrieve scan reports through the Google Checks platform.
Get started with Checks API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"classify generated content for AI safety policies"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Checks API API.
Upload an app bundle for analysis and trigger a privacy and compliance scan
Classify text or media content against AI safety policies in real time
List and retrieve detailed scan reports for an app or repository
Generate scans against a configured source code repository
GET STARTED
Use for: Run a Checks privacy scan on an Android app bundle, Classify a piece of generated text for AI safety violations, List the most recent Checks scan reports for an app, Get the result of a specific Checks scan
Not supported: Does not handle runtime device attestation, malware detection, or app distribution — use for privacy scans, AI safety classification, and repository scans only.
Google Checks is a privacy and AI safety compliance platform that scans mobile apps and AI-generated content for policy and regulatory issues, and the Checks API exposes its scan, report, and AI safety classification capabilities programmatically. It supports app privacy reports for Android and iOS bundles, repository scans, AI content classification against safety policies, and management of long-running operations. Product and security teams use it to add automated compliance gates to release pipelines.
Track long-running scan operations and cancel or wait on them
Retrieve historical scan results for trend analysis across releases
Patterns agents use Checks API API for, with concrete tasks.
★ Pre-Release Privacy Compliance Gate
Mobile teams add a CI step that uploads each release candidate APK or AAB to Checks via /v1alpha/{parent}/reports:analyzeUpload, waits for the analysis to finish, and fails the build if high-severity privacy or policy issues are detected. This catches issues like undisclosed SDKs and missing data-safety declarations before submission to Google Play. The integration replaces ad hoc manual reviews.
Upload an AAB to /v1alpha/{parent}/reports:analyzeUpload and poll the returned operation until done is true, then return the highest-severity finding.
Realtime AI Safety Classification
Teams shipping LLM features classify generated text and media against Google's AI safety policies before returning content to end users. The aisafety:classifyContent endpoint returns category labels and severity so the application can block, redact, or surface a warning. This is a synchronous call suitable for inline moderation.
POST to /v1alpha/aisafety:classifyContent with the candidate output and return any policy categories with severity HIGH.
Repository Scan Automation
Security teams connect a source repository to Checks and trigger scans on demand or on a schedule. The API's scans:generate operation kicks off a scan and the scans.list endpoint enumerates results for dashboards. This lets teams track trend lines for code-level privacy and policy issues across many repos.
POST to /v1alpha/{parent}/scans:generate for the connected repository and list the resulting scans for the account.
AI Agent Compliance Reviewer via Jentic
An AI agent through Jentic handles compliance triage — running a Checks scan, parsing the highest-severity issues, classifying any AI-generated text returned by another tool, and posting a summary back to the team. Jentic isolates the Google Cloud OAuth credentials so the agent never touches the service account key.
Through Jentic, search checks_classify_content, load schema, and execute it with the candidate response text and return the matched policy categories.
11 endpoints — google checks is a privacy and ai safety compliance platform that scans mobile apps and ai-generated content for policy and regulatory issues, and the checks api exposes its scan, report, and ai safety classification capabilities programmatically.
METHOD
PATH
DESCRIPTION
/v1alpha/aisafety:classifyContent
Classify content against AI safety policies
/v1alpha/{+parent}/reports:analyzeUpload
Upload an app bundle and start a privacy scan
/v1alpha/{+parent}/reports
List app privacy and compliance reports
/v1alpha/{+parent}/scans:generate
Generate a new repository scan
/v1alpha/{+parent}/scans
List repository scans
/v1alpha/{+name}:wait
Wait on a long-running operation
/v1alpha/aisafety:classifyContent
Classify content against AI safety policies
/v1alpha/{+parent}/reports:analyzeUpload
Upload an app bundle and start a privacy scan
/v1alpha/{+parent}/reports
List app privacy and compliance reports
/v1alpha/{+parent}/scans:generate
Generate a new repository scan
/v1alpha/{+parent}/scans
List repository scans
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google Cloud service account credentials with cloud-platform scope are stored encrypted in the Jentic vault (MAXsystem). Agents receive short-lived access tokens — service account JSON never enters the agent context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'classify generated text for AI safety') and Jentic returns the aisafety.classifyContent operation with its input schema.
Time to first call
Direct integration: 2-3 days for project enablement, OAuth setup, and async operation polling. Through Jentic: under 1 hour — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Play Integrity API
Verify that an app and device are genuine at runtime, complementing Checks' static scans.
Use Play Integrity for runtime device attestation; use Checks for pre-release privacy and policy scans.
Google Play Android Publisher API
Publish the AAB to the Play Store after Checks confirms it passes compliance gates.
Use Checks first; then use Android Publisher to upload and roll out the approved bundle.
Safe Browsing API
Check URLs against Google's threat lists rather than scanning app bundles.
Use Safe Browsing for URL threat lookups; use Checks when the artefact is a mobile app or AI-generated content.
Specific to using Checks API API through Jentic.
What authentication does the Checks API use?
It uses OAuth 2.0 with the cloud-platform scope on a Google Cloud project that has Checks enabled. Through Jentic, that credential lives in the Jentic vault and the agent receives only short-lived scoped access tokens.
Can I scan an Android AAB through the Checks API?
Yes. POST the bundle to /v1alpha/{parent}/reports:analyzeUpload as a media upload. The call returns a long-running operation; poll the operation under /v1alpha/{+name} until done is true and read the report from the response.
What are the rate limits for the Checks API?
Checks is in v1alpha with conservative per-project quotas — typically tens of scans per day and hundreds of aisafety:classifyContent calls per minute. Higher quota requires a request through the Google Cloud console.
How do I classify AI-generated content through Jentic?
Use the Jentic search query "classify content for AI safety" to discover the aisafety.classifyContent operation, load its schema, and execute it with the input content. Run pip install jentic to get started.
Is the Checks API stable?
The current surface is v1alpha, meaning fields and endpoints can change without long deprecation windows. Pin to a specific spec version and re-validate against new releases before upgrading.
Is the Checks API free?
Checks offers a free tier covering a fixed number of app scans and AI safety classifications per month, with paid tiers for higher volume. See the Google Checks pricing page for current details.
/v1alpha/{+name}:wait
Wait on a long-running operation