> ## Documentation Index > Fetch the complete documentation index at: https://docs.guidinghand.ai/llms.txt > Use this file to discover all available pages before exploring further. # Decide a request > Approves or denies one of the conversation’s `approval` items, or answers a `question` item, as your team (the API key, or the member signed in). Send exactly one of `approval`, `answer` or `action`. No agent is named, so it works in any conversation, including the one a task run without an agent gets. The decision reaches the task waiting on it, and a reply paused for it (`requires_action`) carries on by itself: follow it with GET /v1/responses/{response_id}, or decide with POST /v1/agents/{agent_id}/responses to stream it instead. Answers at once, with the request as decided. 409 with `code: already_decided` and `decided_by` when someone decided first, or `not_pending` when its task has ended, so nothing would act on it. ## OpenAPI ````yaml /api-reference/openapi.json post /v1/conversations/{conversation_id}/decisions openapi: 3.1.0 info: title: Eager API version: 1.0.0 description: >- Train AI agents like new hires: hand an agent your files and coach it, and it writes its own procedures and works in any software, even without an API. Talk to your agents one message at a time (POST /v1/agents/{agent_id}/responses): they answer from their files, procedures and your HTTP tools, and run tasks on their own cloud browser or your linked computers when an answer needs a website or a desktop app. Manage agents (versioned: save a draft, publish it), their procedures, browser and computers; follow conversations and tasks, answer approvals, and fetch history and recordings. Run tasks yourself on a session: a customer’s computer through an invite link, or a cloud browser. Test agents with evals: chat, browser and desktop test cases, run several times against your agents and judged on the answer. Every change is in the org’s audit log. servers: - url: https://guidinghand.ai description: Production - url: https://dev.guidinghand.ai description: Development (Stripe test mode) security: - bearerAuth: [] tags: - name: Agents - name: Agent files - name: Agent tools - name: Agent folders - name: Computers description: >- Computers your org links with the Eager app, and pools of them, for agents’ desktop tasks. Attach them to an agent in its `resources.computers`. - name: Phone numbers description: >- Bring your own Twilio numbers: connect the account, add its numbers, and pick the agent that answers each. Calls are answered by the agent's published version. - name: Sessions - name: Tasks - name: Webhooks - name: Audit log - name: Test cases - name: Test sets - name: Test runs - name: Start states - name: Runners - name: Responses description: >- Talk to an agent: each call is one turn of a conversation. The agent answers with its files, procedures and tools (and, with Run code, its own sandbox), asks for details with forms, and runs browser and desktop tasks when an answer needs a website or a desktop app. - name: Conversations description: >- The history of each conversation: messages, tool calls and the tasks the agent started, in order. - name: Uploads description: >- Files for conversations: attach them to a message, and download what the agent’s code made. Kept as long as their conversation. - name: Procedures description: >- An agent’s playbooks: when to use each and its steps. The agent finds and follows them; ones it writes from a first run are marked written_by: agent. - name: Categories description: The kinds of request an org’s procedures and test cases are sorted into. - name: Escalations description: >- What needs your team: an approval only the team can give or a question only it can answer, in a real conversation; a procedure run that failed; and one that worked another way, with the procedure rewritten to match (a proposed change). Test chats never escalate; evals do, without webhooks. - name: Schedules description: >- Run an agent’s procedure on a cron expression, in a time zone, with the inputs it needs. Each run is a conversation of its own with nobody in it (`channel` `schedule` in its variables): the procedure’s steps without AI run outright when it has them, else the model follows it to its end. Its record says how it ended, what the agent said last and what it cost; the team hears by webhook (`schedule.run_completed`, `schedule.run_failed`), email and Slack or Teams, as the schedule says. paths: /v1/conversations/{conversation_id}/decisions: parameters: - name: conversation_id in: path required: true description: The conversation’s id. schema: type: string post: tags: - Conversations summary: Decide a request description: >- Approves or denies one of the conversation’s `approval` items, or answers a `question` item, as your team (the API key, or the member signed in). Send exactly one of `approval`, `answer` or `action`. No agent is named, so it works in any conversation, including the one a task run without an agent gets. The decision reaches the task waiting on it, and a reply paused for it (`requires_action`) carries on by itself: follow it with GET /v1/responses/{response_id}, or decide with POST /v1/agents/{agent_id}/responses to stream it instead. Answers at once, with the request as decided. 409 with `code: already_decided` and `decided_by` when someone decided first, or `not_pending` when its task has ended, so nothing would act on it. operationId: decideInConversation requestBody: required: true content: application/json: schema: type: object description: Exactly one of `approval`, `answer` or `action`. properties: approval: type: object description: >- Approves or denies an `approval` item of the conversation (its `approval_id`). required: - approval_id - decision properties: approval_id: type: string decision: type: string enum: - approve - deny note: type: string maxLength: 500 description: 'For the agent: why, or what to do instead.' answer: type: object description: >- Answers a `question` item of the conversation (its `question_id`). required: - question_id - answer properties: question_id: type: string answer: type: string maxLength: 4000 action: type: object description: >- An A2UI action on a request’s surface (the item’s `surface_id`), as a renderer sends it (or wrapped as `{ version: "v0.9", action }`): on an `approval` item’s, `name` is `approve` or `deny` (and `context.note`, if any, the note); on a `question` item’s, its form’s `submit` (`context: { answer: ["