Postal DevelopersUse cases
Use cases
What people build on Postal, and which parts of the API each one uses.
Catalogue sync
Keep a label or publisher's system of record in step with Postal: uploads by URL, metadata patches, composer records, webhooks back.
Sync and pitching
Turn a brief into a shortlist with natural-language search and ship it as a playlist link.
Tagging pipeline
Auto-tag every upload, review low-confidence suggestions, write corrections back.
Reporting
Weekly engagement digests, top-track leaderboards, partner platform reporting.
AI assistant
Let Claude or Cursor work in a library through the MCP server.
Who builds on Postal
- Labels and publishers syncing a catalogue and split sheets with their royalty or rights system.
- Sync agencies and music supervisors searching a roster for briefs and sending shortlists.
- Producers with large libraries automating tagging, deduplication and clean-up.
- Tool builders adding Postal as a source or destination in their own product.
- Anyone with an AI assistant who wants to ask questions of their music instead of scrolling.