Opsis OSINT API
OSINT API for your apps, tools and workflows.
Build email, username and domain search into your website, power an external tool, or integrate public-source intelligence into your investigation workflow.
Your interface. Opsis search underneath.
Websites & apps
Give your users a search feature without building a collector for every source. Send requests through your backend and present the returned profiles and account signals in your own interface.
External tools
Add account and domain research to investigation tools, threat-intelligence products and fraud-review workflows. Keep source references available so your users can inspect the evidence behind a result.
Custom integrations
Connect search to dashboards, automations and other services. Submit identifiers, track each run and bring the findings into the workflows your product already supports.
You build the integration and user experience; Opsis provides the search API. These are use cases, not prebuilt integrations or an automated fraud-scoring service. Account presence or absence is not proof of fraud. Follow our acceptable-use terms; Opsis is not for employment, tenant or credit-eligibility screening.
One API. Three kinds of input.
Search an email, username or domain. Each source can return different details; your integration receives results in a consistent JSON structure.
Email enrichment
Discover available account-existence signals and associated profile information. Not every service exposes an email-to-profile connection or the same fields.
Username lookup
Research a handle across supported sources and retrieve matching profile details where available. Cross-platform matches need independent verification.
Domain context
Request domain searches from the same endpoint. Incorporate returned domain-related findings alongside account research in your own application.
Build the search experience your users need.
JSON for your interface
Use run IDs, source and platform fields, result values and source-dependent metadata to build profile cards, reports or your own result views. Keep source references attached as you present the findings.
Progress for your users
Start a run and poll its status, or use server-sent events to show results and progress as they arrive. An optional bounded wait mode returns inline results when a search finishes within its wait window.
Usage you can manage
Read run status and module progress, inspect your API credit balance, and check API capabilities. Build rate-limit and incomplete-result handling into your product; a closed connection does not prove completion.
Example request · No live search
curl -X POST https://api.useopsis.com/v1/searches \
-H "Authorization: Bearer $OPSIS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"type":"email","query":"[email protected]"}'
# Use the returned run_id to read progress and results.
curl "https://api.useopsis.com/v1/searches/<run_id>" \
-H "Authorization: Bearer $OPSIS_API_KEY"Use your own authorized input. Store the key on your server, never in browser code. Replace <run_id> with the value returned by the first request.
Pro access. Separate API credits.
Keep integration usage separate from searches in the web app.
Start with Pro
An active Pro subscription is required for new API customers. Create a key in your account, then buy prepaid API credits. Legacy Unlimited access is preserved.
View subscription plans →Top up as you need
Top-ups start at $20 for 50 credits. Volume pricing reaches $0.25 per credit at 1,000 credits ($250); larger quantities keep that rate. Prices are in USD, in addition to your subscription.
Standard searches cost one credit; premium username searches cost two and include additional solver-backed checks. Reading results does not spend search credits.
Purchased API credits carry over until spent, but require eligible plan access to use. Subscription-credit fallback defaults off; you can enable it in API settings. Top-ups are one-time purchases, not automatic reloads.
Give your users evidence, not just a match.
Opsis maintains source-specific modules and tests them with positive and negative fixtures. These checks help reduce false positives; they do not guarantee complete coverage or verify someone’s identity. Fields, availability and completion times vary by source. See our methodology and limitations.