BloodhoundBloodhound Docsv1

Rate limits

Design clients that remain stable under concurrency and provider pressure.

Bloodhound v1 does not currently publish or enforce a fixed request-per-minute quota at the public API boundary.

The mission-creation endpoint does not currently accept an idempotency key. Do not automatically repeat a timed-out creation request: a mission may already have started. Streams are safe to reconnect using the existing sessionId and startIndex.

Do not start a replacement mission because a stream reconnect failed. Reconnect to the original sessionId.

Backoff

Use exponential backoff with jitter for temporary 5xx or network failures. Reset the backoff after a successful response. Never start a replacement mission merely because its stream disconnected.

Next steps

Implement the retry rules in best practices and handle errors.

On this page