Google Cloud Functions API
Browse all Google APIs42
AI ReadinessFoundational (D-)42/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureServerlessoauth219 EndpointsREST
For Agents
Deploy, list, update, and delete Google Cloud Functions, plus orchestrate v2 upgrades with traffic redirection and source upload URLs. Useful for serverless deployment automation on GCP.
Use for: I need to deploy a new Cloud Function from my packaged source, List every function in our europe-west1 region, Generate a signed upload URL so my CI can push the source archive, Update the memory and timeout for an existing function
Not supported: Does not run function code, schedule invocations, or store source archives in repos - use for function lifecycle, source upload URL, and v2 upgrade orchestration only.
Google Cloud Functions runs short-lived, event-driven code without server management. The v2 API exposes function lifecycle operations - create, update, delete, list - plus signed download and upload URLs for source archives, and traffic-management endpoints used during version upgrades. Agents can deploy a new function from a source archive, generate a signed upload URL for a build artefact, list every function in a region, and orchestrate the v2 upgrade flow that detaches, redirects traffic, and commits or aborts the upgrade.
Install Jentic One Beta
Connect the Cloud Functions API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Functions 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%2Fcloudfunctions" | 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%2Fcloudfunctions" | 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 Functions API.
Deploy a new Cloud Function from a source archive in Cloud Storage
Generate a signed upload URL for a function source archive
Generate a signed download URL for an existing function source
List all functions in a region with paginated results
Patch a function's runtime configuration, memory, or environment variables
Detach a function from a v1 deployment to begin a v2 upgrade
Redirect, commit, or abort a function upgrade and roll traffic between versions
Use Cases
Patterns agents use Cloud Functions API for, with concrete tasks.
★ CI/CD-Driven Function Deployment
CI pipelines call generateUploadUrl to obtain a signed Cloud Storage URL, push the packaged source, and then call create or patch on the function resource referencing that source. The flow takes a few minutes per function and replaces gcloud-only deployment with a fully API-driven path that integrates with non-Google CI tools.
Call POST /v2/{parent}/functions:generateUploadUrl, push the archive to the returned URL, then POST /v2/{parent}/functions with sourceUploadUrl set
Region-Wide Function Inventory
Platform teams use the functions list endpoint to enumerate every Cloud Function in a region, surface runtime versions and memory settings, and flag functions that are running on deprecated runtimes. Pagination via pageToken supports environments with hundreds of functions.
Call GET /v2/{name}/locations to enumerate regions, then GET on the functions collection in each region with a filter on runtime
v1-to-v2 Upgrade Orchestration
Operators upgrading a v1 function to v2 call detachFunction to break the v1 link, redirectFunctionUpgradeTraffic to send traffic to the new version, and commitFunctionUpgrade or abortFunctionUpgrade depending on rollout health. Each step is a long-running operation, so callers poll until completion before moving on.
Call POST /v2/{name}:detachFunction, POST /v2/{name}:redirectFunctionUpgradeTraffic, then POST /v2/{name}:commitFunctionUpgrade once health checks pass
AI Agent Serverless Operator via Jentic
An agent invoked by a developer searches Jentic for the right Cloud Functions operation, deploys a packaged function, and reports the resulting URL. For upgrades, the agent orchestrates the detach, redirect, and commit sequence with health checks between each step. Jentic injects a scoped OAuth token at execution time.
Search Jentic for 'deploy google cloud function', execute against POST /v2/{parent}/functions with the prepared sourceUploadUrl, and return the resulting function URL
Key Endpoints
19 endpoints — google cloud functions runs short-lived, event-driven code without server management.
METHOD
PATH
DESCRIPTION
POST
/v2/{+name}:generateUploadUrl
Get a signed URL to upload function source
POST
/v2/{+name}:generateDownloadUrl
Get a signed URL to download function source
PATCH
/v2/{+name}
Update a function's configuration
DELETE
/v2/{+name}
Delete a function
POST
/v2/{+name}:detachFunction
Detach a function to begin a v1-to-v2 upgrade
POST
/v2/{+name}:redirectFunctionUpgradeTraffic
Redirect traffic during a function upgrade
POST
/v2/{+name}:commitFunctionUpgrade
Commit a completed function upgrade
POST
/v2/{+name}:abortFunctionUpgrade
Abort an in-progress function upgrade
POST
/v2/{+name}:generateUploadUrl
Get a signed URL to upload function source
POST
/v2/{+name}:generateDownloadUrl
Get a signed URL to download function source
PATCH
/v2/{+name}
Update a function's configuration
DELETE
/v2/{+name}
Delete a function
POST
/v2/{+name}:detachFunction
Detach a function to begin a v1-to-v2 upgrade
POST
/v2/{+name}:redirectFunctionUpgradeTraffic
Redirect traffic during a function upgrade
POST
/v2/{+name}:commitFunctionUpgrade
Commit a completed function upgrade
POST
/v2/{+name}:abortFunctionUpgrade
Abort an in-progress function upgrade
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 Functions API
- Foundational (D-)42/100
58
Foundational Compliance56
Developer Experience & Jentic Compatibility19
AI-Readiness & Agent Experience94
Agent Usability63
Security67
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
58
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C+Signals: 4
73%
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).
60%
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.
19
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
76%
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).
67
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
67%
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 Functions API by hand means setting up Google OAuth 2.0, minting short-lived tokens against the cloud-platform scope, and addressing each function by resource name against cloudfunctions.googleapis.com yourself. Through Jentic you install once, import the Cloud Functions API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
Cloud Functions puts the function resource name in the URL path (/v2/{+name}:generateUploadUrl, /v2/{+name}), so a rule can pin your agent to one function: it can generate upload URLs and patch that function and nothing else. You choose the operations it may call, so function deletion or the upgrade-commit and abort operations are not included unless you add them.
Credential isolation
Your Cloud Functions 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 'generate a Cloud Function upload URL' or 'update a function's configuration', and Jentic returns the matching Cloud Functions 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 Functions API through Jentic.
What authentication does the Cloud Functions API use?
The Cloud Functions API uses OAuth 2.0 with the cloud-platform scope. Tokens are issued for a Google service account or end user. Through Jentic, the OAuth credential lives in your Jentic One instance and the agent receives a short-lived access token only - the underlying service account JSON never enters agent context.
Can I deploy a Cloud Function from a CI pipeline using this API?
Yes. Call POST /v2/{parent}/functions:generateUploadUrl, push your zipped source to the returned signed URL, then POST /v2/{parent}/functions with sourceUploadUrl set to that URL and the runtime, entry point, and trigger configuration. The deployment runs as a long-running operation.
What are the rate limits for the Cloud Functions API?
Cloud Functions admin-API quotas are published per-method in the Google Cloud console under the Cloud Functions API quota page; typical defaults are several hundred deployment operations per minute per project, with separate per-region concurrency limits on long-running operations.
How do I orchestrate a v1-to-v2 function upgrade through Jentic?
Search Jentic for 'detach google cloud function' and execute the returned operation against POST /v2/{name}:detachFunction. Then call /v2/{name}:redirectFunctionUpgradeTraffic to shift traffic, and finally /v2/{name}:commitFunctionUpgrade once health checks pass - or /v2/{name}:abortFunctionUpgrade to roll back.
Can I update a function's runtime or memory without redeploying source?
Yes. PATCH /v2/{name} with an updateMask that lists the fields to change, such as serviceConfig.availableMemory or buildConfig.runtime. The patch reuses the existing source archive and only rebuilds when source-related fields change.
Is Cloud Functions free?
Cloud Functions includes a monthly free tier of invocations, GB-seconds, and outbound networking; usage beyond that is billed per invocation, per GB-second of execution, and for outbound networking as documented on the Cloud Functions pricing page.
Can I limit what my agent is allowed to do with the Cloud Functions API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which Cloud Functions operations and credentials your agent may use. Since the function resource name sits in the URL path (for example /v2/{+name}:generateUploadUrl and PATCH /v2/{+name}), a rule can pin the agent to a single function so it can only generate upload URLs and patch that function's configuration. Destructive or upgrade operations such as DELETE /v2/{+name}, commitFunctionUpgrade, and abortFunctionUpgrade stay out of reach unless you explicitly add them.
GET STARTED