WaveGen Bot
WaveGen is a content-repurposing tool. When a signed-in user pastes the URL of one of their own articles, WaveGen retrieves that single page on the user's behalf and turns it into social media posts. This page documents how that fetcher behaves so site operators can recognize, verify, and allow it.
What it is — and isn't
- User-initiated. A request is made only when a signed-in user explicitly submits a URL to repurpose. It does not run on a schedule.
- Single-URL. It fetches only the exact page the user provides. It does not crawl sites, follow links, or enumerate pages.
- Not a scraper. It does not harvest content in bulk, build a search index, or train models on retrieved pages.
- A signed agent. It acts on behalf of an end user, in the sense of Cloudflare's Signed Agent category.
User-Agent
WaveGen requests are sent with a User-Agent that begins with WaveGen/1.0 and links back to this page:
WaveGen/1.0 (+https://wavegen.ai/bot)How to verify it's really us
Every WaveGen request to a participating platform is cryptographically signed using Web Bot Auth (IETF HTTP Message Signatures). Requests carry Signature, Signature-Input, and Signature-Agent headers. You can verify a request against our published Ed25519 public key, served at our key directory:
https://wavegen.ai/.well-known/http-message-signatures-directoryBecause requests are signed, you can allow WaveGen without relying on IP ranges or an easily-spoofed User-Agent.
Allowing or blocking WaveGen
- To allow it: permit requests bearing a valid Web Bot Auth signature from
wavegen.ai, or allow theWaveGen/1.0User-Agent. - To block it: deny the
WaveGen/1.0User-Agent. We honor blocks and will not attempt to evade them on your domain.
Contact
Questions, or want WaveGen allowed or blocked on your domain? Email lu@wavegen.ai.