> ## 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. # Post v1privacyclassify ## OpenAPI ````yaml /api-reference/openapi.json post /v1/privacy/classify 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/privacy/classify: post: tags: - Privacy operationId: privacy_classify requestBody: content: application/json: schema: $ref: '#/components/schemas/PrivacyClassifyRequestDoc' required: true responses: '200': description: Privacy classification completed successfully content: application/json: schema: $ref: '#/components/schemas/PrivacyClassifyResponseDoc' '400': description: Invalid request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Model not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '429': description: >- Rate limited or overloaded — retry with backoff. Check error.type: rate_limit_exceeded or service_overloaded. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - api_key: [] components: schemas: PrivacyClassifyRequestDoc: type: object description: >- Privacy classification endpoint (passthrough) Proxies privacy classification requests to a token-classification model (e.g. `openai/privacy-filter`) that returns PII spans with categories and scores. Only the `model` field is read from the request for routing; the rest is forwarded as-is. These documentation-only types approximate the request and response bodies for OpenAPI schema generation. The runtime handler still accepts a raw `Bytes` body and forwards it transparently to the provider. required: - model properties: input: description: >- Text or list of texts to classify. Either a string or array of strings. model: type: string description: ID of the model to use for privacy classification. threshold: type: - number - 'null' format: double description: Optional minimum confidence score for returned spans (0.0–1.0). PrivacyClassifyResponseDoc: type: object properties: data: description: >- Per-input classification results; each entry contains `spans` and per-input `usage`. model: type: string description: Model identifier that produced the classification. ErrorResponse: type: object required: - error properties: error: $ref: '#/components/schemas/ErrorDetail' 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.