Redis Cloud API
42
AI ReadinessFoundational (D-)42/100
Official vendor OpenAPI document · agent-readyPaymentsBilling SubscriptionsapiKey23 EndpointsREST
For Agents
Programmatically create subscription, list subscriptions. Covers 23 operations with apiKey authentication.
Use for: I need to subscription, I want to subscriptions, Search for subscription, Find all subscription
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Redis Cloud REST API for managing Redis Enterprise Cloud resources including subscriptions, databases, cloud accounts, and access control. Provides programmatic management of hosted Redis instances. The API exposes 23 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Redis Cloud API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Redis Cloud 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%2Fredis.io%2Fredis" | 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%2Fredis.io%2Fredis" | 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 Redis Cloud API.
Create subscription
List subscriptions
Get subscription
Update subscription
Delete subscription
Use Cases
Patterns agents use Redis Cloud API for, with concrete tasks.
★ Payments Operations
Use the Redis Cloud API to perform payments operations programmatically. The API provides 23 endpoints covering core functionality including create subscription, list subscriptions, get subscription.
Call POST /subscriptions to create subscription
Automated Access Control Management
Automate access control operations by combining multiple Redis Cloud API endpoints. Agents can list subscriptions and then get subscription in a single workflow.
Call GET /subscriptions to list subscriptions, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Redis Cloud API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'create subscription', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
23 endpoints — redis cloud rest api for managing redis enterprise cloud resources including subscriptions, databases, cloud accounts, and access control.
METHOD
PATH
DESCRIPTION
POST
/subscriptions
Create subscription
GET
/subscriptions
List subscriptions
GET
/subscriptions/{subscriptionId}
Get subscription
PUT
/subscriptions/{subscriptionId}
Update subscription
DELETE
/subscriptions/{subscriptionId}
Delete subscription
POST
/subscriptions/{subscriptionId}/databases
Create database
GET
/subscriptions/{subscriptionId}/databases
List databases
GET
/subscriptions/{subscriptionId}/databases/{databaseId}
Get database
POST
/subscriptions
Create subscription
GET
/subscriptions
List subscriptions
GET
/subscriptions/{subscriptionId}
Get subscription
PUT
/subscriptions/{subscriptionId}
Update subscription
DELETE
/subscriptions/{subscriptionId}
Delete subscription
POST
/subscriptions/{subscriptionId}/databases
Create database
GET
/subscriptions/{subscriptionId}/databases
List databases
GET
/subscriptions/{subscriptionId}/databases/{databaseId}
Get database
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.
R
Redis Cloud API
- Foundational (D-)42/100
90
Foundational Compliance63
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience94
Agent Usability50
Security10
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
90
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
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.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
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.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
38%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
64%
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.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
10
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
10%
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 Redis Cloud API by hand means sending two separate keys on every call, the x-api-key and the x-api-secret-key headers, and building your own retry handling against the api.redislabs.com host. Through Jentic you install once, import the Redis Cloud API from the API Directory, store the key and secret once, and your agent calls it.
Permission scoping
The Redis Cloud API puts the subscription and database ids in the URL path (/subscriptions/{subscriptionId}/databases/{databaseId}), so a rule can pin your agent to one subscription and read or manage only its databases. You choose the operations it may call, so destructive ones like deleting a subscription or a database are not included unless you add them.
Credential isolation
Your Redis Cloud API key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a subscription' or 'list databases', and Jentic returns the matching Redis Cloud API 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.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using Redis Cloud API through Jentic.
What authentication does the Redis Cloud API use?
The Redis Cloud API uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create subscription with the Redis Cloud API?
Yes. Use the POST /subscriptions endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Redis Cloud API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create subscription through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create subscription'. Jentic returns the matching Redis Cloud API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Redis Cloud API have?
The Redis Cloud API exposes 23 endpoints covering access control, account, cloud accounts operations.
Can I limit what my agent is allowed to do with the Redis Cloud API?
Yes. Because you run Jentic One yourself, your own rules decide which Redis Cloud API operations and credentials the agent can use, so you can grant read-only calls like GET /subscriptions and GET /subscriptions/{subscriptionId}/databases while withholding destructive ones such as DELETE /subscriptions/{subscriptionId}. Since the subscription and database IDs sit in the URL path, a rule can pin the agent to a single subscription and let it manage only that subscription's databases. Your API key and secret are injected at execution time and never enter the agent's prompt or context.
GET STARTED