> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Answer a question the agent asked > Records what the person chose for one `ask_user` call and releases the tool call that has been blocked on it. One answer per question, in the order the questions were asked. The indices are into the option list exactly as question-asked sent it — the engine ordered those options, so a client that reordered them would send back the wrong choice. Answering a question that is already answered, or one a host closed when its turn was interrupted, is a conflict: the tool it was blocking is no longer waiting. A question is not a permission and this is not decidePermission: no rule can be written about a question, nothing is remembered, and the decision audit never carries one. On a product session nothing is blocked: the `ask_user` call finished when it asked and its turn ended there, and the question stands, a restart included, until it is answered here or the person sends a message on its lane instead, which closes it. Answering it starts the next turn with the answer as the person's message, called as this request's person; the `204` is that turn accepted, and a refusal to admit it answers as createMessage would. The message rides the question's id as its idempotency key, so answering again after a refusal, or a second press, sends the recorded answer once rather than answering `409`. A refusal that leaves no message behind reopens the question and answers `409` `NRY-0032` instead of the message road's own status: the answer was not delivered and the question is pending again, which a client must not read as the question being settled. ## OpenAPI ````yaml /pt/openapi/v3-current/narya.yaml post /v1/questions/{questionId}/answer openapi: 3.1.0 info: title: Narya Host API version: 1.0.0 description: >- The contract between the Narya host and every client. On your own machine, one long-lived host serves this API over a Unix socket in your Narya home. The terminal client and the one-shot command that Lerian ships drive this API, and a client you write drives the same one. Requests authenticate with a bearer token issued by the identity provider the host is configured with. On your own machine, the host also accepts a request with no token from your own operating system user. Once signed-in work has claimed the home for an organization, it does so only while this machine is signed in to that organization. Such a request gets 401 with NRY-0011 on work that reaches your organization beyond the machine. An operation that declares another security scheme also accepts that credential. Any other request without a valid credential gets 401 with NRY-0011. A caller whose role lacks the permission an operation needs gets 403 with NRY-0028. Submitting a message returns 202 with a turn id. Everything the turn produces streams over GET /v1/events as server-sent events with a typed envelope, and a stream resumes from a Last-Event-ID header. One error envelope: code, title and message. Codes are NRY- followed by four digits. Cursors are opaque. servers: [] security: - bearerAuth: [] tags: - name: host description: The host process itself — version, uptime, mode, store. - name: sessions description: Durable conversation containers. Archive, never destroy. - name: messages description: Submitting work into a session and interrupting it. - name: events description: The server-sent event stream every client consumes. - name: lanes description: Parallel tracks inside a session — main, subagent, side. - name: agents description: Named recipes — instructions, tools, model, policy. Read-only in v1. - name: ladder description: >- What a person can type: the skills and command files in force for one repository, and expanding one into text. Five origins merged, nearest winning a name, the repository's own rungs gated on trust. - name: permissions description: Pending permission asks, decisions, and the decision audit. - name: intercom description: Sessions on one machine finding and messaging each other. - name: packages description: The one thing a user installs — resources, Go code, or both. - name: extensions description: >- Host-side extensions and the operations each exposes over the wire. This is the generic lane a host extension uses to serve its own client half (a TUI component, a web panel) or any API-only consumer, without adding routes to this contract. - name: workflows description: Deterministic multi-agent orchestration runs. - name: providers description: Model suppliers, their auth state, and the model catalogue. - name: monitors description: >- Long-running watchers a session keeps beside its conversation — a test runner in watch mode, a build, a log being followed. Started by the model or by the person, always listed, always killable. - name: records description: The queryable local record of everything that happened. - name: environments description: >- Where a session's code lives and its commands run — this machine, or a container narya operates. A session that names none runs here. - name: schedules description: >- Work the host's own clock starts with nobody present — a repository, a prompt, a rule and what one fire may spend. Cancel, never destroy. - name: sharing description: >- Publishing a session from a developer's own home to the organisation's, and what is held back before a byte leaves the machine. - name: refinements description: >- What this owner has taught narya and allowed it to keep — distilled facts, and the skills, agents and commands the model wrote for itself. Propose, read, consent, roll back. Nothing here fires until a person answers. - name: platform description: >- Calls Lerian's control plane made to a home it hosts, as this home recorded them. paths: /v1/questions/{questionId}/answer: parameters: - $ref: '#/components/parameters/QuestionIdParam' post: tags: - permissions summary: Answer a question the agent asked description: >- Records what the person chose for one `ask_user` call and releases the tool call that has been blocked on it. One answer per question, in the order the questions were asked. The indices are into the option list exactly as question-asked sent it — the engine ordered those options, so a client that reordered them would send back the wrong choice. Answering a question that is already answered, or one a host closed when its turn was interrupted, is a conflict: the tool it was blocking is no longer waiting. A question is not a permission and this is not decidePermission: no rule can be written about a question, nothing is remembered, and the decision audit never carries one. On a product session nothing is blocked: the `ask_user` call finished when it asked and its turn ended there, and the question stands, a restart included, until it is answered here or the person sends a message on its lane instead, which closes it. Answering it starts the next turn with the answer as the person's message, called as this request's person; the `204` is that turn accepted, and a refusal to admit it answers as createMessage would. The message rides the question's id as its idempotency key, so answering again after a refusal, or a second press, sends the recorded answer once rather than answering `409`. A refusal that leaves no message behind reopens the question and answers `409` `NRY-0032` instead of the message road's own status: the answer was not delivered and the question is pending again, which a client must not read as the question being settled. operationId: answerQuestion requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/QuestionAnswerRequest' responses: '204': description: >- Answered. On a session with a blocked tool call, that call is running again, and its close arrives as tool-call-finished for the call question-asked named. On a product session nothing was blocked: the answer is the person's message, and this `204` is the next turn accepted. '400': $ref: '#/components/responses/BadRequest' '404': $ref: '#/components/responses/NotFound' '409': $ref: '#/components/responses/Conflict' '413': $ref: '#/components/responses/RequestBodyTooLarge' '422': $ref: '#/components/responses/UnprocessableEntity' '500': $ref: '#/components/responses/InternalServerError' '503': $ref: '#/components/responses/ProductNotLoaded' components: parameters: QuestionIdParam: name: questionId in: path required: true description: The question's id, as question-asked announced it. schema: type: string format: uuid schemas: QuestionAnswerRequest: type: object description: >- One person's answer to every question of one `ask_user` call, in the order the questions were asked — position is the join, because a question carries no id of its own. required: - answers properties: answers: type: array description: One entry per question asked, in that order. minItems: 1 maxItems: 4 items: $ref: '#/components/schemas/QuestionAnswer' examples: - answers: - options: - 0 - options: - 2 text: Keep both and reconcile nightly. QuestionAnswer: type: object description: What the person chose for ONE question, by position in the asked list. required: - options properties: options: type: array description: >- The indices of the options chosen, into the option list exactly as the engine sent it. Several only when the question said `multiple`. Empty is "this one was not answered", which the agent is told rather than left to infer from a short list. items: type: integer minimum: 0 text: type: string description: >- What the person typed into the free-text row. It counts only when that row's index is among `options`; typed text with the row unchosen, and the row chosen with nothing typed, are both no answer at all. examples: - options: - 0 Error: type: object description: >- The single error envelope every operation returns. Codes are NRY- followed by four digits and are catalogued in the top-level x-error-catalog extension. required: - code - title - message properties: code: type: string pattern: ^NRY-[0-9]{4}$ description: Machine-readable error code from the NRY catalogue. title: type: string maxLength: 256 description: Short human-readable summary of the error class. message: type: string maxLength: 4096 description: Specific, actionable description of what went wrong. fields: type: object description: Per-field validation problems. additionalProperties: type: string examples: - code: NRY-0002 title: Session not found message: >- No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host. responses: BadRequest: description: Malformed request — invalid parameter, cursor, or JSON body. content: application/json: schema: $ref: '#/components/schemas/Error' NotFound: description: The addressed resource does not exist on this host. content: application/json: schema: $ref: '#/components/schemas/Error' Conflict: description: >- The resource's current state rejects the request — archived session, busy lane, slot conflict, failed build, already-final state. content: application/json: schema: $ref: '#/components/schemas/Error' RequestBodyTooLarge: description: >- The request body weighs more than this operation accepts (NRY-0024). The host holds one ceiling per operation and refuses at the door, in front of every handler: a body whose declared Content-Length is past the ceiling is refused before a byte of it is read, and a body that declares no length is read only as far as the ceiling and refused there. Nothing was read past that point and nothing was written. content: application/json: schema: $ref: '#/components/schemas/Error' UnprocessableEntity: description: The request was well-formed but failed validation. content: application/json: schema: $ref: '#/components/schemas/Error' InternalServerError: description: The host failed — including a store that refuses writes (NRY-0012). content: application/json: schema: $ref: '#/components/schemas/Error' ProductNotLoaded: description: >- A product session's product has no tools loaded on this home yet (NRY-0021): nothing was admitted, and sending it again does. content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- Enforced on every transport, with no exempt operation. A person's request must carry a JWT issued by the configured identity provider, which the host verifies itself against that issuer's key set: signature, issuer, expiry, and the person and organisation it names. Requests without a valid one receive 401 NRY-0011 — except a request with no token on a laptop's socket from the OS user the kernel names as the host's own, which is that machine's user. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.