Google Cloud Storage JSON API
Browse all Google APIs37
AI ReadinessNon-Ready (F)37/100
Official vendor OpenAPI document · agent-readyStorageObject Storageoauth281 EndpointsREST
For Agents
Upload, download, copy, and manage objects in Google Cloud Storage buckets. Configure bucket lifecycle, IAM, retention, and Pub/Sub notifications.
Use for: I want to upload a file to a Cloud Storage bucket, Download an object from a Cloud Storage bucket, List all objects in a bucket with a given prefix, Create a new bucket in a specific region
Not supported: Does not handle relational queries, block storage volumes, or end-user file sharing UI - use for managing buckets and immutable objects in Google Cloud Storage only.
The Cloud Storage JSON API manages buckets and objects on Google Cloud Storage. It covers bucket lifecycle and configuration (location, storage class, retention policy, CORS, lifecycle rules, IAM), object operations (insert, get, list, copy, compose, rewrite, delete), ACL management at both bucket and object level, HMAC keys for interoperable access, notifications to Pub/Sub, and Anywhere Cache resources for low-latency regional reads. Object content uploads use the dedicated upload host with multipart or resumable protocols.
Install Jentic One Beta
Connect the Cloud Storage JSON API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Storage JSON 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%2Fstorage" | 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%2Fstorage" | 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 Cloud Storage JSON API.
Create, list, update, and delete Cloud Storage buckets with chosen storage class and location
Upload, download, copy, compose, and rewrite objects within and across buckets
Manage bucket and object ACLs and IAM policies at fine granularity
Configure lifecycle rules, retention policies, and object versioning on a bucket
Register Pub/Sub notifications to receive events when objects change
Manage HMAC keys for S3-compatible interoperable access to a bucket
Provision Anywhere Cache resources for low-latency regional reads of distant buckets
Use Cases
Patterns agents use Cloud Storage JSON API for, with concrete tasks.
★ Static Asset Hosting
Host product images, JavaScript bundles, and static HTML in a public Cloud Storage bucket fronted by a CDN. The Storage JSON API exposes bucket creation with website settings, object insert with cache-control metadata, and IAM policy management to make objects publicly readable. Lifecycle rules can transition cold assets to cheaper storage classes automatically.
POST /b with name=static.example.com, location=US, then upload index.html via the upload host with cacheControl='public, max-age=300'.
Lakehouse Ingestion
Ingest source files into a Cloud Storage data lake by uploading partitioned objects under date-prefixed paths, then publish a Pub/Sub notification on each new object so downstream pipelines pick them up. The API supports object insert, list-with-prefix for catalog scans, and notifications for change events.
Upload events_2026-06-10.parquet under bucket 'events-raw' with prefix 'date=2026-06-10/', then POST /b/events-raw/notificationConfigs with topic=projects/p/topics/raw-events.
Compliance Retention
Apply a bucket-level retention policy that locks objects against deletion for the regulatory retention window. The Storage JSON API exposes retentionPolicy with both a soft retention period and a lock action that makes the policy permanent for compliance officers' sign-off.
PATCH /b/audit-logs with retentionPolicy.retentionPeriod=2592000 (30d), then POST /b/audit-logs/lockRetentionPolicy.
AI Agent Document Workflow
An AI agent processing a user's uploaded contracts uploads each document to a Cloud Storage bucket, then triggers downstream extraction. Through Jentic, the agent searches for the upload operation, loads the schema, and executes - Jentic handles auth so the agent never sees the underlying access token.
Search Jentic for 'upload a file to Cloud Storage', execute the object insert call against bucket 'contracts' with the file content and contentType='application/pdf'.
Key Endpoints
81 endpoints — the cloud storage json api manages buckets and objects on google cloud storage.
METHOD
PATH
DESCRIPTION
GET
/b
List buckets in a project
POST
/b
Create a new bucket
GET
/b/{bucket}
Get a bucket's metadata
GET
/b/{bucket}/acl
List the ACL entries on a bucket
GET
/b/{bucket}/folders
List folders in a hierarchical-namespace bucket
GET
/b/{bucket}/anywhereCaches
List Anywhere Cache resources on a bucket
POST
/b/{bucket}/anywhereCaches/{anywhereCacheId}/pause
Pause an Anywhere Cache resource
GET
/b
List buckets in a project
POST
/b
Create a new bucket
GET
/b/{bucket}
Get a bucket's metadata
GET
/b/{bucket}/acl
List the ACL entries on a bucket
GET
/b/{bucket}/folders
List folders in a hierarchical-namespace bucket
GET
/b/{bucket}/anywhereCaches
List Anywhere Cache resources on a bucket
POST
/b/{bucket}/anywhereCaches/{anywhereCacheId}/pause
Pause an Anywhere Cache resource
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
Cloud Storage JSON API
- Non-Ready (F)37/100
48
Foundational Compliance56
Developer Experience & Jentic Compatibility16
AI-Readiness & Agent Experience89
Agent Usability63
Security65
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
48
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: D+Signals: 4
91%
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).
2%
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.
16
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
64%
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.
89
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: ASignals: 1
89%
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).
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 Cloud Storage JSON API by hand means configuring a service account, minting OAuth access tokens against the storage.googleapis.com/storage/v1 host, and refreshing them yourself. Through Jentic you install once, import the Cloud Storage JSON API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
Cloud Storage puts the bucket in the URL path (/b/{bucket}, /b/{bucket}/acl), so a rule can pin your agent to one bucket: it can read the bucket, its ACLs, and its folders and nothing else. You choose the operations it may call, so creating buckets or pausing caches is not included unless you add them.
Credential isolation
Your Cloud Storage 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 'upload a file to Cloud Storage' or 'list objects in a bucket', and Jentic returns the matching Cloud Storage 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 Cloud Storage JSON API through Jentic.
What authentication does the Cloud Storage JSON API use?
The Cloud Storage JSON API uses OAuth 2.0 with scopes such as devstorage.read_only, devstorage.read_write, or cloud-platform. HMAC keys are also supported for S3-compatible interoperability. Through Jentic, OAuth credentials are stored in your Jentic One instance and exchanged for short-lived access tokens.
Can I upload large files with the Storage JSON API?
Yes. Object uploads use the upload host (uploadType=resumable for files over a few MiB), which supports chunked, resumable transfers. The metadata-only POST /b/{bucket}/o initiates the resumable session and returns an upload URL the client streams content into.
What are the rate limits for the Cloud Storage JSON API?
Cloud Storage scales to very high object operation rates per bucket but enforces a soft limit of around 1 write per second per object name and recommended ramp-up patterns for new buckets. Per-project read and write quotas exist and can be inspected in the Google Cloud Console under IAM and admin > Quotas.
How do I copy an object between buckets through Jentic?
Search Jentic for 'copy a Cloud Storage object', load the objects.copy or objects.rewrite schema, and execute. POST /b/{sourceBucket}/o/{sourceObject}/copyTo/b/{destBucket}/o/{destObject} performs the copy in a single call; objects.rewrite is used for cross-region copies and storage class transitions on large objects.
Is the Cloud Storage JSON API free?
The API itself has no per-call charge. Cloud Storage costs come from storage volume per GB-month, network egress, and operation classes (Class A for writes, Class B for reads). A free tier of 5 GB Standard storage and limited operations is available.
Can I receive notifications when an object changes?
Yes. POST /b/{bucket}/notificationConfigs registers a Pub/Sub topic that receives object lifecycle events such as OBJECT_FINALIZE and OBJECT_DELETE, which downstream pipelines can subscribe to.
Can I limit what my agent is allowed to do with the Cloud Storage JSON API?
Yes. Because you run Jentic One yourself, your own rules decide which Cloud Storage operations and credentials the agent may use. Since the bucket sits in the URL path (/b/{bucket} and /b/{bucket}/acl), you can pin the agent to a single bucket so it only reads that bucket, its ACLs, and its folders. You also choose the exact operations it may call, so actions like creating buckets or pausing Anywhere Caches stay off limits unless you grant them.
GET STARTED