What you assemble
None of it requires writing an agent framework. Reach for code — a
plugin — only when the work is computation you
own and nothing you can configure covers it.
How people reach it
Every agent you publish gets an A2A endpoint atagent-{handle}.noorle.com. A
gateway you compose gets its own MCP origin at
mcp-{handle}.noorle.com, with its own authentication. An agent can also be
reached over Telegram, Slack, or SMS, and from the
Portal Playground.
The surface settles one thing worth deciding early: whether a call can pause and
wait for a person. On a gateway, and over Slack, Telegram, and SMS, there is no
channel to ask on, so a call that would have paused is denied instead.
Interactive clients and the Management API can answer. See
Autonomy and approvals.
What the platform is responsible for
Three things run underneath whatever you sell.Execution
The turn loop, conversation state, model routing and failover, and the
isolation each capability runs inside.
The admission decision
Every capability call is allowed, paused, or denied before it dispatches,
and every decision lands in an audit trail you can read and export.
The meter
One account, pay-as-you-go, with the balance and spending cap enforced at
the point a run allocates its budget.
Where the commercial line falls
The platform meters your account for what your agents consume. What you charge for the thing you sell is set outside the platform, by you.The meter
What gets recorded, where you read it, and what happens when the balance
runs out.
Built on Noorle
Your name on the door, and the platform named underneath it.