# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Technical Architecture](https://a1c-io.gitbook.io/docs/features-and-technical/technical-architecture.md)
- [Our Presences](https://a1c-io.gitbook.io/docs/links/our-presences.md)
- [A1C Token Information](https://a1c-io.gitbook.io/docs/economic-model/a1c-token-information.md)
- [Key Features](https://a1c-io.gitbook.io/docs/features-and-technical/key-features.md)
- [Development Roadmap](https://a1c-io.gitbook.io/docs/future-plans/development-roadmap.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://a1c-io.gitbook.io/docs/features-and-technical/technical-architecture.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://a1c-io.gitbook.io/docs/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://a1c-io.gitbook.io/docs/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., `/docs/features-and-technical/technical-architecture.md`).

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