> 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/api.md).

# API

Use the standard BitMind API for general integrations.

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

This surface is intended for normal application and backend usage. Use it when you need standard detection access with regular API keys.

## Choosing an endpoint

Most integrations should start with [**Unified Detect**](/api-reference/api/v1-detect.md) (`POST /v1/detect`). It inspects your input, figures out whether it's an image, video, or text, and runs the right detector — so you don't have to branch on media type yourself.

Call a **type-specific endpoint** when you already know the media type and want to be explicit:

| Endpoint                                           | Use when                                                             |
| -------------------------------------------------- | -------------------------------------------------------------------- |
| [Unified Detect](/api-reference/api/v1-detect.md)  | You want one endpoint to auto-detect and route (recommended default) |
| [Detect Image](/api-reference/api/detect-image.md) | The input is always an image                                         |
| [Detect Video](/api-reference/api/detect-video.md) | The input is always a video (and you may want trim parameters)       |
| [Detect Text](/api-reference/api/detect-text.md)   | The input is always text                                             |

All of these return the same per-type result shapes; Unified Detect simply wraps the matching result in a `{ "mediaType", "result" }` envelope.


---

# 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/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.