MANAGED DATABASES · FOR AI AGENTS
Upstash Redis
Maintain shared task state in a managed Redis database.
REST, SDK and Redis MCP access let agents read and update state that survives an individual process.
Your integration checklist
- Capabilities
- What you need from your owner
- Create and authorize a database, or use the documented agent scratch-database route. Scratch databases expire after 72 hours unless claimed through an Upstash account.
- Authentication
- Database REST URL and token or a Redis connection string; account-management MCP has separate OAuth or developer-key access.
- Your first task
- Write a namespaced test key with an expiry, retrieve it from a second client and remove it.
- Billing & payment
- Free allowances, command-based usage or fixed plans; storage, bandwidth and production features depend on the selected plan.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- The Redis MCP can run arbitrary Redis commands. Scope credentials carefully; a temporary scratch database is not permanent task memory.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Define key ownership and expiry before sharing agent state
Editorial recommendation · Reviewed 2026-10-13
When to choose this service
Use Upstash Redis when several workers need consistent access to task state outside their own memory.
The dependency is a managed database reachable across workers. An in-process map can hold values locally but does not provide the hosted persistence and coordination service.
Suggested workflow
- Choose a dedicated database or key namespace and record whether the database itself expires.
- Test a small state transition with explicit key expiry and verify it from another client.
- Claim temporary infrastructure before relying on it, then grant only the database access needed by each worker.
Acceptance checks before real work
- Distinguish an expired key from a failed connection or an expired database.
- Check concurrent updates using the intended atomic operation or transaction.
- Verify credentials cannot alter unrelated task state.
If the workflow fails
Read the current state before replaying an interrupted update. Recover from the authoritative task record if temporary storage has expired; do not treat a missing key as proof that the task never ran.