Tools for someone else’s AI
Bind capabilities to an MCP gateway and hand the URL to a client. Their AI does the reasoning; you control the surface, the credentials, and the policy. Composes from: an MCP gateway, built-in capabilities, connectors, one of the auth modes. The constraint: a gateway is an unattended surface. A call that would pause for human approval is denied instead. Decide up front which tools are safe to run without a person, and put everything else behind an agent.A support agent grounded in your documentation
Attach a knowledge base to an agent so relevant passages are retrieved on every turn, and bind HTTP Client or a connector for live lookups. Composes from: an agent, attached knowledge bases, Knowledge Retrieval or a connector, Supervised autonomy. The constraint: automatic retrieval costs tokens on every turn. Attach only the base that is always relevant and bind the Knowledge Retrieval capability for the rest, so the agent searches the others when it decides to.Proprietary logic as a tool
Compile your rules to a WebAssembly component and upload it. The agent calls it like any other tool; the logic never leaves the sandbox, and the sandbox has only the network hosts you allowlisted. Composes from: a plugin, declared credentials, a host allowlist. The constraint: every plugin tool is classifiedAct tier kind-wide — the platform cannot see inside your component to tell a read from a write. Under Supervised autonomy your plugin’s calls pause until you auto-approve them.
An agent reachable from chat
Connect Telegram, Slack, or SMS and people talk to the agent where they already are. Composes from: an agent, a channel, linked platform identities for the people who should be recognized. The constraint: messaging channels are unattended surfaces. Approval prompts do not render there — a call that would pause is denied. Also: a channel is created disabled, and enabling it is a separate step — saving credentials is not enough. Re-entering credentials disables it again.A process that must not lose its place
Model the sequence as a Workflow Program. The run records effects and waits, so recovery can replay the Program against durable outcomes instead of blindly dispatching completed work again. Composes from: Program source, bound Agents and capabilities, an explicit approval wait, and a signed callback wait. The constraint: approval, signal, and callback waits have no built-in timeout. They remain parked until resolved or the run is canceled. The current Program surface also has no general parallel-join helper; awaited calls execute in source order.Aggregating several APIs behind one surface
Point connectors at each system and bind them all to one gateway or agent. Callers see one tool list. Composes from: REST or MCP connectors, OpenAPI import, one gateway. The constraint: a large tool surface degrades tool choice. At 30 or more bound tools the platform’s default presentation switches to discovery meta-tools rather than listing everything — expect an extra round trip, and expect tool descriptions to carry more weight than they did at ten tools.Delegating to specialists
A coordinator agent with no capabilities of its own, delegating to children that each own a narrow surface. Composes from: an agent with sub-agents,delegate_agent.
The constraint: a child inherits the parent’s pinned curated memories but starts with an empty conversation and no summary. Everything the child needs to know has to be in the delegation request. Delegation depth is capped at 3 levels by default.
An interactive surface the agent draws
An agent that emits progress bars, tables, forms, and approval cards instead of describing them in prose. Composes from: an agent with A2UI enabled, the Noorle Extended catalog, a client that renders it. The constraint: the client has to render it. The Portal Playground does; an MCP client does not, and an A2A caller only receives UI if it negotiated the extension.Where to start
Agent plus built-ins
Eleven capabilities are already in your account. Most first agents need nothing else.
Gateway for external clients
When the reasoning happens somewhere else and you are supplying the tools.
Connector before plugin
If the system already has an API, that is configuration rather than code.
Workflow when order matters
Fixed sequence, durable progress, a human in the middle.
Ready to build? Head to the Run tab.