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

# Bridge integrations

Using **neuron** bridges involves a combination of REST APIs and direct on-chain interactions with bridge smart contracts.

Any protocol can use the existing **neuron** cross chain bridging infrastructure to add bridging capabilities to their app or protocol.

The [REST APIs](/integrations/api.md) provided by the protocol serve as the primary interface for interacting with the bridging service. These APIs enable users to retrieve bridging quotes, explore available bridging options, query bridge contracts, fetch address balances, and access bridging history. 

Additionally, direct on-chain interactions with smart contracts are necessary to facilitate token transfers and execute bridging transactions securely. 

Users interact with the smart contracts to approve token spending, deposit funds into the bridge, and (importantly) [initiate the bridging process](/integrations/building-bridge-deposit.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 dynamically by asking a question.

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

```
GET https://docs.goneuron.xyz/integrations/bridge-integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.