---
title: "Execute Route"
method: POST
path: "/execute"
---

# Execute Route

`POST /execute`

## Request

- Base URL: `https://mcp.physea.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://mcp.physea.ai/execute`
- Auth: none declared

C1 — CLICK-TO-EXECUTE ("we ask a question. Questions are solved. And I go
to execute... I could just click a thing and execute"). Body: {"record_id":
<yield record id>} OR {"question": <text resolving to a record>}.

Wraps the SAME execution path the MCP execute_algorithm verb uses
(execution.execute) to map the route; for records carrying an
execution_blueprint it runs motherboard/engine/spine.run_blueprint — the
real runtime, runnable-prefix semantics.

HONESTY: nothing fake-fires. steps[] reports exactly what happened:
"fired" (ran with a confirm), "blocked" (could not fire — the recruit
lane), "skipped" (not reached / mapped only). A record with no resolved
blueprint is MAPPED (skipped steps), never pretend-run. The engine being
unimportable is a 503, never a crash.

## Request body

- ExecuteRequest
  - `record_id` string, nullable
  - `question` string, nullable
  - `alt` boolean

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/physea/apis/liminality-router-service.md) · [All operations](https://skmtc.dev/physea/apis/liminality-router-service/llms.txt) · [OpenAPI document](https://skmtc.dev/physea/apis/liminality-router-service/revisions/5f60ddd97544?raw)