December 10, 2025
Now streaming your prompts (and drama)
OpenRouter Broadcast
Broadcast beams your AI data — fans cheer, skeptics yell “not open”
TLDR: OpenRouter’s new Broadcast sends AI request logs to popular monitoring tools without extra setup. The crowd is split: convenience lovers cheer, while critics slam the “Open” name, demand on‑prem control, and question the Coming Soon list—plus rivals plug their own solutions. It matters for visibility and data control.
OpenRouter just dropped “Broadcast,” a beta feature that auto-sends your AI app’s usage logs—things like prompts, model replies, costs, and timing—into popular monitoring tools like Datadog and Langfuse, plus S3 and more. It even lets you tag traces with a user ID or session ID for easier debugging. On paper, it’s plug-and-play observability; in the comments, it’s pure chaos.
The loudest voice? “It’s not ‘Open’,” fumes one user, demanding an on‑prem option and dunking on the name. Fans of convenience clap back: fire-and-forget integrations are a dream when you don’t want to juggle a dozen keys. Cue the meme parade: “OpenishRouter,” “Big Brother of prompts,” and “fire‑and‑regret” for anyone blasting sensitive data into third parties.
Then came the eyebrow raise: someone noticed “WhyLabs” in the Coming Soon list and asked if it’s… shutting down, sparking a “who’s actually alive?” thread. Meanwhile, a rival strolls in with a grin—“Congrats!”—and drops a link to Svix Stream, basically saying, we do this too.
Bottom line: people love the convenience and analytics, but the debate is hot over transparency, vendor lock‑in, and who controls your data. Broadcast makes monitoring easy; the community wants it easier—and genuinely open.
Key Points
- •OpenRouter launched Broadcast (beta) to auto-send API request traces to external observability and analytics platforms without extra app instrumentation.
- •Users enable Broadcast via OpenRouter Settings > Broadcast, toggle it on, and add destinations; org admin rights are required for organizations.
- •Current destinations: Braintrust, Datadog, Langfuse, Weave, S3, and OpenTelemetry Collector, with many additional integrations listed as coming soon.
- •Traces include request/response (multimodal stripped), token usage, cost, timing, model info, and tool usage; optional user and session IDs can be included.
- •Destinations can be configured to receive traces only from specific API keys, and credentials for destinations are encrypted and stored securely.