Google Cloud Storage
Object storage service offering high durability, availability, and scalability for storing and accessing data on Google Cloud Platform.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Google Cloud Storage the way a machine reads it — 64 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Google Cloud Storage scores 65.9/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Google Cloud Storage
Each block below is one kind of artifact we hold for Google Cloud Storage. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Google Cloud Storage XML API
Amazon S3-compatible XML API for Google Cloud Storage.
Google Cloud Storage BucketAccessControls API
Operations for managing bucket-level access control lists
Google Cloud Storage Buckets API
Operations for managing Cloud Storage buckets
Google Cloud Storage DefaultObjectAccessControls API
Operations for managing default object access controls on buckets
Google Cloud Storage ObjectAccessControls API
Operations for managing object-level access control lists
Google Cloud Storage Objects API
Operations for managing objects within Cloud Storage buckets
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Google Cloud Storage JSON API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Gcp Cloud Storage Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Gcp Cloud Storage Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Multi-Regional Storage
Store data across multiple regions for high availability and low-latency access worldwide.
Object Lifecycle Management
Automatically transition objects between storage classes or delete them based on configurable rules.
Versioning
Maintain multiple versions of objects for data protection and recovery.
Fine-Grained Access Control
Control access using IAM policies, ACLs, and signed URLs for secure data sharing.
Object Composition
Compose multiple objects into a single object without downloading and re-uploading data.
Change Notifications
Watch for changes to objects in a bucket and receive push notifications.
Retention Policies
Lock retention policies to prevent object deletion for regulatory compliance.
Scroll within the panel for all 7 ·
Semantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Gcp Cloud Storage Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Google Cloud Storage API Rules
SPECTRALGoogle Cloud Storage API Rules
SPECTRALJSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Google Cloud Storage Bucket
JSON SCHEMABucketAccessControl
JSON SCHEMABucketList
JSON SCHEMABucket
JSON SCHEMAChannel
JSON SCHEMAComposeRequest
JSON SCHEMAError
JSON SCHEMAObjectAccessControl
JSON SCHEMAObjectList
JSON SCHEMAObject
JSON SCHEMAPolicy
JSON SCHEMARewriteResponse
JSON SCHEMAScroll within the panel for all 12 ·
JSON Structure 11
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Gcp Cloud Storage Json Bucket Access Control Structure
JSON STRUCTUREGcp Cloud Storage Json Bucket List Structure
JSON STRUCTUREGcp Cloud Storage Json Bucket Structure
JSON STRUCTUREGcp Cloud Storage Json Channel Structure
JSON STRUCTUREGcp Cloud Storage Json Compose Request Structure
JSON STRUCTUREGcp Cloud Storage Json Error Structure
JSON STRUCTUREGcp Cloud Storage Json Object Access Control Structure
JSON STRUCTUREGcp Cloud Storage Json Object List Structure
JSON STRUCTUREGcp Cloud Storage Json Object Structure
JSON STRUCTUREGcp Cloud Storage Json Policy Structure
JSON STRUCTUREGcp Cloud Storage Json Rewrite Response Structure
JSON STRUCTUREScroll within the panel for all 11 ·
Examples 11
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 11 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Data Lake Storage
Store structured and unstructured data at scale for analytics and machine learning pipelines.
Backup and Disaster Recovery
Store backups with configurable retention and cross-region replication for business continuity.
Static Website Hosting
Serve static web content directly from Cloud Storage buckets with custom domains.
Media Content Delivery
Store and serve media assets with CDN integration for low-latency content delivery.
Resources
Every other property we hold for Google Cloud Storage — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/gcp-cloud-storage · machine-readable index on apis.io