Build with muwkl
Agents with a defined job. APIs with explicit state. A clear place to start.
One workspace. Clear boundaries.
A workspace contains your agents and credentials. Each agent has an editable draft and immutable published revisions. Conversations belong to an agent; messages enter a conversation, while turns record the work that follows.
Your business systems remain the authority for their records. Connect the specific capabilities an agent needs and decide which operations it may perform.
Development access
This reference describes the current development API contracts. Use the base URL and workspace access supplied during setup. Examples are for your server; they do not call a public live API from this documentation.
Runtime, channel and integration availability depend on your environment. An accepted message is not evidence that an action completed or that a customer received a reply.
Core resources
| Resource | Purpose |
|---|---|
| Agent | Role, configuration and lifecycle |
| Draft / Revision | Editable configuration / an immutable published snapshot |
| Conversation | The container for an agent’s exchange with a subject |
| Message | An incoming request with a stable client identity |
| Collection / Document | Reviewed knowledge, document versions and ingestion jobs |
| Provider / Tool | A connected system and its declared capabilities |
| Turn / Operation | Processing state and the outcome of a particular operation |
Choose your starting point
Start with Quickstart to make a read request. Use Authentication to scope the credential, Agents to manage configuration, and Conversations to understand message admission and inspect results.
Need a hand? Get in touch