Cloud Filestore API

Name: Cloud Filestore API API
Brand: Cloud Filestore API
Availability: InStock

✓ Official Vendor SpecStorageObject Storageoauth215 EndpointsREST

For Agents

Provision and manage Google Cloud Filestore NFS file server instances, backups, and replicas so an agent can automate shared file storage for cloud workloads.

Quickstart

Get started with Cloud Filestore API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"provision a managed nfs file server"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cloud Filestore API API.

Provision a managed NFS file server in a chosen Google Cloud region

Snapshot a Filestore instance into a backup for disaster recovery

Restore a Filestore instance from a previously created backup

Promote a replica Filestore instance to a standalone primary

GET STARTED

Start building with Cloud Filestore API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Cloud Filestore API API for, with concrete tasks.

★ Shared NFS Storage for GKE Workloads

Provision a managed Filestore instance to give multiple Google Kubernetes Engine pods read-write access to a shared file system without operating an NFS server. The API creates the instance in a chosen tier and region, exposes the mount address, and lets automation poll the long-running operation until ready. Integration into a Terraform-style pipeline takes a few hours.

Call POST /v1/{+parent}/instances to create a BASIC_HDD Filestore instance named shared-data in us-central1-a, then poll the returned operation via GET /v1/{+name}/operations until it reports done.

Scheduled Backups and Disaster Recovery

Create on-demand backups of a Filestore instance via POST /v1/{+parent}/backups, then restore them with POST /v1/{+name}:restore when data corruption or accidental deletion occurs. Backups are managed objects discoverable through GET /v1/{+parent}/backups, supporting compliance and recovery-point-objective requirements without external snapshot tooling.

Trigger POST /v1/{+parent}/backups for instance shared-data, wait for the operation to complete, and tag the resulting backup resource with description nightly-2026-06-10.

Replica Promotion for Regional Failover

When a primary Filestore instance becomes unavailable in a region, the API can promote a replica to a standalone instance via POST /v1/{+name}:promoteReplica, restoring write access for downstream workloads. This automates the failover step that would otherwise require manual coordination. Promotion is irreversible and best suited to genuine failover scenarios.

Call POST /v1/{+name}:promoteReplica on the replica resource and verify success by polling GET /v1/{+name} until the instance state reads READY without a sourceReplica field.

Agent-Managed Filestore Lifecycle via Jentic

An AI agent connected through Jentic can manage Filestore instances end to end — provision, back up, restore, and clean up — using natural-language intents. Jentic exposes the 15 Filestore endpoints, handles OAuth 2.0 authentication transparently, and lets the agent string together create, poll, and snapshot calls without dealing with raw REST URLs.

Through Jentic, search for provision a managed nfs file server, load the create instances operation, and execute it with project=my-project, location=us-central1-a, tier=BASIC_HDD.

Key Endpoints

15 endpoints — the cloud filestore api provisions and manages fully-managed nfs file servers on google cloud, providing shared persistent storage for compute engine and google kubernetes engine workloads.

METHOD

PATH

DESCRIPTION

POST

/v1/{+name}:restore

Restore a Filestore instance from a backup

POST

/v1/{+name}:revert

Revert a Filestore instance to an earlier snapshot

POST

/v1/{+name}:promoteReplica

Promote a replica instance to standalone primary

GET

/v1/{+parent}/backups

List backups under a project location

GET

/v1/{+name}/locations

List Filestore locations

POST

/v1/{+name}:cancel

Cancel a long-running Filestore operation

POST

/v1/{+name}:restore

Restore a Filestore instance from a backup

POST

/v1/{+name}:revert

Revert a Filestore instance to an earlier snapshot

POST

/v1/{+name}:promoteReplica

Promote a replica instance to standalone primary

GET

/v1/{+parent}/backups

List backups under a project location

GET

/v1/{+name}/locations

List Filestore locations

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google OAuth 2.0 service-account credentials are stored encrypted in the Jentic vault. Agents receive a scoped, short-lived access token per call so the underlying private key never enters the agent's prompt or memory.

Intent-based discovery

Agents search Jentic with intents like provision a managed nfs file server and Jentic returns the create-instances operation with its tier, location, and capacity parameters resolved from the spec.

Time to first call

Direct integration with Cloud Filestore: 1-3 days for OAuth, long-running-operation polling, and quota handling. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Google Cloud Storage API

Object storage for unstructured blobs rather than POSIX-compliant shared NFS.

Choose Cloud Storage when files don't need POSIX semantics or shared-mount access; use Filestore for NFS workloads such as legacy apps or GKE pods needing ReadWriteMany volumes.

Alternative

Firebase Storage API

Mobile and web client-facing object storage backed by Cloud Storage.

Choose Firebase Storage for end-user mobile uploads; use Filestore only for server-side workloads needing a shared file system.

Complementary

Google Cloud Billing API

Tracks the spend generated by provisioned Filestore instances and backups.

Choose Cloud Billing alongside Filestore to monitor and alert on storage costs after provisioning new instances.

FAQs

Specific to using Cloud Filestore API API through Jentic.

What authentication does the Cloud Filestore API use?

The API uses Google OAuth 2.0 with the cloud-platform scope. Through Jentic the OAuth credentials live in the Jentic vault and a short-lived access token is supplied to each request without entering the agent's context.

Can I create and restore Filestore backups with the Cloud Filestore API?

Yes. POST /v1/{+parent}/backups creates a backup of an instance and POST /v1/{+name}:restore restores an instance from a named backup. Both operations are long-running and return an operation resource you can poll under /v1/{+name}/operations.

What are the rate limits for the Cloud Filestore API?

Google Cloud enforces standard project-level quotas for write and read operations on Filestore. Concurrent instance creation is also bounded by per-region capacity quota, which can be raised in the Google Cloud console quota page.

How do I provision a Filestore NFS instance through Jentic?

Run pip install jentic, then search for provision a managed nfs file server, load the create instances operation, and execute it with project, location, instanceId, and tier parameters. Sign up at https://app.jentic.com/sign-up.

Does the Cloud Filestore API support promoting replicas?

Yes. POST /v1/{+name}:promoteReplica promotes a replica Filestore instance to a standalone primary, used during regional failover scenarios. The action is irreversible once the operation reports done.

Is the Cloud Filestore API free?

The API calls themselves are not separately billed, but the Filestore instances and backups they create are charged by tier, capacity, and region under standard Filestore pricing in the Google Cloud price list.