> ## Documentation Index > Fetch the complete documentation index at: https://docs.visiqlabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Regenerate an agent's AI name > Re-runs AI naming for one agent now, from its normalized event schemas. This is an explicit opt-in, so it takes AI ownership of the name even if a person set it. A naming failure returns 200 with `status: skipped`. Requires permission `allow_agents:update`. ## OpenAPI ````yaml /api-reference/openapi.yaml post /allow/agents/{id}/regenerate-naming openapi: 3.1.0 info: title: VisIQ Governance API version: 1.0.0 description: > The VisIQ platform API for governing agentic AI. One rule engine evaluates every governed agent event against your policies and returns a decision (permit, deny, approval-required, redact, mask, or escalate), records a cryptographically-verifiable audit trail, and governs agent-to-agent delegation. All requests are authenticated with a bearer API key presented as `Authorization: Bearer vq_prod_...`. Keys come in two audiences. Harness keys, minted under **Settings → Harness Keys**, are what your SDK or harness runs with; they reach only the operational surface (evaluate, rule bundles, telemetry, record ingestion). API keys for your own scripts and CI, minted under **Settings → API Keys**, reach the management API (rules, agents, settings, audit reads) through the permissions you grant each key. Dashboard sessions use your role's permissions. Decision vocabularies differ per facet. Action governance emits `permit | deny | approval_required | mask`. Retrieval governance emits `allow | deny | redact | escalate`. The unified `POST /evaluate` surface projects both into a single union vocabulary (`permit | deny | approval_required | redact | escalate | mask`). contact: name: VisIQ Labs url: https://docs.visiqlabs.com servers: - url: https://api.visiqlabs.com description: Production security: - bearerAuth: [] tags: - name: Evaluation description: Per-event governance decisions for action, retrieval, and delegation. - name: Action Rules description: Manage the rules that govern agent actions (writes/tool calls). - name: Retrieval Rules description: Manage the rules that govern retrieval and context exposure. - name: Unified Rules description: Operation-native rule management across both facets in one surface. - name: Rule Bundles description: Compiled, cacheable rule bundles the SDK runtime pulls per agent. - name: Agents description: Register and manage the agents whose events you govern. - name: Human-in-the-loop description: The approval queue for events that require a human decision. - name: Settings description: Per-account governance defaults. - name: Telemetry description: Decision and execution telemetry the SDK reports after evaluating locally. - name: Key lifecycle description: Operations an API key performs on itself. - name: Delegation description: Govern scoped agent-to-agent hand-offs with signed grant tokens. - name: Records description: Ingest, retrieve, finalize, and verify the tamper-evident audit trail. - name: Audit Log description: Versioned, paginated read APIs over recorded decisions and events. - name: Cognition description: >- Read captured Agent Cortex cognition sessions and beats (dedicated cognition:read scope). paths: /allow/agents/{id}/regenerate-naming: parameters: - $ref: '#/components/parameters/AgentUuid' post: tags: - Agents summary: Regenerate an agent's AI name description: > Re-runs AI naming for one agent now, from its normalized event schemas. This is an explicit opt-in, so it takes AI ownership of the name even if a person set it. A naming failure returns 200 with `status: skipped`. Requires permission `allow_agents:update`. operationId: regenerateAgentNaming responses: '200': description: The naming outcome. content: application/json: schema: $ref: '#/components/schemas/RegenerateNamingResult' example: status: updated title: Billing Copilot description: Answers billing questions and issues refunds. '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '503': $ref: '#/components/responses/ServiceUnavailable' security: - bearerAuth: [] components: parameters: AgentUuid: name: id in: path required: true schema: type: string format: uuid description: The agent's row UUID (not the human-readable agent_id). schemas: RegenerateNamingResult: type: object required: - status properties: status: type: string enum: - updated - unchanged - skipped reason: type: string title: type: string description: type: string Error: type: object required: - error - code description: > The standard error envelope. `code` is a stable, machine-readable snake_case identifier on every JSON error: the `error` value itself when that is already an identifier, otherwise a code derived from the HTTP status (see [REST conventions](/reference/rest-conventions)). `details` carries the validation issue list on 400s; authorization failures add fields such as `detail`, `requiredScopes`, or `requiredPermission`. properties: error: type: string code: type: string pattern: ^[a-z][a-z0-9_]*$ description: Stable machine-readable error code. Branch on this, not on `error`. detail: type: string details: type: array items: type: object additionalProperties: true additionalProperties: true responses: BadRequest: description: The request was malformed or failed validation. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Invalid request body code: invalid_request details: - path: - agent_id message: Required Unauthorized: description: Missing or invalid API key. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Unauthorized code: unauthenticated Forbidden: description: The key lacks the required permission or scope. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: insufficient_scope code: insufficient_scope detail: This API key is not authorized for the requested operation. NotFound: description: >- The requested resource does not exist (or is not visible to this account). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Rule not found code: not_found ServiceUnavailable: description: > A dependency needed to serve the request is unavailable, for example the API-key rate limiter (`rate_limiter_unavailable`) or, for a request that sent an idempotency key, the idempotency store. The request was not processed; retry after the `Retry-After` delay. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 0 content: application/json: schema: $ref: '#/components/schemas/Error' example: error: rate_limiter_unavailable code: rate_limiter_unavailable detail: Rate limiter unavailable, please retry. securitySchemes: bearerAuth: type: http scheme: bearer description: > A VisIQ API key presented as `Authorization: Bearer vq_prod_...`. Mint harness keys under **Settings → Harness Keys** and API keys under **Settings → API Keys** in the dashboard. ````