# Page Not Found

The URL `files/QzfCwQ4omFIT8xJ0om8N` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Announcement of Cadabra Finance stopping](https://cadabra.gitbook.io/v2/articles/announcement-of-cadabra-finance-stopping.md)
- [ABRA emission + External Yield. Complementarity](https://cadabra.gitbook.io/v2/articles/abra-emission-+-external-yield.-complementarity.md)
- [Strategies boost algorithm](https://cadabra.gitbook.io/v2/articles/strategies-boost-algorithm.md)
- [ABRA locking migration vs Unlocking. What to choose?](https://cadabra.gitbook.io/v2/articles/abra-locking-migration-vs-unlocking.-what-to-choose.md)
- [ABRA Locking: why it’s essential and how it increases your yield](https://cadabra.gitbook.io/v2/articles/abra-locking-why-its-essential-and-how-it-increases-your-yield.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 documentation index with the `ask` parameter:

```
GET https://cadabra.gitbook.io/v2/articles/announcement-of-cadabra-finance-stopping.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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://cadabra.gitbook.io/v2/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://cadabra.gitbook.io/v2/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., `/v2/articles/announcement-of-cadabra-finance-stopping.md`).

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