domain: supercast.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request API access from Supercast support — it's enabled per-account rather than fully self-serve
Once enabled, generate a Bearer token from the dashboard's Advanced Settings > API section
Call the Subscribers resource to list, create, or update subscribers, addressable by UUID or email
Use the activate/deactivate operations on a subscriber to control their podcast feed access
Cross-reference the Episodes and Creators resources if you need subscription context beyond the subscriber record itself
Known gotchas
Whether API access requires manual enablement or is fully self-serve from Settings > Advanced > API could not be confirmed either way from current docs — verify current onboarding flow before assuming either path
Confirm the exact base path and version prefix (docs point to api.supercast.tech) before building, since it wasn't independently verified via a direct fetch
Subscriber operations are addressable by either UUID or email — pick one consistently to avoid targeting the wrong record on an ambiguous email match
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?