> ## Documentation Index
> Fetch the complete documentation index at: https://partners.trybloom.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# OpenAPI and agents

> Give the Brand Skills API contract and guides to development agents.

Use the OpenAPI specification as the source of truth for the HTTP contract.

## Machine-readable resources

<CardGroup cols={2}>
  <Card title="OpenAPI specification" icon="file-code" href="/openapi/brand-skills.json">
    Exact operations, authentication, payloads, responses, and errors.
  </Card>

  <Card title="Full documentation context" icon="robot" href="/llms-full.txt">
    The complete guide and reference content in one agent-readable file.
  </Card>
</CardGroup>

Mintlify also publishes a lightweight documentation index at
[`/llms.txt`](/llms.txt).

## Hand this to a coding agent

Give the agent both the OpenAPI specification and `/llms-full.txt`. The
specification owns the HTTP contract; the guides explain the integration flow
and how to mount the downloaded Skill.

You can start with this instruction:

```text theme={null}
Integrate Bloom's Brand Skills API using the supplied OpenAPI specification and
documentation. Keep the API key server-side. Create one Brand Skill, persist its
ID, poll the same resource until terminal, store the downloaded folder with its
paths intact, and delete Bloom's retained copy after storage succeeds.
```

Do not place a real Bloom API key in an agent prompt or committed configuration.