> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/14.-cross-chain-interoperability-using-fswap/14.5-developer-interaction-with-the-bridge.md).

# 14.5 Developer Interaction with the Bridge

From a developer perspective, the bridge can be integrated into applications through smart contracts and frontend interfaces.

Applications may:

* detect user balances on both FreCx and Polygon
* trigger bridge transactions through UI workflows
* monitor bridge status using transaction hashes
* interact with WFreCx tokens as standard ERC-20 assets on Polygon

Because WFreCx follows standard token interfaces, it can be used within existing DeFi protocols on Polygon, enabling liquidity integration and broader ecosystem participation.


---

# 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.frequencychain.org/14.-cross-chain-interoperability-using-fswap/14.5-developer-interaction-with-the-bridge.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.