> ## 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. ## OpenAPI ````yaml /en/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. One long-lived host runs on your machine and serves this API over a Unix socket in your Narya home. Narya creates the socket owner-only, and file permissions are the whole authorization. There is no password, no token and no TLS. The terminal client and the one-shot command that Lerian ships drive this API, and a client you write drives the same one. Results never arrive on the response of the request that caused them. 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, message, and fields on 422. Codes are NRY- followed by four digits. A paged list answers items, limit and a nextCursor when more remains. Cursors are opaque. servers: [] security: [] 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: 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: 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. 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. operationId: answerQuestion requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/QuestionAnswerRequest' responses: '204': description: >- Answered. The tool call that raised it is running again, and its close arrives as tool-call-finished for the call question-asked named. '400': $ref: '#/components/responses/BadRequest' '404': $ref: '#/components/responses/NotFound' '409': $ref: '#/components/responses/Conflict' '500': $ref: '#/components/responses/InternalServerError' 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. 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. fields appears only on 422 validation errors, mapping each offending property to its problem. 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. Present on 422 only. 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' InternalServerError: description: The host failed — including a store that refuses writes (NRY-0012). content: application/json: schema: $ref: '#/components/schemas/Error' ````