> For the complete documentation index, see [llms.txt](https://use.temporal.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://use.temporal.xyz/nozomi/faq.md).

# FAQ

## How do I get access?

Nozomi is available to approved users. [**Request access via this form →**](https://form.typeform.com/to/pGXN0ryV?utm_source=docs\&utm_medium=cta\&utm_campaign=nozomi_access\&utm_content=faq)

## Rate Limits

Each API key has an associated rate limit. Rate limits are applied **per region** — sending the same transaction to multiple regions does not count against your limit.

#### QoS Priority

If your transactions have a high failure rate, Nozomi applies a QoS penalty to your priority. For example, if only 10% of your transactions land successfully over the last 30 minutes, your effective priority is discounted to 10%.

To maintain high QoS priority:

* Check account state before submitting to avoid predictable failures.
* Avoid sending transactions that will fail due to stale blockhashes.
* Monitor your landing rate and reduce volume if it drops.

## Custom Limits

High-volume users can request custom rate limits and priority configurations. Reach out via Discord.

## Does Nozomi Simulate Transactions?

No. Nozomi does not simulate transactions. It routes directly to the TPU for the fastest possible delivery.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://use.temporal.xyz/nozomi/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.