> For the complete documentation index, see [llms.txt](https://docs.veda.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veda.tech/api.md).

# API

The Veda API is the programmatic surface for interacting with Veda vaults outside of the [Veda Console](https://console.veda.tech). It exposes the same primitives that power Veda's first-party products — rebalancing, position data, fees, and accounting — to partners building automation, dashboards, custom strategist tooling, and back-office integrations.

**Base URL:** `https://api.veda.tech`

**Authentication:** Bearer token using an API key created in the [Veda Console](https://console.veda.tech).

**OpenAPI / Swagger:** [api.veda.tech/docs](https://api.veda.tech/docs)

## What's here

| Page                                                                     | Purpose                                                                 |
| ------------------------------------------------------------------------ | ----------------------------------------------------------------------- |
| [Quick Start](/api/quick-start.md)                                       | Create an API key in the console and make your first authenticated call |
| [Vaults](/api/vaults.md)                                                 | List your tenant's vaults; inspect roots set on a specific vault        |
| [Transaction Builder](/api/transaction-builder.md)                       | Discover vault actions and build rebalance calldata                     |
| [Access Control & Merkle Trees](/api/access-control-and-merkle-trees.md) | How vault permissioning works; fetch a merkle tree by root hash         |
| [API Reference](/api/api-reference.md)                                   | Full endpoint reference via the OpenAPI spec                            |
| [Change Log](/api/change-log.md)                                         | What's new, what's deprecated, examples, rate limits                    |

## When to use the API

The API is the right choice when you need to:

* **Automate rebalancing** — write a script or scheduled job that builds and submits rebalance transactions for a vault you operate as a strategist
* **Build a custom dashboard** — surface vault state inside your own product

For everything the hosted API serves, the underlying data is also reconstructible directly from chain. Many partners run both: the API for the fast path, and their own indexer for whatever the API doesn't expose.

## Capabilities

* **Protocol-, asset-, and chain-agnostic** — the same endpoints work across every chain Veda supports
* **Verifiable** — `encoded_tx_data` is calldata you submit yourself from your strategist address; the API never holds keys or signs
* **Simulated by default** — every build is dry-run against Tenderly before returning, so you can catch reverts before broadcasting
* **Composable** — batch multiple actions into a single atomic transaction with `execute-multiple`

## Getting access

API keys are provisioned per partner. If you don't already have a Veda Console account for your team:

1. Reach out to your Veda contact
2. Once your account is provisioned, sign in to [console.veda.tech](https://console.veda.tech)
3. Follow [Quick Start](/api/quick-start.md) to create your first key


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.veda.tech/api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.