For developers

Build the experience. Define what the agent can do.

Connect muwkl agents to your application with clear APIs, scoped permissions and state you can inspect. Start with a request. Follow what happens next.

Follow what actually happened.

Read the turn, its outputs and its operations. Show the recorded result, and handle unavailable or unknown states explicitly.

Read the reference
Your application → muwklServer side
Request
GET /v1/conversations/{id}/turns

// Inspect the recorded turn.
// Then read its outputs and operations.

GET /v1/conversations/{id}/turns/{turn_id}
GET /v1/conversations/{id}/turns/{turn_id}/outputs
ResponseRecorded state
admitted → sealed → finalized
              ↘ abandoned

Inspect output availability.
Read the operation’s recorded state.
Reconcile an unknown outcome.

Inspect before confirming

Abbreviated examples. Replace placeholders during setup.

Every step should be understandable.

Explicit permissions

Workspace keys with read, write and converse scopes. Give an integration only the access it needs.

Configuration you can review

Editable drafts and immutable published revisions. Validate changes before publishing them.

Inspectable outcomes

Separate message admission from processing and delivery. Read the recorded state before showing a confirmation.

From understanding to your first request.

Examples, fields, permissions and error behavior in one place. Use the enabled development environment for your workspace.