Hosted Read-Only Adapters for Public Research Sources

Why This Search Exists

Teams often want a uniform interface for public research lookups, but they do not need a full browser runtime for every one of those tasks. At the same time, they still want the same product to handle heavier local browser work elsewhere.

That creates a strong case for a hosted adapter subset that complements, rather than replaces, the local browser core.

Recommended Approach

Hosted read-only adapters provide that middle layer. They expose public-source lookups through a consistent API surface while avoiding the cost and confusion of unnecessary local browser control.

This works best when the adapter catalog clearly marks which adapters are hosted and when teams can switch back to local runtime for stateful tasks.

Key Takeaways

• Public research sources are strong candidates for hosted adapters.
• Consistency of naming matters across local and hosted tools.
• The adapter catalog should explain execution mode, not just function names.
• Hosted read-only adapters extend the platform without distorting the local browser core.

Fast Start

1. Check the hosted subset via `/v1/sites/hosted`.
2. Pick a public source adapter such as `arxiv/search` or `wikipedia/summary`.
3. Run it through `/v1/sites/run` with a simple JSON payload.
4. Move to the local runtime only when the workflow requires live browser context.