> 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 self-service: create an account and generate an API key in the dashboard. [**Sign up →**](https://dashboard.nozomi.temporal.xyz/sign-up?utm_source=docs\&utm_medium=cta\&utm_campaign=nozomi_access\&utm_content=faq)

## Support & Community

Join our [**Discord**](https://discord.gg/8Tw6wMdvtx) for announcements and updates.

Need help? You can reach the team:

* In our [**Discord**](https://discord.gg/8Tw6wMdvtx).
* Through **live chat** in the dashboard (`dashboard.nozomi.temporal.xyz`).

## Rate Limits

Each API key has a rate limit enforced **per key, per region, per second**. Because it is per region, sending the same transaction to multiple regions does **not** count against your limit in a single region. Fanning out is the first thing to try if you are hitting the limit.

New keys start with a default of **5 requests/second**. A `429` response means you exceeded your per-key, per-region rate, or your traffic was flagged as spam.

When you hit `429`:

1. **Fan out across regions.** Limits are per region, so sending the same signed transaction to several regional endpoints multiplies your effective throughput. See [Regions & Endpoints → Send to multiple regions](/nozomi/endpoints.md#send-to-multiple-regions).
2. **Use one key and stop client-side retries.** Nozomi retries server-side; resubmitting the same transaction burns your limit and hurts your priority. Do not spread traffic across multiple keys.
3. **Then request an increase** (below).

## Requesting a Higher Limit

Request a higher rate limit from your key in the dashboard (`dashboard.nozomi.temporal.xyz`). Requests are reviewed based on your **landing rate, success rate, and overall transaction quality**, not purchased. Keeping those healthy is what qualifies you for a higher limit.

## Priority

Nozomi prioritizes transactions based on your **tip** and your **historical success and landing rates**. Consistently landing successful transactions keeps your priority high; a high failure rate lowers it.

To keep your priority high:

* Don't send transactions you expect to fail: check account state before submitting.
* Avoid stale blockhashes.
* Let Nozomi handle retries instead of resubmitting client-side.

## Does Nozomi Simulate Transactions?

No. Nozomi does not simulate transactions. It routes them for the fastest possible delivery.

## Why Didn't My Transaction Land?

See the [Troubleshooting](/nozomi/troubleshooting.md) page. The most common causes are a tip below the minimum, over-requested compute units, client-side retry loops, and a low landing/success history.

## How Do I Protect Against Sandwiching / MEV?

Default keys are speed-optimized and are not sandwich-protected. A separate **MEV Protect** key is available on request. See [Tipping → Front-Running Protection](/nozomi/tipping-and-faq.md#front-running-protection). As a backstop on any key, set a strict slippage tolerance and enforce `minAmountOut`.

## Does Nozomi Offer a Shredstream or Bundle Feed?

No. Nozomi does not offer a shredstream feed, and there is no Jito-style bundle-subscribe / gRPC subscription feed. The low-latency product is transaction submission. For tip data, use the [Tip Stream](/nozomi/tip-stream.md).

## Managing Keys & Account

The **dashboard** (`dashboard.nozomi.temporal.xyz`) is the self-service surface: create or import API keys, request rate-limit increases, view per-transaction tip / success analytics, and manage tip accounts.

* **Sign in with Google or with email and password.**
* **Teams are supported.** You can invite other people to your team from the dashboard.


---

# 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.