Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.oathnet.org/llms.txt

Use this file to discover all available pages before exploring further.

Account & Access

Generate it in Dashboard > Account.
Yes. Public customer-facing endpoints use the x-api-key header.
Yes. File search, exports, bulk search, archive downloads, AI filter creation, and scanner quotas depend on your plan.

Search & Results

Prefer /service/v2/* for new integrations. Legacy /service/* search endpoints remain available for compatibility and OSINT lookups.
Search for a victim, fetch the victim manifest, then request a specific file or the archive download.

Technical

Successful responses use a few different shapes:
{
  "success": true,
  "message": "Description",
  "data": { "...": "..." }
}
Search endpoints and most legacy lookups return the envelope above.Some v2 endpoints return raw JSON instead, including:
  • file-search jobs
  • export jobs
  • bulk-search list and status
  • AI filter endpoints
  • breach autocomplete endpoints
  • scanner CRUD endpoints
Download endpoints return raw text or binary streams.
Technically yes, but it is not recommended. API keys should stay on a trusted backend.
The q parameter automatically detects common types such as email, domain, IP, Discord ID, and username where supported by the endpoint.

Support

For additional questions, contact support@oathnet.org or join the Discord.