---
title: "Run Agent Definition"
method: POST
path: "/v1/agent-definitions/{def_id}/run"
---

# Run Agent Definition

`POST /v1/agent-definitions/{def_id}/run`

## Request

- Base URL: `https://api.app.membase.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.app.membase.ai/v1/agent-definitions/{def_id}/run`
- Auth: none declared

`wait: false` detaches the turn: the response is the running record and the caller
polls GET /v1/agent-runs/{run_id} to a terminal state — a turn outlives what proxies
in front of the API allow a single request to take.

`conversation_id` names the web conversation this turn continues, so the agent resumes
that session and no other. Without one the turn is said in the `web` venue's own
session — this route IS the web surface. Telegram, schedules
and MCP clients each speak in their own venue and never through here.

## Path parameters

- `def_id` string, required

## Request body

- object

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error
- `default`: Error envelope (ADR 0027)

---

[API](https://skmtc.dev/membase/apis/membase-hosted-api.md) · [All operations](https://skmtc.dev/membase/apis/membase-hosted-api/llms.txt) · [OpenAPI document](https://skmtc.dev/membase/apis/membase-hosted-api/revisions/e0ac58cdb320?raw)