# Page Not Found

The URL `2023-08/august-17-prepare-for-usage-based-billing-append-sas-tokens-to-uris` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [August 17: Prepare for usage-based billing; append SAS tokens to URIs](https://changelog.graphlit.dev/august-2023/august-17-prepare-for-usage-based-billing-append-sas-tokens-to-uris.md)
- [August 11: Support for Azure AI Document Intelligence by default, language-aware summaries](https://changelog.graphlit.dev/august-2024/august-11-support-for-azure-ai-document-intelligence-by-default-language-aware-summaries.md)
- [August 25: Support for custom AWS Bedrock endpoints, feed-specific backup, bug fixes](https://changelog.graphlit.dev/august-2025/august-25-support-for-custom-aws-bedrock-endpoints-feed-specific-backup-bug-fixes.md)
- [August 8: Support for LLM-based document extraction, .NET SDK, bug fixes](https://changelog.graphlit.dev/august-2024/august-8-support-for-llm-based-document-extraction-.net-sdk-bug-fixes.md)
- [August 31: Support for Google 'nano-banana' image generation, email filtering options.](https://changelog.graphlit.dev/august-2025/august-31-support-for-google-nano-banana-image-generation-email-filtering-options..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://changelog.graphlit.dev/august-2023/august-17-prepare-for-usage-based-billing-append-sas-tokens-to-uris.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://changelog.graphlit.dev/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://changelog.graphlit.dev/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., `/august-2023/august-17-prepare-for-usage-based-billing-append-sas-tokens-to-uris.md`).

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