Skip to main content
Osintly runs each search through an API-driven pipeline with progressive delivery to the result page.

Validated search launch

Input, plan access, and credit availability are checked before execution is launched.

Streaming delivery

Result cards and status updates arrive progressively while the search is running.

Persistent history

Stored searches can be reopened later without launching a new execution.

​
Search lifecycle

1

Normalize input

The query is received, trimmed, and validated against the selected or detected input type.
2

Authorize execution

Plan entitlements, team/project access, and billable credit source are validated.
3

Launch execution

The search is launched through the upstream search service.
4

Stream updates

The result page subscribes to stream events and updates cards/status progressively.
5

Persist and index

Search metadata and final result payload are persisted for history and reopening.

​
What the user sees during execution

The result header exposes actions such as Collaborate, AI Analyst, Export, and New Search.

​
Credit and execution behavior

Launching a new search execution consumes credits.
Opening a result from history does not run a new execution and does not consume credits.
The provider set depends on your plan and selected options. Some sources are disabled on lower plans.
For plan pricing and current entitlements, refer to osint.ly/pricing.