What is Bedrock?
Bedrock handles the hard parts of building AI agents:- Persistent Memory: Agents remember conversations across sessions with automatic summarization
- Tool Execution: Connect agents to SMS, email, calendars, or your own APIs via webhooks
- Autonomous Runtime: Agents run independently, waking and sleeping on schedules
- Full Observability: Every LLM call, tool invocation, and decision is traced
Core Architecture
- Organization — your top-level account
- Product — one per application, holds shared configuration
- LLM Provider Keys (OpenAI, Anthropic)
- System Prompt
- Adapters (tool integrations)
- Agent 1, Agent 2, … — deployed instances, each with its own Memory, State, and Tools
- Product — one per application, holds shared configuration
Key Concepts
- Product — Your application’s configuration template: system prompt, LLM keys, adapters. Configure it once in the portal.
- Agent — A deployed instance of your product with its own memory, contacts, and state. Create one per end-user.
- Adapter — An integration module (SMS, Email, CRM, etc.) that gives agents tools.
- Tool — A callable function an agent can invoke, either built-in or a webhook to your API.
Products
Configure LLM keys, system prompts, and adapters in the portal.
Agents
Deploy autonomous AI instances with their own memory and state.
Adapters
Built-in integrations for SMS, email, calendars, and more.
Custom Adapters
Build your own adapters to connect agents to any API.
Memory
Hierarchical summarization that maintains context across sessions.
Tracing
Full observability into every LLM call, tool execution, and decision.
Built-in Adapters
Bedrock includes these default integrations:| Adapter | Description |
|---|---|
| Contacts | Store and manage contact information |
| SMS | Send and receive text messages via Twilio |
| MMS | Send and receive iMessage/RCS via Linq |
| Surge | Send and receive SMS via Surge |
| Send and receive emails via AgentMail | |
| Gmail | Read/send from a user’s Gmail via OAuth |
| Google Calendar | Manage events on a user’s Google Calendar |
| Notifications | Internal notification/reminder system |
| Projects | Hierarchical project tracking with sub-projects |
| Documents | Store text documents for agent reference |
| Computer | Cloud VM sandbox for shell commands and files |
| Browser | Asynchronous browser automation for web tasks |
Custom Integrations
Build your own adapters to connect agents to any system:- Create an adapter — a named container for related tools
- Add webhook tools — each tool POSTs to your API when called
- Verify requests — check the
X-Agent-Secretheader to authenticate - Return data — your JSON response becomes the tool result the agent sees
How Agents Run
- Wake agent (API call or scheduled)
- Load memory context
- Build prompt with tools
- Call LLM (OpenAI/Anthropic)
- Execute tool calls
- Log to memory
- Repeat until agent sleeps
Use Your Own LLM Keys
Bedrock uses your LLM provider accounts:- You control costs directly with OpenAI/Anthropic
- Use any model available on your account
- Prompt caching with Claude reduces costs significantly
Quick Links
Quickstart
Set up a product and deploy your first agent
Custom Adapters
Connect agents to your own APIs
API Reference
Full endpoint documentation
Authentication
API key setup and usage