BreachSpiderBREACHSPIDER
Research Intel Features Docs About Sign In Sign Up Free

API and SDK Terms

API and SDK Terms, version 1.0, November 8, 2026. CITED Relevance LLC, operator of BreachSpider.

These terms add to the Terms of Service for anyone who uses the BreachSpider API, the breachspider Python SDK, the BreachSpider MCP server (the breachspider-mcp package or the hosted connector) or the embeddable widget.

1. The client software

The Python SDK and the MCP server package are published under the MIT License, which governs the code itself. Using them to call BreachSpider is governed by these terms, because the code is a client for the service.

2. Keys and access

3. Limits

Each key has request limits and an allowance that depend on the plan; current usage is reported in response headers and in Settings. Calls over a limit are refused with a retry hint. Do not spread traffic over several keys or accounts to avoid limits. Large inventories go through batch jobs, not loops of single calls.

4. What you send

5. Versioning and changes

The API follows the BreachSpider versioning and breaking-change policy: everything under /api/v1/ is stable; new fields, objects, warning codes and enum values can appear at any time, so clients must ignore unknown fields and tolerate new values; a breaking change gets a new version and notice before the old one is retired.

6. Using the results

7. The widget

A site that embeds the BreachSpider widget must keep the widget's attribution and source links visible and must not change what it says about a result. Device checks made through the widget count against the partner's key.

8. Security

Report vulnerabilities in the API, SDK, MCP server or widget under the disclosure policy. Do not load-test or scan the API.

9. Suspension and ending

We may throttle or suspend a key that breaks these terms or puts the service at risk, and tell the key's organization. You may stop using the API at any time; revoke your keys when you do.