Check an API build
writ_discovery_statusPoll a build's status from writ_website_to_api. Returns terminal state, escalations, and guidance needs, automatically following superseded builds.
Instructions
Poll a build started by writ_website_to_api. Terminal states are succeeded, failed and cancelled. RESTING state: needs_guidance — Writ's mechanical rungs are done and the build is YOURS to finish: it carries map (endpoints seen, specs, candidate functions) and you continue it with writ_website_to_api mode=guided build_id=. A rung the ladder replaced reports superseded=true with fallback_build_id; with wait=true this tool FOLLOWS that pointer for you and answers with the rung now running (followed_from lists the ids it walked; poll the returned build_id from then on). escalations lists every earlier rung with the real reason it handed over (robots.txt refused the crawl, no pages fetched, nothing matched the goal, no structured list...) — quote it when you explain why a browser was needed. On success it returns the workflow_id, the surfaces mapped, and verified — FALSE for a fast/browser map, whose functions are candidates until a real run proves them; say so when you report them. Run any function with writ_run_workflow (function_name), and fetch the generated API docs (OpenAPI 3, Markdown or a Postman collection, all pointing at the real Writ endpoint) from GET /api/v1/workflows/{workflow_id}/api-docs.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| wait | No | ONE held call (≤75s) that follows escalations to the newest rung and returns when that build is terminal or parked as needs_guidance — instead of polling. If still building at the ceiling, call again with wait=true and the build_id this answer carries. | |
| build_id | Yes | The build id from writ_website_to_api. | |
| timeout_seconds | No | Ceiling for wait=true (≤75). |