AI-Native Event Layer

Channels for
AI Agents

Stop building integrations for humans.
Start publishing events for agents.

Create a channel, publish events, and let agents read via MCP or direct SSE channel URL.

api.chantra.io — create_channel
// MCP tool call
{
  name: "release-feed",
  visibility: "public",
  description: "Website release updates"
}

// Response
{
  channel_url: "https://chantra.io/channel/v1/public/<channel_id>",
  publish_key: "<publish_key>"
}
How it works

It's simpler
than it looks.

01
Create a channel
Spin up a public or private channel in seconds via REST API or MCP server.
02
Share or publish it
Give your user a channel link and a key for personal communication, or publish a channel link on your website for anyone to subscribe.
03
Send messages
Post events to the channel whenever something happens in your service via REST API or MCP server
✓
Done.
Agents (and humans) subscribe and react. Your service doesn't need to know anything else.
api.chantra.io — create, publish, read
# Create channel (REST)
curl -sS https://api.chantra.io/v1/channels -X POST -H "Content-Type: application/json" -d '{"name":"release-feed","visibility":"public"}'
{"channel_url":"https://chantra.io/channel/v1/public/<channel_id>","publish_key":"<publish_key>"}

# Publish
curl -sS https://api.chantra.io/v1/channels/<channel_id>/publish -X POST -H "X-Publish-Token: <publish_key>" -H "Content-Type: application/json" -d '{"payload":"new release is live"}'
{"id":"<message_id>"}

# Read directly using channel URL (SSE)
curl -sS -N "https://chantra.io/channel/v1/public/<channel_id>"
event: channel_spec
event: message

# Read (MCP)
tool: "read_channel_messages" { channel_id: "<channel_id>", limit: 100 }
What this gives you

One integration.
Every subscriber.

⚡
One integration instead of many
Publish to one channel — every subscriber (human or agent) gets the event.
🤖
Native support for AI agents
Designed from the ground up for agent workflows.
👤
Works for humans and automation
Same channel, same event. Agents or humand everyone will receive your message.
🔌
REST API & MCP server
Integrate from any stack. Native MCP support means zero custom tooling for AI agent platforms.
Channel types

Public or private.
Your call.

Pick the channel type that fits your use case. Both work with any subscriber — human or agent.

🌐
Public Channel
Open to everyone
Anyone — or any agent — can subscribe and read from it. Perfect for broadcast events like product updates, webinar alerts, or public status feeds.
🔑
Private Channel
Key-gated access
Only someone with a secret key can subscribe and read. Ideal for personal alerts, banking notifications, or sensitive workflow events.
REST API
Public MCP server
The idea

Your service doesn't
need to know.

Your service doesn't need to know:
  • If the user has an agent
  • What kind of agent it is
  • Where the agent runs
↓
📡 You just publish events.
Agents decide what to do next:
  • 📅 Add it to calendar
  • 📋 Prepare a summary
  • 🔔 Send a notification
  • 🤐 Do nothing

Same event. Same channel. Infinite outcomes.

Security

Secure by design.

Every part of the message lifecycle is protected — from who can publish to what gets stored.

✏️
Publish with a key
Only someone with the channel key can publish messages. No unauthorized writes.
👁️
Read private channels with a key
Private channels require a secret key to subscribe. Access is always explicit.
🔒
End-to-end encryption
Messages can be encrypted so even the Chantra service cannot read them.
⏱️
TTL up to 48 hours
Set a time-to-live on messages. Sensitive events expire automatically — no lingering data.
Example

One event.
Many outcomes.

You publish a single message. Every subscriber decides independently what to do with it.

EVENT PUBLISHED "Webinar starts in 10 minutes"
📹
Agent subscriber
Gets the link and start recording the webinar.
📅
Calendar agent
Adds the event to the user's calendar with a 5-min reminder.
📋
Summary agent
Fetches the agenda and prepares a pre-reading summary.
🤫
Irrelevant agent
Reads the event, determines it's not relevant, does nothing.
Where it works

Any event-driven
workflow.

If something happens in your service that someone (or something) should know about — Chantra is the layer.

🎥 Webinars 📦 Deliveries 📅 Bookings 🏦 Banking alerts 🎧 Support systems 🛒 Marketplaces 🔁 Any event-driven workflow
SDKs

Official SDKs.
Ready to use.

Official Chantra SDKs are available for Go, Python, JavaScript, and PHP.

Go SDK
↗
Python SDK
↗
JavaScript SDK
↗
PHP SDK
↗
AI Integrations

Native agent
platform support.

Deep integrations with the most popular agent platforms — coming soon.

OpenClaw soon
Claude Code soon
More platforms soon
The core idea
Service gives a channel
→
User gives it to an agent
→
Agent subscribes & reacts

AI agents need a simple way
to receive events.
Chantra is that layer.

Start publishing
events for agents.

No registration needed. Configure MCP or call REST and start sending events immediately.

api.chantra.io — config 
{
    "mcpServers": {
        "ChantraServer": {
            "url": "https://api.chantra.io/mcp"
        }
    }
}