# Page Not Found

The URL `developer-guides/03-how-to-create-a-strategy` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Building the Blend Strategy](https://docs.defindex.io/advanced-documentation/developer-introduction/03-how-to-create-a-strategy.md)
- [What is a strategy?](https://docs.defindex.io/advanced-documentation/developer-introduction/what-is-a-strategy.md)
- [Strategy Contract](https://docs.defindex.io/advanced-documentation/10-whitepaper/04-contracts/02-strategy-contract.md)
- [Deposit & Transfer dfTokens](https://docs.defindex.io/api-integration-guide/guides-and-tutorials/deposit-and-transfer-dftokens.md)
- [Sponsored Transactions (Fee Bump Tx)](https://docs.defindex.io/api-integration-guide/guides-and-tutorials/sponsored-transactions.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://docs.defindex.io/advanced-documentation/developer-introduction/03-how-to-create-a-strategy.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://docs.defindex.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.defindex.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., `/advanced-documentation/developer-introduction/03-how-to-create-a-strategy.md`).

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