Skip to content

docs: describe rate limiting without the figures #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
christabone merged 1 commit into from
Oct 13, 2026
Merged

docs: describe rate limiting without the figures #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,9 +140,9 @@ Each is described in [docs/tools.md](docs/tools.md).
- **Data release.** Every result names the FlyBase release it came from, currently FB2026_03.
- **BLAST databases.** BLAST searches the archived FB2023_04 database set, so BLAST results can lag the rest of
the server. Each `blast_submit` response says so.
- **Rate limit.** Each client IP gets about 2 requests per second, with a short burst allowance. Requests over
the limit get HTTP 429. One assistant session stays well under it. Please be polite with scripts: pause
between calls and use `batch_download` for long ID lists.
- **Fair use.** The server is shared and rate limited per client. Requests over the limit get HTTP 429;
wait and retry. One assistant session stays well within it. Please be polite with scripts: pause
between batches, use `batch_download` and `validate_ids` for bulk work, and cache what you fetch.
- **Only `/mcp` is public.** `/health` and `/metrics` are intentionally not exposed and return 404.

## BLAST
Expand Down
Loading