> ## Documentation Index > Fetch the complete documentation index at: https://docs.near.ai/llms.txt > Use this file to discover all available pages before exploring further. # Create API key for workspace > Creates a new API key for a workspace. Note: The key may take up to 10 seconds to become active for authentication due to internal caching. ## OpenAPI ````yaml /api-reference/openapi.json post /v1/workspaces/{workspace_id}/api-keys openapi: 3.1.0 info: title: NEAR AI Cloud API description: >- NEAR AI Cloud API for private AI model inference and organization administration. contact: name: NEAR AI Team email: support@near.ai license: name: MIT version: 1.0.0 servers: - url: https://cloud-api.near.ai description: NEAR AI Cloud security: - session_token: [] - api_key: [] tags: - name: Chat description: Chat completion endpoints for AI model inference - name: Images description: Image generation endpoints - name: Audio description: Audio transcription endpoints - name: Rerank description: Document reranking endpoints - name: Score description: Text similarity scoring endpoints - name: Privacy description: Privacy classification (PII span detection) endpoints - name: Models description: Public model catalog and information - name: Responses description: >- Stateless response inference (`store: false` only). Raw request/response content, response items, and history are not persisted. Clients must include any prior context in each request. Every successful Responses inference makes exactly one Chat Completions call. Only custom `function` tools are supported. They are client-managed: Cloud returns `function_call` items but never executes them; a later `store: false` request replays the individual call (the raw item from output is accepted) with its matching `function_call_output`, alongside caller-managed message history and the same function tool definitions. The minimal replay path also accepts assistant `message` text parts of type `output_text`, but not reasoning or arbitrary full `response.output` items. Server-executed tools (`web_search`, `web_context_search`, `file_search`, `code_interpreter`, `computer`, and remote `mcp`) and image-generation/editing models are rejected. The separate `POST /mcp` endpoint continues to expose its `web_search` tool independently of Responses; use `/v1/images/*` for image generation/editing. Existing completed-response gateway attestation is preserved best-effort: when the signature write succeeds, `GET /v1/signature/resp_*` retrieves signatures over SHA-256 request/response digests, never raw content. Interrupted streams create no `resp_*` attestation record or legacy disconnect fallback. Conversations, response history, and file input are rejected. - name: Organizations description: Organization management - name: Organization Members description: Organization member and invitation management - name: Workspaces description: Workspace and API key management - name: Users description: User profile and token management - name: Invitations description: Token-based invitation handling - name: Usage description: Usage tracking and billing information - name: Reporting description: Read-only customer usage reporting - name: Billing description: Billing costs endpoint (HuggingFace integration) - name: Staking Farm description: House of Stake farm credit configuration and synchronization - name: Health description: Health check endpoints - name: Attestation description: Attestation and verification endpoints - name: Gateway description: Model gateway integration endpoints - name: Admin description: Administrative endpoints (admin access required) - name: Services description: Public platform services (e.g. web_search pricing) paths: /v1/workspaces/{workspace_id}/api-keys: post: tags: - Workspaces summary: Create API key for workspace description: >- Creates a new API key for a workspace. Note: The key may take up to 10 seconds to become active for authentication due to internal caching. operationId: create_workspace_api_key parameters: - name: workspace_id in: path description: Workspace ID required: true schema: type: string format: uuid requestBody: content: application/json: schema: $ref: '#/components/schemas/CreateApiKeyRequest' required: true responses: '201': description: API key created successfully content: application/json: schema: $ref: '#/components/schemas/ApiKeyResponse' '400': description: Bad request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Workspace not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Internal server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - session_token: [] components: schemas: CreateApiKeyRequest: type: object required: - name properties: expires_at: type: - string - 'null' format: date-time name: type: string spendLimit: oneOf: - type: 'null' - $ref: '#/components/schemas/DecimalPriceRequest' ApiKeyResponse: type: object description: API Key response model required: - id - key_prefix - workspace_id - created_by_user_id - created_at - is_active properties: created_at: type: string format: date-time created_by_user_id: type: string deleted_at: type: - string - 'null' format: date-time expires_at: type: - string - 'null' format: date-time id: type: string is_active: type: boolean key: type: - string - 'null' key_prefix: type: string last_used_at: type: - string - 'null' format: date-time name: type: - string - 'null' spend_limit: oneOf: - type: 'null' - $ref: '#/components/schemas/DecimalPrice' usage: oneOf: - type: 'null' - $ref: '#/components/schemas/DecimalPrice' workspace_id: type: string ErrorResponse: type: object required: - error properties: error: $ref: '#/components/schemas/ErrorDetail' DecimalPriceRequest: type: object description: >- Decimal price for API requests The system internally uses a fixed scale of 9 (nano-dollars = 1 billionth of a dollar). Clients must provide amounts in nano-dollars. Examples: $100.00 USD: amount=100000000000, currency="USD" $1.00 USD: amount=1000000000, currency="USD" $0.01 USD: amount=10000000, currency="USD" required: - amount - currency properties: amount: type: integer format: int64 description: >- Amount in nano-dollars (scale 9). For example, $1.00 = 1000000000 nano-dollars. currency: type: string DecimalPrice: type: object description: >- Decimal price for API responses The system uses a fixed scale of 9 (nano-dollars = 1 billionth of a dollar). The scale field is included in responses for client convenience. required: - amount - scale - currency properties: amount: type: integer format: int64 currency: type: string scale: type: integer format: int64 ErrorDetail: type: object required: - message - type properties: code: type: - string - 'null' message: type: string param: type: - string - 'null' type: type: string securitySchemes: session_token: type: http scheme: bearer bearerFormat: JWT description: >- JWT access token for user authentication (Authorization: Bearer ). Create via POST /users/me/access_tokens. api_key: type: http scheme: bearer bearerFormat: api_key description: 'API key for programmatic access (Authorization: Bearer sk-)' ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.