Itachi’s Crow

USAGE LIMITS

Room to explore. Limits to keep it running.

These limits help keep the public demo available and reduce accidental overuse. Each feature has its own allowance.

Limits per IP address · Updated 14 September 2026
FeaturePer minutePer hour
Chat requests12120
Place searches20100
Map starts410
AI images & panoramas624
Voice-session starts312
Research & trip plans320

What counts?

Attempts count when admitted, even if generation later fails or you cancel. A request rejected because you are already at the limit does not use another allowance.

When do limits reset?

The minute allowance resets at the start of the next clock minute. The hourly allowance resets at the start of the next clock hour. Both limits apply: reaching either one pauses that feature until its window resets. Unused requests do not carry over.

For example, reaching the hourly image limit at 2:40 pm means waiting until 3:00 pm, even if your minute allowance is available.

If you reach a limit

The app tells you how many seconds to wait. Try again after that time. Refreshing or switching API keys does not reset your allowance. Other features with available allowances can still be used.

Limits are shared by people using the same public IP address, which can include the same home, office, or event Wi-Fi. They are not individual account allowances.

Google and OpenAI limits also apply

Providers can reject a request even when your app allowance remains. Google’s 3D map, place-detail, and photo requests have their own quotas. These app limits do not cap every direct Google request or guarantee a maximum bill.

What is stored?

Usage counts are stored on the server so they survive reloads and restarts. The limiter stores a daily hash derived from your IP address and the feature, rather than the raw IP address. This describes the limiter’s counters, not Google or OpenAI’s data handling.

Return to exploring ↗