> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.alpha.openantares.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.alpha.openantares.com/_mcp/server.

# Vault scoping

Call `GET /v1/vaults` first. It returns only the vaults the credential owner can access. Use the exact returned ID or name in later requests.

```json
{
  "vault": "qh73edk6m4999tm8v7etwcm0x98dng7t",
  "query": "carrier credentials"
}
```

## Scope rules

* A credential may have access to several vaults.
* Most read and write tools accept a `vault` field.
* A vault ID is preferred for production integrations because names can change.
* If a credential can reach several vaults, do not rely on a default.
* Never reuse a vault chosen for one customer when processing another customer's request.

## Cross-vault analysis

Run a separate scoped request for each vault, keep each result labeled, and combine the results only in your own application after confirming that the user requested the comparison.

Do not fetch every accessible vault and merge the contents as a convenience. That breaks client boundaries even when the credential technically has access.