> ## Documentation Index > Fetch the complete documentation index at: https://docs.cloudhumans.com/llms.txt > Use this file to discover all available pages before exploring further. # Confirm an agent create > Second step of a safe create. Send ONLY the confirmationId returned by proposeAssistantCreate — the server creates the assistant from the proposal it stored; any other body field is ignored. Each proposal is confirmed ONCE — the confirmationId is consumed as soon as the confirm's checks pass, immediately before the assistant is created; to create another agent, run proposeAssistantCreate again and confirm the new confirmationId. If a confirm errors or times out after the proposal was spent, check listAssistants for the draft FIRST — the creation may have completed — before proposing again. PROPOSAL_NOT_FOUND (404) means the proposal expired or was already confirmed: re-run proposeAssistantCreate with the same body and confirm again with the new confirmationId. New assistants are created as DRAFTS; a human reviews and publishes them in the app. Second step of the propose → confirm flow. See [Propose an agent edit](/api-reference/claudia/endpoints/propose-assistant-edits) for the full walkthrough. Each confirmationId from [proposeAssistantCreate](/api-reference/claudia/endpoints/propose-assistant-create) is single-use: it is consumed as soon as the confirm's checks pass, right before the agent is created — even if the creation itself then fails — so a retry needs a fresh propose call. If the confirm errored or timed out, list the agents first: the creation may have completed, and re-proposing blindly would duplicate the draft. ## OpenAPI ````yaml api-reference/specs/claudia/v1.json POST /v1/tenants/{tenant}/assistants/confirm-create openapi: 3.0.1 info: title: Claudia API version: 1.0.0 servers: - url: https://api.cloudhumans.com/claudia description: Production - url: https://api.cloudhumans.com/claudia/staging description: Staging security: - bearerAuth: [] tags: - name: MCP Servers description: >- The MCP servers your agents can call tools on. Registering one here is what makes its tools selectable in an agent; the credentials it needs are stored encrypted and never read back. - name: Knowledge Base Content description: Read, search and edit the content that answers your customers. - name: Content Quality description: Rewrites proposed for content that is answering your customers badly. - name: Playground description: >- Talk to one of your agents as if you were a customer, without touching a real conversation. - name: Project Settings description: >- Read and change how a ClaudIA project behaves — the settings screens of the ClaudIA app, as an API. - name: Content Improvements description: Answers Claudia proposes for questions your content does not cover yet. - name: Knowledge Bases description: The knowledge bases your account can manage. - name: Content Sources description: The sites Claudia crawls to keep a knowledge base in sync. - name: Agents description: >- The AI agents (assistants) configured for your tenant: the orchestrator (supervisor) and its specialists (react). Reads answer the same passthrough shape the platform stores; creates land as DRAFTS a human reviews and publishes in the app. - name: Agent Tools description: >- The tool catalog your agents can be given, aggregated across every MCP server registered for the tenant. This is the same catalog an assistant's mcp_servers[].tools whitelist is validated against. - name: Conversations description: >- Read access to a conversation's lean investigation summary — messages, status and resolution — and the execution trace behind one of its processed messages, without the internal processing state the hub UI's full read carries. paths: /v1/tenants/{tenant}/assistants/confirm-create: post: tags: - Agents summary: Confirm a proposed create (create the assistant) description: >- Second step of a safe create. Send ONLY the confirmationId returned by proposeAssistantCreate — the server creates the assistant from the proposal it stored; any other body field is ignored. Each proposal is confirmed ONCE — the confirmationId is consumed as soon as the confirm's checks pass, immediately before the assistant is created; to create another agent, run proposeAssistantCreate again and confirm the new confirmationId. If a confirm errors or times out after the proposal was spent, check listAssistants for the draft FIRST — the creation may have completed — before proposing again. PROPOSAL_NOT_FOUND (404) means the proposal expired or was already confirmed: re-run proposeAssistantCreate with the same body and confirm again with the new confirmationId. New assistants are created as DRAFTS; a human reviews and publishes them in the app. operationId: confirmAssistantCreate parameters: - name: tenant in: path description: >- Tenant whose agents you are managing. Discover the tenants your credentials cover with `listMyClaudiaProjects`. A tenant your credentials do not cover is indistinguishable from one that does not exist. required: true schema: type: string requestBody: description: Just the confirmationId returned by proposeAssistantCreate. content: application/json: schema: $ref: '#/components/schemas/ConfirmAssistantCreateRequest' required: true responses: '201': description: >- The agent as created — a draft, in the same passthrough shape getAssistant returns. A free-form object: read the keys rather than assuming a shape. content: application/json: schema: type: object additionalProperties: true description: >- Free-form object: the agent's stored configuration, in whatever shape the live config schema for its deployment accepts. Read the keys you need; do not assume a fixed set. '400': description: confirmationId is missing from the body. content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Missing, expired or invalid credentials. '403': description: The credentials hold no account allowed to manage this content. content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: >- Either PROPOSAL_NOT_FOUND (the confirmationId has no stored proposal — it may have expired, or it was already confirmed) or the tenant this token cannot reach. content: application/json: schema: $ref: '#/components/schemas/Error' '422': description: >- CONFIRMATION_MISMATCH (the stored proposal no longer matches this confirmationId — re-propose), `metadata.productionAssistantId` no longer names a published agent of the same `deployment` on this tenant (re-verified at confirm time), or a policy violation on the stored proposal. content: application/json: schema: $ref: '#/components/schemas/Error' '429': description: Rate limit applied by the API gateway. Back off and retry. components: schemas: ConfirmAssistantCreateRequest: type: object required: - confirmationId properties: confirmationId: type: string description: >- Confirmation token returned by propose-create; the only field this endpoint reads. The server creates the assistant from the proposal it stored for this token. Omitting it answers 400. description: >- The confirmationId returned by propose-create — the only field this endpoint reads. Error: required: - error type: object properties: error: type: string description: What went wrong. example: 'Forbidden: token holds no claim for the requested account' description: Something the caller needs to fix. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ````