Google Cloud Memorystore for Memcached API
Browse all Google APIs✓ Official Vendor SpecStorageDatabaseoauth212 EndpointsREST
For Agents
Provision and manage Cloud Memorystore for Memcached instances: create and delete instances, change Memcached parameters on live nodes, upgrade engine versions, and reschedule maintenance.
Use for: Provision a new Cloud Memorystore for Memcached instance with 3 nodes, List all Memcached instances under my project and their versions, Update Memcached parameters on a running instance, Apply previously updated parameters across all nodes of an instance
Not supported: Does not handle cache reads or writes, persistence, or Redis-style data structures — use for Memcached instance lifecycle, parameter management, version upgrades, and maintenance scheduling only.
Cloud Memorystore for Memcached provides a managed Memcached service on Google Cloud, with this API covering instance lifecycle, parameter management, version upgrades, and maintenance scheduling. Instances are scoped to project locations and most state changes return long-running operation handles. The API exposes apply-parameters and update-parameters semantics that let teams change Memcached configuration on running nodes, and rescheduleMaintenance lets workloads control planned maintenance windows.
Install Jentic One Beta
Connect the Cloud Memorystore for Memcached API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Memorystore for Memcached 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Memorystore for Memcached API.
Provision and delete Memcached instances inside a Google Cloud project location
List Memcached instances and their node counts and versions
Update Memcached parameters and apply them across the running nodes
Trigger an in-place version upgrade of a Memcached instance
Reschedule a planned maintenance window for an instance
Cancel and inspect long-running provisioning and update operations
Use Cases
Patterns agents use Cloud Memorystore for Memcached API for, with concrete tasks.
★ Cache layer provisioning
Provision a managed Memcached instance to sit in front of a backend database for read-heavy workloads, specifying node count, node CPU and memory, and the network. Provisioning is a long-running operation that typically completes within a few minutes for small instances.
Create an instance named cache-prod under projects/acme/locations/us-central1 with 3 nodes of 4 vCPUs and 4 GB memory each and poll the operation until done
Live parameter tuning
Update Memcached parameters such as max_item_size on a running instance and use applyParameters to push the change to all nodes without recreating the cluster. Useful when applications begin storing larger objects or require connection-related tuning.
Update parameters on instance cache-prod to set max_item_size=4194304, then call applyParameters on all node IDs
Maintenance window control
Reschedule a planned maintenance window so it falls outside critical traffic periods. The rescheduleMaintenance endpoint accepts a target start time or instructs the service to take the next available window, returning a long-running operation that resolves once the schedule is updated.
Call rescheduleMaintenance on instance cache-prod with rescheduleType SPECIFIC_TIME and scheduleTime set to next Sunday 03:00 UTC
Agent integration via Jentic
AI agents managing cache infrastructure can use the Memcached API through Jentic to provision instances, tune parameters, and time maintenance windows without holding the underlying OAuth refresh token. Jentic surfaces the long-running operation handles for the agent to poll.
List all instances in projects/acme/locations/us-central1 with no traffic in the last 7 days and queue a delete request for each
Key Endpoints
12 endpoints — cloud memorystore for memcached provides a managed memcached service on google cloud, with this api covering instance lifecycle, parameter management, version upgrades, and maintenance scheduling.
METHOD
PATH
DESCRIPTION
GET
/v1/{+parent}/instances
List Memcached instances in a project location
DELETE
/v1/{+name}
Delete a Memcached instance
POST
/v1/{+name}:applyParameters
Apply staged parameters to nodes
PATCH
/v1/{+name}:updateParameters
Update Memcached parameters
POST
/v1/{+name}:upgrade
Upgrade a Memcached instance version
POST
/v1/{+instance}:rescheduleMaintenance
Reschedule a maintenance window
GET
/v1/{+name}/operations
List long-running operations
GET
/v1/{+parent}/instances
List Memcached instances in a project location
DELETE
/v1/{+name}
Delete a Memcached instance
POST
/v1/{+name}:applyParameters
Apply staged parameters to nodes
PATCH
/v1/{+name}:updateParameters
Update Memcached parameters
POST
/v1/{+name}:upgrade
Upgrade a Memcached instance version
POST
/v1/{+instance}:rescheduleMaintenance
Reschedule a maintenance window
GET
/v1/{+name}/operations
List long-running operations
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google Cloud OAuth 2.0 client credentials and refresh tokens are stored encrypted in the Jentic vault. Agents receive short-lived bearer tokens scoped to cloud-platform; the refresh token and client secret never enter the agent's context.
Intent-based discovery
Agents search Jentic by intent such as provision memcached instance or update memcached parameters and Jentic returns the matching operations with input schemas, so the agent does not have to navigate Google Cloud's discovery documents.
Time to first call
Direct integration takes a day or more for OAuth setup, long-running operation polling, and parameter application logic. Through Jentic the same flows are under an hour: search, load schema, execute, poll the returned operation.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cloud Memorystore for Memcached API through Jentic.
What authentication does the Memorystore for Memcached API use?
The API uses Google OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope. Through Jentic, the OAuth credentials are held in the encrypted vault and the agent only sees a scoped, short-lived bearer token.
Can I update Memcached parameters on a running instance?
Yes. Call updateParameters with the new parameter values, then applyParameters to push the staged changes to nodes. Both calls return long-running operations you can poll for completion.
What are the rate limits for this API?
Per-project quotas for the Memorystore service govern how many instances you can have and how often lifecycle operations can be invoked. See the Cloud Console quotas page; bulk lifecycle calls should respect concurrent operation limits and use exponential backoff on 429 responses.
How do I reschedule a Memcached maintenance window through Jentic?
Search Jentic for reschedule memcached maintenance, load the operation that maps to /v1/{+instance}:rescheduleMaintenance, and execute with the instance name and a SPECIFIC_TIME scheduleTime. Jentic returns the long-running operation for polling.
Is the Memorystore for Memcached API free?
The API itself is not separately billed; you pay for provisioned Memcached node-hours and any associated network egress. See the Memorystore pricing page for current rates.
Does this API let me read or write cache values?
No, this is the control-plane API for managing instances. Application-level cache reads and writes happen over the standard Memcached protocol against the instance's discoveryEndpoint, not through this API.
GET STARTED