Jalebi is the platform that sits between “we built an agent” and “we trust it with production traffic, real cost controls, and our compliance requirements.” No AI infrastructure team required.
Built on Amazon Bedrock AgentCore.
What happens when it goes from 10 users to 10,000 — who's paying for it, and does your infrastructure survive without a rebuild or a runaway bill?
A six-level quota chain — org, workspace, user, API key, customer, agent — caps spend and attributes cost automatically. Give finance a budget and marketing a separate one; both get warned before they hit it. Most agent-building tools have no concept of this.
Every conversation runs in its own isolated instance on serverless infrastructure. When one account's limits become the ceiling, workspaces already span multiple accounts — a real design iteration we went through ourselves before any customer could hit that wall.
Deploy entirely inside your own cloud account. Zero data leaves your network. Same console, same features, same guardrails — just running where your compliance team can see it.
When an agent writes to your CRM or sends an email, the system on the other end should know whether a person did it or an agent did it for them — and which person. Most agent tools send one service account and the trail ends there. We're building the delegation chain in, so your audit log still names a human.
Two ways to take the reply: wait for the finished answer, or watch the agent work a step at a time. Same agent either way, and nothing is redeployed to switch.
Post your message. Take the reply as JSON when it is ready.
curl -X POST \
https://api.jalebi.chat/agents/agt_xyz/invoke \
-H "Authorization: Bearer jc_sk_..." \
-H "X-Jalebi-User-Id: user_42" \
-H 'X-Jalebi-Tags: {"dept":"support"}' \
-d '{
"message": "Where is my order?",
"sessionId": "ses_abc",
"context": { "account_tier": "premium" }
}'{
"success": true,
"data": {
"response": "Your order shipped Tuesday.",
"sessionId": "ses_abc",
"metadata": {
"model": "mistral.ministral-3-14b-instruct",
"latency": 1430
}
}
}The agent still looked up the order and still kept the session — you just did not have to watch it happen.
Open a stream. Watch each tool call and word as it lands.
# 1 authorize→ POST /agents/agt_xyz/connect?protocol=agui← { "endpoint": "https://bedrock-agentcore.us-west-2...", "paths": { "ws": "/ws", "sse": "/invocations" }, "token": "eyJhbGci...", "expiresIn": 900 }# 2 open one socket and keep it→ GET <endpoint>/ws Upgrade: websocket Bearer eyJ...← {"type":"connected","sessionId":"ses_abc", "clientsInSession":1}# 3 ask→ {"threadId":"ses_abc","messages":[ {"role":"user","content":"Where is my order?"}]}← {"type":"RUN_STARTED","threadId":"ses_abc"}← {"type":"TOOL_CALL_START","toolName":"get_order"}← {"type":"TOOL_CALL_RESULT","result":{"eta":"Tue"}}← {"type":"TEXT_MESSAGE_CONTENT","delta":"Your order "}← {"type":"TEXT_MESSAGE_CONTENT","delta":"shipped Tuesday."}← {"type":"RUN_FINISHED","threadId":"ses_abc"}# 4 follow up on the same socket→ {"threadId":"ses_abc","messages":[ {"role":"user","content":"Send it to my office"}]}← {"type":"RUN_STARTED","threadId":"ses_abc"}← {"type":"TOOL_CALL_START","toolName":"update_address"}← {"type":"TEXT_MESSAGE_CONTENT","delta":"Done - at work"}← {"type":"RUN_FINISHED","threadId":"ses_abc"}One socket, many turns — the follow-up lands in the same thread, so the agent already knows which order you mean. Every client in that session receives the same frames, which is how spectators watch one run live. Want the simple path instead? POST the payload to sse and take one streamed response.
Both ways carry the same three things, so per-user quotas and chargeback by tag do not change because you chose to stream. Only the field names differ: a header when you post a message, a property on the stream when you open one.
X-Jalebi-User-IdforwardedProps.userIdWho it is for. Drives per-user quotas and puts a name on the cost.
X-Jalebi-TagsforwardedProps.tagsHow to group it. Chargeback by department, project, or customer.
contextcontext[]What the agent should know. Injected at runtime, never in your prompt.
The same agent is reachable over MCP for IDEs like Claude Desktop and Cursor, and over A2A for other agents. One deployment, no adapters needed.
Every agent Jalebi deploys is a real Amazon Bedrock AgentCore resource in your own AWS environment. We didn't build a new runtime to bet your business on — we built the console, the governance, and the guardrails that AgentCore itself doesn't provide out of the box.
Think Vercel or Shopify to AWS's raw infrastructure: same underlying platform, but with the operational layer a business actually needs to run it — without hiring a team to build that layer first.
See the full platform →Jalebi is early, and we would rather be precise about that than impressive about it. The platform is built — the quota chain, multi-account workspaces, and BYOC deployment above are implemented and covered by several thousand tests. What they are not yet is battle-tested by production traffic. Our own first app, live cricket scoring for a club that is ready to use it, is the next thing we put on the platform, specifically so we are not asking you to be our first production customer. If you want a platform whose team will tell you plainly what is proven and what is merely written, we'd like to talk.
Your agents. Your data. Your rules. Zero infrastructure to manage.
jalebi.chat — AI agent platform for teams that need to trust what they ship