Prepend 'https://op3.dev/e/' to each episode's audio enclosure URL in your RSS feed — for example, change 'https://cdn.example.com/ep1.mp3' to 'https://op3.dev/e/cdn.example.com/ep1.mp3' (omit the 'https://' from the original URL when constructing the prefixed URL)
No account, API key, or signup is required — OP3 automatically creates a public stats page for any show it measures once traffic begins flowing through the prefix
Multiple analytics prefixes can be chained: OP3 documentation confirms that existing prefixes do not need to be removed — append 'https://op3.dev/e/' before any existing prefix URL, resulting in a chain where each service records the request and redirects to the next
Verify the prefix is working by downloading an episode URL through the prefixed link and then checking your show's public OP3 stats page at 'https://op3.dev/show/{your-show-uuid}' — OP3 typically processes and displays downloads within a few minutes
Access aggregated download data programmatically via the OP3 public API — the API provides download counts, app breakdowns, and geographic data for shows measured by OP3; API documentation is available at op3.dev
Communicate to your audience that OP3 collects and publishes download data publicly — OP3's open data model means your download counts and app breakdowns are visible to anyone who looks up your show on op3.dev
Known gotchas
OP3 hashes IP addresses immediately using privately rotated keys and never stores raw IPs — but it does publish download counts and app breakdowns publicly, which may reveal more analytics data than you intend to share
The prefixed URL must preserve the full original URL including query parameters — if your hosting platform appends tracking query strings to audio URLs, ensure the full string including parameters appears after 'https://op3.dev/e/'
OP3 runs on a global CDN and is designed to be fast, but adding any redirect prefix introduces a small additional network hop — this is typically under 100ms globally due to OP3's edge infrastructure but should be noted for latency-sensitive delivery
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp