Official vendor OpenAPI document · agent-readyCloud InfrastructureComputeoauth29 EndpointsREST
For Agents
Submit, list, and cancel Google Cloud Batch jobs that run containerised or script-based tasks on managed Compute Engine and GKE.
Use for: I need to submit a Batch job that runs a Docker container across 100 tasks, List all Batch jobs in europe-west1 and their current state, Cancel a running Batch job that has produced enough results, Find every Batch location available to my project
Not supported: Does not store task results, manage long-running services, or run interactive workloads - use for submitting and monitoring batch jobs on managed Compute Engine and GKE only.
The Google Cloud Batch API runs batch compute jobs on managed Compute Engine and GKE infrastructure without requiring users to operate their own scheduler. It exposes operations to submit jobs that bundle one or more tasks, list and cancel running jobs, and report task state from inside the job. Batch handles VM provisioning, retries, and result collection so HPC, genomics, simulation, and rendering workloads can be expressed as a single API call. The API is the orchestration surface only and does not store result artifacts.
Install Jentic One Beta
Connect the Batch API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Batch 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%2Fbatch" | 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%2Fbatch" | 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 Batch API.
Submit a Batch job that runs one or more tasks via POST /v1/{+parent}/jobs
List jobs in a project and location with GET /v1/{+parent}/jobs and filter by state
Cancel a running job via /v1/{+name}:cancel to stop further task execution
Report task state from inside a running task via /v1/{+parent}/state:report for custom task progress
Delete completed jobs with DELETE /v1/{+name} to clean up history
List long-running operations and Batch locations available to a project
Use Cases
Patterns agents use Batch API for, with concrete tasks.
★ HPC and Simulation Workloads
Run high-performance computing, simulation, or rendering jobs as a single submission against a managed scheduler that handles VM provisioning, retries, and task coordination. Submit a job with the desired task count and resource shape; Batch boots the right machines, runs each task, and tears the fleet down on completion.
POST a Batch job spec to /v1/{parent}/jobs with taskCount=1024 and the desired machine type, then poll the operation until done.
Genomics and Scientific Pipelines
Express genomics or scientific pipelines as Batch jobs that fan out across many input samples, with each task running the same container against a different input. Suitable for sequencing variant calling, image processing pipelines, and large-scale data preprocessing without operating a Slurm or Kubernetes cluster directly.
Submit a Batch job whose runnable is a genomics container, with one task per sample listed in a Cloud Storage manifest.
Cost-Aware Job Cancellation
Watch a running job and cancel it once enough samples have produced acceptable results, capping cost on long-tail tasks. The API exposes both job listing and a cancel endpoint, so a controller running on a separate node can drive cost-aware execution policies.
POST to /v1/{name}:cancel once a downstream signal indicates enough successful task outputs have been collected.
AI Agent-Driven Batch Submission via Jentic
Use an AI agent to translate a high-level analysis request into a Batch job spec, submit it, and monitor it to completion. Through Jentic the agent finds Batch operations by intent and runs them with project credentials supplied at execute time, avoiding manual SDK setup in the agent runtime.
Use Jentic search for 'submit a Google Batch job', load the schema for POST /v1/{parent}/jobs, and execute it with the constructed job spec.
Key Endpoints
9 endpoints — the google cloud batch api runs batch compute jobs on managed compute engine and gke infrastructure without requiring users to operate their own scheduler.
METHOD
PATH
DESCRIPTION
POST
/v1/{+parent}/jobs
Create a Batch job with task definitions
GET
/v1/{+parent}/jobs
List Batch jobs in a project and location
GET
/v1/{+name}
Get a Batch job by resource name
DELETE
/v1/{+name}
Delete a Batch job
POST
/v1/{+name}:cancel
Cancel a running Batch job
POST
/v1/{+parent}/state:report
Report task state from inside a running task
GET
/v1/{+name}/locations
List Batch locations available to the project
POST
/v1/{+parent}/jobs
Create a Batch job with task definitions
GET
/v1/{+parent}/jobs
List Batch jobs in a project and location
GET
/v1/{+name}
Get a Batch job by resource name
DELETE
/v1/{+name}
Delete a Batch job
POST
/v1/{+name}:cancel
Cancel a running Batch job
POST
/v1/{+parent}/state:report
Report task state from inside a running task
GET
/v1/{+name}/locations
List Batch locations available to the project
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.
B
Batch API
- Foundational (D-)41/100
44
Foundational Compliance56
Developer Experience & Jentic Compatibility20
AI-Readiness & Agent Experience94
Agent Usability63
Security61
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
44
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
74%
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).
0%
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
81%
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.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
61
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
61%
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 Batch API by hand means setting up Google OAuth2, scoping a service account for batch access, and minting short-lived access tokens for each job call yourself. Through Jentic you install once, import the Batch API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
This API puts the project and job name in the URL path (/v1/{parent}/jobs, /v1/{name}), so a rule can pin your agent to one project or job: it can submit and list jobs there and nothing else. You choose the operations it may call, so actions like canceling or deleting a job are not included unless you add them.
Credential isolation
Your Google Cloud OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'submit a Google Batch job' or 'cancel a running job', and Jentic returns the matching Batch operation with its input schema so the agent calls the right endpoint without reading the discovery document.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Batch API through Jentic.
What authentication does the Batch API use?
The API uses Google OAuth 2.0 with cloud-platform scope. Service accounts must hold the roles/batch.* IAM role and have permission to act as the runner service account used by the job's VMs. Through Jentic the credential lives in the encrypted vault and the agent only sees a short-lived access token.
Can I cancel a Batch job that is no longer needed?
Yes. POST to /v1/{name}:cancel where name is the job resource path. Tasks already running are terminated and the job transitions to a cancelled state.
How do I submit a Batch job through Jentic?
Search Jentic for 'submit a Google Batch job'. Jentic returns POST /v1/{parent}/jobs with its full schema; build a job spec referencing your container image and task count, then execute. The credential is supplied from your Jentic One instance.
What are the rate limits for the Batch API?
Numeric limits are not declared in the spec; quotas are enforced per project on batch.googleapis.com along with the underlying Compute Engine quotas the job consumes. Check the project's quotas before scaling up tasks per job.
Where do Batch job results go?
The API does not store task outputs itself. Tasks typically write results to Cloud Storage, BigQuery, or another service of the user's choosing; the job spec defines the runnable that produces those outputs.
Can a running task report custom progress?
Yes. From inside a task, POST to /v1/{parent}/state:report with the task identifier and progress payload. This is useful when stages within a single task need observable progress.
Can I limit what my agent is allowed to do with the Google Cloud Batch API?
Yes. Because you run Jentic One yourself, your own rules decide which Batch operations and credentials the agent may use, and the API puts the project and job name in the URL path (/v1/{parent}/jobs, /v1/{name}), so a rule can pin the agent to a single project or job. You choose the operations it may call, so you can let it submit and list jobs while withholding destructive actions like canceling (/v1/{name}:cancel) or deleting (DELETE /v1/{name}) a job unless you explicitly add them. The Google Cloud OAuth credential is held by your own instance and injected only at execution, so the agent never controls scope beyond what you grant.
GET STARTED