> For the complete documentation index, see [llms.txt](https://docs.symm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.symm.io/liquidity-provider-documentation/role-of-a-liquidity-provider-solver.md). # Role of a Liquidity Provider (Solver) On Symmio, traders don't match against a central order book. They express *intents*: requests that say "I want to go long or short this market, here's my size, my price, and the counterparties I'll trade with." Those intents are picked up by a network of independent counterparties called [solvers](/trader-documentation/glossary-of-terms.md). A solver decides whether to take the other side of a trade, quotes prices, and manages the risk that comes with it. When you run a solver, you act as [PartyB](/trader-documentation/glossary-of-terms.md) in the protocol. Your address is whitelisted on the Symmio contracts, so you can lock quotes, open positions, and hold shared risk with traders. Once a trader sends a quote on-chain, your infrastructure listens for the event, pulls in the quote details, and runs internal checks: is the symbol supported, is the account allowed, do you have enough collateral, and does the price fit your strategy? If everything passes, you lock the quote and open the position on-chain, optionally hedging the exposure elsewhere at the same time. Solvers also manage collateral and solvency on their side. Before a position opens or closes, the contracts and the [Muon oracle](/api-endpoints-and-deployments/muon-api.md) verify that both you and the trader have enough margin and that the prices are valid. You decide how much capital to allocate to each trader, how much open interest to allow per market, and when to settle unrealized profit so positions can close safely. Your risk model is your own, but it must satisfy the protocol's solvency rules enforced on the contracts. Solvers also shape the user experience. Frontends rely on solver APIs to show markets, prices, and funding data. When a trader wants to [instantly open a trade](/trader-documentation/how-trading-works-in-symmio.md), they delegate certain functions to you so you can open and close positions without asking them to sign every transaction. When they set a [take profit or stop loss](/trader-documentation/how-trading-works-in-symmio/using-take-profit-and-stop-loss.md), your **conditional orders** service watches the market and submits the close request when their conditions are hit. From the trader's side, the frontend feels like a fast, responsive exchange. --- # 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.symm.io/liquidity-provider-documentation/role-of-a-liquidity-provider-solver.md?ask=&goal= ``` `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.