Google Cloud Filestore API

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

✓ Official Vendor SpecStorageObject Storageoauth215 EndpointsREST

Install Jentic One Beta

Connect the Cloud Filestore API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Filestore 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Filestore 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

GET STARTED

Start building with Cloud Filestore API

Explore with Jentic

View OpenAPI Document

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.

Use for: Provision a managed NFS file server in us-central1, Create a backup of a Filestore instance before a maintenance window, Restore a Filestore instance from yesterday's backup, List all Filestore backups in a Google Cloud project

Not supported: Does not store object blobs, serve HTTP file downloads, or back mobile clients directly - use for managed NFS file server provisioning and backup only.

Use Cases

Patterns agents use Cloud Filestore 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 Jentic?

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

Credential isolation

Your Google service-account 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 'provision a managed NFS file server' or 'restore a filestore backup', and Jentic returns the matching Cloud Filestore operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Cloud Filestore 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 your Jentic One instance 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. Get started with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Cloud Filestore API?

Yes. Because you run Jentic One yourself, your own rules decide which Cloud Filestore operations the agent may call and which credential it uses. Filestore puts the instance and backup resource in the URL path, such as /v1/{name}:restore and /v1/{parent}/backups, so a rule can pin the agent to a single instance or backup and nothing else. You can allow read and provisioning calls while withholding destructive operations like revert and promoteReplica unless you explicitly grant them.

Google Cloud Filestore API

Connect the Cloud Filestore API to your agent

Capabilities

Start building with Cloud Filestore API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs