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

# Curate API Overview

> How Erebor, Strategy Engine, OMS, and merkle publishing fit together for SuperVault operations.

Curate is the institutional control plane for SuperVaults. Its APIs split by operational responsibility.

## Services

| Service                | Owns                                                                            | Docs                                            |
| ---------------------- | ------------------------------------------------------------------------------- | ----------------------------------------------- |
| Erebor                 | Vault reads, settings, registries, merkle config, upkeep, users, pause controls | [Erebor API](/curate/api/erebor)                |
| Strategy Engine        | Strategy lifecycle, ordering, live shards, intent projections, emergency locks  | [Strategy API](/curate/api/strategy)            |
| OMS                    | DeFiX intent execution, events, session-key readiness, hook transactions        | [OMS API](/curate/api/oms)                      |
| Public merkle artifact | Published proof data for keepers and integrators                                | [Merkle Publishing](/curate/api/merkle-publish) |

## Auth

Authenticated endpoints use Dynamic-issued bearer JWTs:

```bash theme={null}
Authorization: Bearer <jwt>
```

Public endpoints, such as published merkle artifacts and public vault listings, do not require a manager JWT.

## Prepare, Sign, Confirm

Most protocol mutations follow this model:

1. API prepares calldata.
2. Wallet signs and submits the transaction.
3. API / indexer reads resulting state or confirms a transaction hash.

Do not treat a successful prepare request as a completed setting change.

## Vault Identity and Listing State

A vault can be:

* Created onchain.
* Indexed in Erebor.
* Active / discoverable after upkeep is funded.
* Listed and available in the Superform catalog.

Those are related but separate states. The dashboard setup flow tracks them together so operators do not route users into a half-configured vault.

## Strategy Execution Flow

1. Manager configures hooks and publishes merkle authorization.
2. Manager whitelists yield sources and pairs oracles.
3. Manager creates and orders strategies.
4. Strategy Engine evaluates rules and submits DeFiX intents.
5. OMS validates authorization and executes hook transactions.
6. Events and fills flow back into intent history.

## API Reference Pages

* [Erebor API](/curate/api/erebor)
* [Strategy Engine API](/curate/api/strategy)
* [OMS API](/curate/api/oms)
* [Merkle Publishing](/curate/api/merkle-publish)