Why This Search Exists
Teams want repeatable access to public sources such as GitHub, arXiv, news feeds, and research sites without standing up a full browser workflow for every retrieval.
At the same time, they still want one platform that can also support more stateful browser tasks later.
Recommended Approach
Hosted adapters offer a good middle path. They provide source-aware, named commands for public lookups while keeping the heavier local browser runtime reserved for tasks that truly need it.
That makes the hosted `site_run` surface especially useful for market-intelligence pipelines built around public information.
Key Takeaways
- Market-intelligence collection often fits public hosted adapters well.
- Source-aware APIs reduce normalization overhead.
- Hosted adapters are best when the task is read-only and stateless.
- Local runtime remains available for stateful escalation.
Fast Start
- Inspect the hosted subset via `/v1/sites/hosted`.
- Choose public adapters relevant to your sources.
- Call `/v1/sites/run` with structured args.
- Escalate to local runtime when public retrieval is no longer enough.
Next Action
Browse hosted adapters
Move from research to implementation by choosing the correct boundary: local runtime for real-session work, hosted API for public-safe retrieval.