Official vendor OpenAPI document · agent-readySecurityComplianceoauth211 EndpointsREST
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.
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.
Install Jentic One Beta
Connect the Checks API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Checks 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fchecks" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fchecks" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Checks 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
Track long-running scan operations and cancel or wait on them
Retrieve historical scan results for trend analysis across releases
Use Cases
Patterns agents use Checks 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.
Key Endpoints
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
POST
/v1alpha/aisafety:classifyContent
Classify content against AI safety policies
POST
/v1alpha/{+parent}/reports:analyzeUpload
Upload an app bundle and start a privacy scan
GET
/v1alpha/{+parent}/reports
List app privacy and compliance reports
POST
/v1alpha/{+parent}/scans:generate
Generate a new repository scan
GET
/v1alpha/{+parent}/scans
List repository scans
POST
/v1alpha/{+name}:wait
Wait on a long-running operation
POST
/v1alpha/aisafety:classifyContent
Classify content against AI safety policies
POST
/v1alpha/{+parent}/reports:analyzeUpload
Upload an app bundle and start a privacy scan
GET
/v1alpha/{+parent}/reports
List app privacy and compliance reports
POST
/v1alpha/{+parent}/scans:generate
Generate a new repository scan
GET
/v1alpha/{+parent}/scans
List repository scans
POST
/v1alpha/{+name}:wait
Wait on a long-running operation
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Checks API
- Foundational (D)45/100
69
Foundational Compliance56
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability100
Security65
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
69
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B+Signals: 4
75%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
20
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
80%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
65
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
65%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Checks API by hand means setting up Google Cloud service account auth with the cloud-platform scope, minting scoped access tokens, and polling report and scan operations to completion yourself. Through Jentic you install once, import the Checks API from the API Directory, store the service account credential once, and your agent calls it.
Permission scoping
The report and scan operations put the project in the URL path (/v1alpha/{+parent}/reports, /v1alpha/{+parent}/scans:generate), so a rule can pin your agent to one project while it also runs the stateless aisafety classifier. Limit it to the operations it needs, such as classifyContent or analyzeUpload, and other operations are not included unless you add them.
Credential isolation
Your Google Cloud service account credential with the cloud-platform scope is stored once, encrypted, by your own Jentic One instance and injected at execution time. The agent receives only short-lived access tokens and the service account JSON never enters its prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'classify generated text for AI safety', and Jentic returns the aisafety classifyContent operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Checks 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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the Google Checks API?
Yes. Because you run Jentic One yourself, your own rules decide which Checks operations and credentials the agent may use, so you can allow only what a task needs, such as aisafety:classifyContent or reports:analyzeUpload, and leave every other operation off unless you add it. Since the report and scan operations carry the project in the URL path (/v1alpha/{+parent}/reports and /v1alpha/{+parent}/scans:generate), a rule can also pin the agent to a single Google Cloud project while it still runs the stateless AI safety classifier. The service account credential stays in your instance, and the agent only ever calls the operations you have granted it.
GET STARTED