# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Sign up and eligibility](https://stoa-1.gitbook.io/stoa-support-centre/getting-started/sign-up-and-eligibility.md)
- [Gift card issues](https://stoa-1.gitbook.io/stoa-support-centre/perks-and-redemption/gift-card-issues.md)
- [Information (Side Panel) Architecture](https://stoa-1.gitbook.io/stoa-support-centre/perks-and-redemption/information-side-panel-architecture.md)
- [Redeeming Apple and Google Play enabled Perks](https://stoa-1.gitbook.io/stoa-support-centre/perks-and-redemption/redeeming-apple-and-google-play-enabled-perks.md)
- [Travel](https://stoa-1.gitbook.io/stoa-support-centre/perks-and-redemption/perk-information-list/travel.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://stoa-1.gitbook.io/stoa-support-centre/getting-started/sign-up-and-eligibility.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://stoa-1.gitbook.io/stoa-support-centre/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://stoa-1.gitbook.io/stoa-support-centre/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., `/stoa-support-centre/getting-started/sign-up-and-eligibility.md`).

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