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, selected workspace access, and the applicable personal or organization 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
- Header actions
- Synthesis blocks
- Result tabs
The result header exposes actions such as Collaborate, AI Analyst, Export, and New Search.
Credit and execution behavior
What consumes credits
What consumes credits
Launching a new full app search consumes credits. Free previews use a separate quota.
What does not consume credits
What does not consume credits
Opening a result from history does not run a new execution and does not consume credits.
Plan-dependent provider coverage
Plan-dependent provider coverage
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.