> For the complete documentation index, see [llms.txt](https://arbridge-network.gitbook.io/arbridge-network-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arbridge-network.gitbook.io/arbridge-network-docs/readme.md).
# Welcome to Arbridge Network
## Welcome to Arbridge Network
Arbridge Network is an automated blockchain market execution ecosystem built on a singular conviction: that the greatest opportunities in blockchain markets are not found in speculation — they are found in the structure of the market itself.
The Web3 ecosystem is one of the most dynamic financial systems ever created, yet it still operates with significant inefficiencies. One of the largest of these is **arbitrage** — price discrepancies that constantly occur across exchanges and blockchain ecosystems. In theory, these opportunities represent billions of dollars in potential value. In practice, only a small percentage of market participants can capture them, because doing so requires advanced infrastructure, constant monitoring, and the ability to execute transactions across multiple chains at high speed.
Arbridge Network exists to close that gap.
### How to use these docs
Start with the [Arbridge Mission](/arbridge-network-docs/introduction/the-arbridge-vision.md), then explore [PULSE](/arbridge-network-docs/automation-and-tools/pulse-engine.md) — the intelligent system at the center of the ecosystem — and the three operational tiers that bring it to members: [Pulse Foundation, Grid, and Prime](/arbridge-network-docs/automation-and-tools/pulse-foundation-grid-and-prime.md).
Welcome aboard.
---
# 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://arbridge-network.gitbook.io/arbridge-network-docs/readme.md?ask=&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.
