01 / IDENTITY
One identity layer
Give each agent a managed communication identity, with lifecycle and channel capabilities made explicit.
THE COMMUNICATION LAYER FOR AGENTS
Your agent.
Out in the world.
The infrastructure that gives the agents you already run a way to reach people. Identities, channels, routing, and delivery. One layer between your runtime and the conversation.
BUILT FOR DEVELOPERS · BRING YOUR OWN AGENT · NO MODEL LOCK-IN
YOUR RUNTIMEExisting agent
KEZRA LAYERRouting + events
CHANNELMessages
CHANNELVoice
one runtime · many communication surfaces
THE KEZRA LAYERIDENTITY→ROUTING→DELIVERY→OBSERVABILITY
01 — THE PLATFORM
Infrastructure for the part that happens after inference.
Your agent already thinks. Kezra gives it a dependable way to communicate, across the channels your product supports.
02 / TRANSPORT
Channels, not lock-in
Keep channel providers behind replaceable adapters. Your integration stays stable as the transport evolves.
03 / ROUTING
Every event has a path
Normalize inbound events, route them to the runtime you own, and preserve the context needed to respond.
04 / DELIVERY
Delivery you can inspect
Track accepted, queued, sent, delivered, and failed states instead of treating every API response as success.
05 / DEVELOPER TOOLS
Built around your stack
A direct API, SDKs, webhooks, and operational surfaces. No new agent framework to learn.
06 / CONTROL
Your agent stays yours
Bring your own model, prompts, memory, tools, and runtime. Kezra handles the communication boundary.
02 — THE DEVELOPER EXPERIENCE
Keep your runtime.
Change the reach.
Connect the agent you have with a clean communication API. Your code owns the intelligence. Kezra owns the delivery boundary.
Explore the technical directionYOUR APP / send.ts
EXAMPLE CONTRACT
// Send from the agent you already operate
const response = await kezra.messages.send({
identityId: "identity_...",
to: "+1 555 010 2048",
text: "Hey, what can I help with?",
});
if (response.status === "queued") {
// Kezra accepted the message for dispatch
}
API CONTRACT PREVIEW NOT A LIVE CONNECTION
03 — CHANNELS & CAPABILITIES
One API surface.
Honest capabilities.
A channel is only available when the identity is genuinely registered and the underlying provider supports it. No pretend checkmarks.
Transport is a capability, not a promise.
Each identity reports what it can actually do. No channel is inferred from a phone number alone.
TELECOM
SMS & voice
Provider-backed capabilities, subject to number availability and regional requirements.
MESSAGING
iMessage
Core research focus. Commercial provisioning remains gated on Apple's permission and a verified identity path.
ARCHITECTURE
More channels
Adapter-based by design. New transports can be added without changing your agent runtime.
Build the agent.
We'll handle the connection.
Bring your runtime. Keep your stack. Own the experience.