# Page Not Found

The URL `building-on-symm-io/technical-documentation/contract-addresses-rasa-capital-endpoints` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Solver Addresses & Endpoints](https://docs.symm.io/api-endpoints-and-deployments/solver-addresses-and-endpoints.md)
- [Rasa Capital](https://docs.symm.io/api-endpoints-and-deployments/solver-addresses-and-endpoints/rasa-capital.md)
- [Instant Trading](https://docs.symm.io/liquidity-provider-documentation/core-concepts/instant-trading.md)
- [Rasa Capital (Zero Spread)](https://docs.symm.io/api-endpoints-and-deployments/solver-addresses-and-endpoints/rasa-capital-zero-spread.md)
- [Frontend Builder Technical Guidance](https://docs.symm.io/exchange-builder-documentation/frontend-builder-technical-guidance.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.symm.io/api-endpoints-and-deployments/solver-addresses-and-endpoints.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.

### Option 2 — Browse the documentation index

Full index: https://docs.symm.io/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.symm.io/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/api-endpoints-and-deployments/solver-addresses-and-endpoints.md`).

You may also use `Accept: text/markdown` header for content negotiation.