Best practices
Production patterns for reliable, economical Bloodhound integrations.
Write measurable missions
State the target count, geography, required evidence, exclusions, and expected output. Avoid objectives such as “research this company” when the integration needs a deterministic result.
Persist before streaming
Store the returned sessionId and continuation token before opening the stream. Checkpoint the processed event index after each durable batch.
Prevent duplicate work
Record your own request ID with the mission ID. Mission creation does not yet accept a client idempotency key, so disable automatic POST retries and keep the returned mission ID as soon as it arrives.
Set the smallest useful budget
Choose the smallest practical fixed budget before starting. Use unlimited only when completion matters more than a preset cap; it still cannot spend beyond the prepaid balance or system safety limit.
Keep credentials narrow
Use one key per environment, rotate regularly, and never pass a production key to browser code.
Next steps
Adapt the complete clients in examples.