> For the complete documentation index, see [llms.txt](https://docs.bitmind.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitmind.ai/api-reference/enterprise-api.md).

# Enterprise API

Use the Enterprise API for zero-retention integrations.

## Overview

This API is intended for enterprise customers.

It uses enterprise-scoped credentials.

It does not store submitted media.

It does not log analytics for processed media.

Base URL: `https://enterprise.bitmind.ai`

### Authentication

Send a Bearer token in the `Authorization` header.

Use an enterprise API key.

Standard API keys are rejected.

See [Authentication](/api-reference/authentication.md).

### Endpoints

#### `POST /image`

Zero-retention image detection.

See [Enterprise Image](/api-reference/enterprise-api/enterprise-image.md).

#### `POST /video`

Zero-retention video detection.

Video access must be enabled on your account.

See [Enterprise Video](/api-reference/enterprise-api/enterprise-video.md).

### Response shape

Enterprise endpoints return the same core detection fields.

They do not return storage keys because media is not retained.

```json
{
  "isAI": false,
  "confidence": 0.897
}
```

### Rate limits

Rate limits are configured per client.

Typical ranges are `1,000` to `10,000+` requests per hour.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bitmind.ai/api-reference/enterprise-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.