# API Reference

The [full API reference](/api/reference.html) lists the public endpoints, their
required fields, response schemas and HTTP status codes. Download the
[OpenAPI schema](/api/openapi.json) to generate a client for your integration.

Start with the [API quickstart](/quickstart/) to authenticate. Then use
[Direct AI Requests](/api/direct-inference/), [Agent Runs](/chat_agents/) or
[Workflow Runs](/api/workflow-runs/).

The reference covers every supported endpoint. Other routes the Redbelt app uses
can change without notice, so build only on the ones listed here.

## Read an endpoint

1. Find the operation and its HTTP method.
2. Check path parameters, request fields, and required values.
3. Review the response for the specific success status.
4. Send an authenticated request to your deployment's API base URL.

An example schema describes the response shape; it is not evidence that a live
request succeeded. Background operations can return **202** before their work is
complete. Follow the corresponding guide to verify the result.

## Organizations

Each API key belongs to one organization, and every request acts in it. You don't
need to send **X-Redbelt-Organization-ID**. If you do, it must match the key's
organization, or the request returns **403**.

## Deployment differences

Hosted and self-hosted deployments can differ in available providers, models,
and integration setup. Use the API URL and credentials for the deployment you
are calling. For an endpoint or output-delivery contract not listed in the
public reference, contact <support@redbelt.ai>.
