# API

Use HTTP to call Genesis models or MatrixOne Intelligence product capabilities. The two API categories use different service addresses, credentials, and resource models. Confirm the target category before calling an API; do not mix base URLs or authentication headers.

## Choose an API

| Goal | API | Next step |
| --- | --- | --- |
| Call text, multimodal, embedding, or reranking models from an application | Genesis Model API | [Use the Genesis Model API](genesis-model-api/index.md) |
| Manage workspace, data, workflows, agents, and compute resources | Product API | [Use Product API](product-api/index.md) |
| Integrate automation, agent building, skills, tools, MCP, or event callbacks | Integrations and extensions API | [View integrations and extensions](integrations/index.md) |
| Handle authentication, request formats, pagination, retries, and status codes | API common rules | [View API common rules](common/index.md) |

Genesis model calls are not scoped to a Product workspace. Provider, Backend, and Router resources in Product configure internal model services; they do not replace Genesis model APIs.

## API, SDK, and CLI boundaries

- Use an API to call a service directly from any HTTP-capable language or runtime.
- Use an [SDK](../sdk/index.md) to call a service from an application through a language client.
- Use the [CLI](../cli/index.md) to run Product tasks from a terminal or automation script.

```{toctree}
:hidden:
:maxdepth: 1

Genesis Model API <genesis-model-api/index>
Product API <product-api/index>
Integrations and extensions <integrations/index>
API common rules <common/index>
```