# Page Not Found

The URL `tylt-cpg-crypto-payment-gateway/api-reference/accept-crypto-payments` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Accept Crypto-Assets](https://docs.tylt.money/tylt-cpg-crypto-asset-gateway/api-reference/accept-crypto-assets.md)
- [Transfer Crypto-Assets](https://docs.tylt.money/tylt-cpg-crypto-asset-gateway/api-reference/transfer-crypto-assets.md)
- [Supporting API's](https://docs.tylt.money/tylt-cpg-crypto-asset-gateway/api-reference/supporting-apis.md)
- [Creating a Pay-in Request](https://docs.tylt.money/tylt-cpg-crypto-asset-gateway/api-reference/accept-crypto-assets/creating-a-pay-in-request.md)
- [Set Custom Conversion Rate](https://docs.tylt.money/tylt-cpg-crypto-asset-gateway/api-reference/accept-crypto-assets/set-custom-conversion-rate.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.tylt.money/tylt-cpg-crypto-asset-gateway/api-reference/accept-crypto-assets.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.tylt.money/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.tylt.money/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., `/tylt-cpg-crypto-asset-gateway/api-reference/accept-crypto-assets.md`).

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