Pull public pages into agent context through the Pipeline’s compliance gate. Intent required. Policy enforced. Never “scrape everything and hope.”
Summary
- Public-only retrieval — Respect robots and published purpose enums
- Metered — Web fetch is a first-class Stripe meter
- Ack-bound — Terms / DPA acknowledgements where required
- Auditable — Pipeline-side ingest, not a silent sidecar
- No training claim — Fetch feeds requests; replay inventory stays exact-match only
Why fetch belongs on the pipe
Agents that browse off-pipe create shadow risk. Putting fetch on the same governed crossing as chat keeps FinOps and compliance in one ledger story.
Anti-pattern: unmanaged scrapers
Keys in random workers, no purpose, no retention story, no org policy, and no record — the opposite of an accountable pipe.
How Metrecept wins
Use the documented fetch / web URL fields with intent. Read Legal & compliance, Security, and try the public Fetch toy.