Public Content Enrichment With /v1/open and /v1/sites/run

Why This Search Exists

A generic URL fetch can capture metadata and text, but some sources benefit from source-specific adapters with structured arguments and cleaner outputs. Teams then need a way to combine both approaches without building two unrelated systems.

This is especially common in indexing, market intelligence, and knowledge pipelines.

Recommended Approach

The hosted layer can cover both sides: `/v1/open` for generic public retrieval and `/v1/sites/run` for structured source-specific calls. Together they cover a large share of public enrichment workloads without crossing into stateful browser control.

The local runtime remains available when a workflow later expands into interactive or authenticated browser steps.

Key Takeaways

• Public enrichment often needs both generic and source-specific retrieval.
• Hosted open and hosted adapters complement each other well.
• Structured adapter calls reduce normalization work for known sources.
• Keep the local browser runtime for stateful escalation paths.

Fast Start

1. Use `/v1/open` for generic public page retrieval.
2. Use `/v1/sites/run` for known public-source adapters.
3. Combine outputs in the same enrichment pipeline.
4. Escalate to local runtime only when browser state becomes necessary.