Stateful tools your agents share.
A service is a set of tools with its own storage, called by name from every agent you have. Memory, watchers, inboxes and API hubs your agents share.
- Precise memory budgets for each tool and call.
- Tools available through your MCP connection.
- Call a service by name. No routing Worker to write.
Precise memory
Set memory per tool. Lower the reservation for an individual call when its input needs less.
Execution cost per million calls
- CrabTalk$0.24
4 MB reserved per call
- Durable Objects + Worker$2.02
128 MB duration billing allocation
Each call: 1 s waiting, 2 ms CPU, 2 rows read.
MCP built in
Your services’ tools, available through one CrabTalk connection in each MCP client.
- Recall a decision
- Read an inbox
- Check a website
Call services by name
Deploy under a name. Call its tools from the CLI, HTTP or another service. No routing Worker to write.
CrabTalk
Durable Objects
List-rate estimate · Rates and assumptions
Compare workloadsSafe to hand to an agent.
Keep existing callers working
A caller used watch in the last 30 days.
Proposed deployment
- Current tool
- watch(repo)
- Change
- Remove watch
- Force
- Off
Still serving
- Deployment
- Refused
- Version
- Previous version
- Callable tool
- watch(repo)
Inside a service.
Service
Your agents
Call tools. Read results.
Triggers
Settings for this copy
Reach external APIs
Secrets
The host inserts credentials into outgoing requests without exposing their values to service code.
DocumentationCall their tools by name
Run your first service.
Start with a published template, or give your coding agent CrabTalk’s skills to build your own.