> For the complete documentation index, see [llms.txt](https://docs.intents.aurora.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intents.aurora.dev/intents-connect/deep-dive/api-usage.md).

# API Usage

The Intents Connect API gives developers full programmatic control over cross-chain protocol interactions. Rather than embedding a UI component, you call the API directly — constructing intents, receiving transaction plans, and managing execution from your own backend or application logic.

#### When to use the API

The API is the right integration path if you want to:

* Enable AI agents to perform any operation on the chain
* Build a custom interface around Intents Connect
* Orchestrate cross-chain actions programmatically as part of a larger workflow
* Integrate into a backend system where an embeddable widget is not applicable

If you want a frontend-first integration, the [Intents Connect Widget](https://docs.intents.aurora.dev/intents-connect/intents-connect-widget.md)[ ](https://docs.intents.aurora.dev/intents-connect-widget/introduction)may be a better starting point.

#### What the API handles

You provide the intent parameters — source chain and wallet, destination chain, target protocol, asset, and amount. The API then:

1. Validates the intent and checks for replay safety
2. Prepares the full transaction plan for the destination chain
3. Estimates gas and quotes fees upfront, before execution
4. Executes on the destination chain via the intermediary account
5. Returns status updates and transaction hashes throughout

#### Get access

Start using the API or contact the team. [Talk to the team](mailto:contact@aurora.dev)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intents.aurora.dev/intents-connect/deep-dive/api-usage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
