Documentation
Queues for your code and your agents
Managed message queues with FIFO ordering, dead-letter queues and object storage. Build with the SDK or the REST API, or hand it to your agent over MCP.
Send your first message
// npm install @rindahq/sdk
import { Rinda } from '@rindahq/sdk';
const rinda = new Rinda({ apiKey: process.env.RINDA_API_KEY });
const orders = await rinda.queues.create({ name: 'orders' });
await rinda.queue(orders.id).send({ body: { orderId: 1 } });
Pick how you’ll build
SDK
TypeScript SDK
Typed clients for queues, messages and storage, with a worker loop that acknowledges for you.
SDK reference →RESTREST API
Any language, one API key. Every endpoint documented with runnable examples.
API reference →MCPYour agent
Point Claude Code, Cursor, Zed or any MCP client at Rinda and let it manage queues for you.
MCP server →Guides
- ConceptsOrganizations, projects, environments and queues
- MessagesSend, receive, acknowledge and extend
- WorkersReliable consumers that survive a crash
- FIFO queuesOrdering within a message group
- Dead-letter queuesWhere messages go after too many tries
- StorageLarge bodies and message history
- AuthenticationAPI keys, scopes and environments
- Moving from SQSKeep the AWS SDK, change the endpoint