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

# Bridge Integration

Integrate the Onyx bridge without hardcoding mutable limits or operator addresses.

The Onyx bridge moves XCN, ETH, and USDC between Ethereum Mainnet and Onyx Mainnet.

| Interface           | URL                                          |
| ------------------- | -------------------------------------------- |
| User interface      | `https://app.onyx.org/bridge`                |
| **REST API**        | **`https://bridgeapi.onyx.org/api/v1`**      |
| Ethereum BridgeLock | `0xa9fd64b5095d626f5a3a67e6db7fb766345f8092` |
| Onyx BridgeMint     | `0x1d14ae13ca030eb5e9e2857e911af515cf5ffff2` |

{% hint style="info" %}
**External integrators** should call **`https://bridgeapi.onyx.org/api/v1`** directly. The first-party app may use a same-origin proxy under `app.onyx.org`; that path is optional for browser UIs and is **not** required for server-side or partner clients.
{% endhint %}

## Integration rules

* Call `GET /health` before enabling a bridge action.
* Fetch `GET /bridge/limits` and a fee quote immediately before presenting or submitting a transfer.
* Poll `GET /bridge/status` using the source transaction hash and surface the returned status truthfully.
* Treat maintenance or delayed states as unavailable/in-progress, not as success.
* For native XCN from Onyx to Ethereum, register the signed intent first and send only to the destination returned by that response.
* ERC-1271 signatures from deployed smart accounts are supported. For ERC-4337, bind the final execution transaction hash, not the user-operation hash.

Processing time depends on source-chain confirmation, relayer state, security holds, and destination submission. Applications must use API state instead of promising a fixed duration.

See the [REST API Reference](https://docs.onyx.org/developer-guide/bridge/api-reference.md), [Smart Account Integration](https://docs.onyx.org/developer-guide/bridge/smart-account-integration.md), and [contract registry](https://docs.onyx.org/reference/contracts.md).


---

# 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.onyx.org/developer-guide/bridge.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.
