An open standard
Podcast registry for any podcast platform
A shared lexicon for podcast publishing on the atmosphere. Providing a common language for shows, episodes, and subscriptions across hosts and players.
Get started
The core lexicons
Why pod.place
Built for movement
pod.place is an attempt to create a portable, open standard for podcast metadata — so show metadata, episodes, and other information don't need to be duplicated and can travel with the creator.
One schema, many surfaces
Indexers, apps, and directories all read from the same record format. No custom parsers per platform.
Creator-owned data
Switch hosts without re-uploading your catalog. Your show history and subscriber graph stay in your repository.
Open and extensible
Core fields are required. Everything else is optional. Anyone can propose additions. Add metadata as your product grows; well-implemented changes get adopted by the ecosystem.
Verification
Pointing back to the record
pod.place records point to domain names and webpages. We need a way for those
to point back to the record. This is done through a
.well-known route for shows.
Add a /.well-known/place.pod.show endpoint
to your show's domain. The response should be the AT-URI of your show record.
This confirms the link between the web presence and the atproto record, improving discovery and preventing impersonation.
Request
https://example.show/.well-known/place.pod.showResponse
at://did:plc:abc123/place.pod.show/rkey
Add a <link> tag in the episode page's
<head> that references its AT-URI.
HTML
<link rel="place.pod.episode"
href="at://did:plc:xyz789/place.pod.episode/rkey">Adoption
Being implemented by
Building a podcast app or platform? The standard is open for collaboration. Reach out on Bluesky to discuss implementation and help shape the spec.
FAQ
Questions
Common questions about pod.place, its governance, and implementation. If something is missing, ask us on Bluesky.
Why not just use RSS?
RSS is great for distribution, but it is pull-only, static, and controlled by the host. Host level records still need to be written by hosts and pod.place provides a standard way for this. pod.place intend to compliment and co-exist beside RSS.
How do I get started?
Start by creating records using the place.pod.show and place.pod.episode lexicons in your users' PDS repositories. Check out the schemas page for details. You can always reach out on Bluesky if you have questions or have feedback on the spec.
Can I extend the lexicons?
Yes, feel free to extend the lexicons. The validation enforces the core pod.place fields, others pass through. If adoption grows, we can collaborate on standardizing common extensions.
What about audio storage and encoding?
The lexicons focus on metadata, not audio encoding. Your platform decides whether to serve MP3, AAC, Opus, or something else. The audioUrl field is just a pointer. This keeps the standard minimal and universally adoptable.
Who maintains pod.place?
Initiated by @usaa.ma, pod.place has the goal of becoming a community-maintained standard. You are invited to participate in shaping the spec.
How can I get involved?
Best way is to start by implementing the standard, and then reach out with your feedback and suggestions either by opening an issue on tangled (link below) or reach out through Bluesky on @pod.place.