> 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-deposits/what-are-intents-deposits.md).

# What are Intents Deposits?

Deposit Addresses are a deposit primitive built on NEAR Intents. Generate a deposit address for the user - the system handles chain detection, routing, asset conversion, and settlement.

<figure><img src="https://387686700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLp9IVb8Xkubcbzzk80Br%2Fuploads%2FVIge2RMEutqn1nxoBTjB%2FScreenshot%202026-04-16%20at%2011.37.41.png?alt=media&amp;token=537ccc17-244d-433d-804f-5ce60b9470f4" alt="" width="375"><figcaption></figcaption></figure>

The user performs a standard token transfer to the address. Everything after that — monitoring, routing via NEAR Intents, optional swap, and crediting the destination — is handled on the infrastructure side with no further input required from the user or the integrating application.

## Features

### Cross-chain routing

Deposits from any supported source chain are automatically detected and routed. The integrating application does not need to handle per-chain logic or monitor incoming transactions.

### Non-EVM Support

Source chains include EVM networks and non-EVM chains: Tron, Bitcoin, Zcash, Solana, TON, and NEAR. See [Supported Chains](https://docs.intents.aurora.dev/intents-deposits/supported-chains.md) for the full list.

### Permissionless

No allowlist, no approval process. API keys are issued immediately. Start generating addresses and testing end-to-end flows without contacting the team.

### Webhooks (coming soon)

Stay informed about transaction status updates with webhooks. Set up URL endpoints to receive event notifications directly from the system, allowing seamless integration into your existing workflows.

### Persistent addresses

Each address is permanent and reusable. There is no TTL, no session, and no requirement to re-generate between deposits. The same address accepts unlimited sequential deposits. Read more about [Persistent Addresses](https://docs.intents.aurora.dev/intents-deposits/persistent-addresses.md).

### Confidentiality

This is an optional feature where source deposits are separated from destination withdrawals, so outside actors don’t have a link between deposits and withdrawals because they go through confidential intents.

## Next Steps

{% stepper %}
{% step %}

### Create API key

First, create an account and set up [API Keys & Fees](https://docs.intents.aurora.dev/getting-started/api-keys-and-fees.md) for your integration.
{% endstep %}

{% step %}

### Decide on the integration path

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a data-mention href="https://docs.intents.aurora.dev/intents-deposits/quickstart/widget-integration.md">Widget integration</a></td><td data-object-fit="contain"><a href="https://387686700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLp9IVb8Xkubcbzzk80Br%2Fuploads%2FVIge2RMEutqn1nxoBTjB%2FScreenshot%202026-04-16%20at%2011.37.41.png?alt=media&amp;token=537ccc17-244d-433d-804f-5ce60b9470f4">Screenshot 2026-04-16 at 11.37.41.png</a></td></tr><tr><td><a data-mention href="https://docs.intents.aurora.dev/intents-deposits/quickstart/api-integration.md">API integration</a></td><td><a href="https://images.unsplash.com/photo-1594904351111-a072f80b1a71?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHwzfHxhcGl8ZW58MHx8fHwxNzc2OTI1NjMwfDA&#x26;ixlib=rb-4.1.0&#x26;q=85">https://images.unsplash.com/photo-1594904351111-a072f80b1a71?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHwzfHxhcGl8ZW58MHx8fHwxNzc2OTI1NjMwfDA&#x26;ixlib=rb-4.1.0&#x26;q=85</a></td></tr></tbody></table>

{% endstep %}
{% endstepper %}

**Questions?** [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-deposits/what-are-intents-deposits.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.
