Straight answers to what publishers actually ask. Not a sales page.
No. Every change is proposed and confirmed by you. We never write to your source catalog without explicit approval on each row.
ISRC (12 characters, CC-XXX-YY-NNNNN), ISWC (T-XXX-XXX-XXX-X), IPI (9–11 digits). We also cross-check that linked rows agree — e.g. two rows with the same title shouldn't carry different ISRCs.
The browser makes direct GET requests to https://musicbrainz.org/ws/2 for artist and work lookups. We rate-limit to 1 request/second per MusicBrainz's terms of service. No data is cached server-side; you control what gets assigned to your catalog.
None of those societies expose a public lookup API for ownership data. We flag items that need manual submission to those PROs rather than guessing ownership from unofficial sources.
The product works on CSV / JSON upload. A direct integration with DDEX-compatible catalog tools is on the roadmap — for now, most customers run weekly exports through us.
Split Verification can email each co-writer a confirmation link. They approve the final split in-browser (no account required), and the confirmation is timestamped in your audit log.
Cleaned CSV, CWR v2.1 registration packets (.v21), and a per-work audit PDF. CWR export is compatible with ASCAP, BMI, PRS, GEMA, SACEM, and STIM submission.
Uploads are processed in memory for the free audit. Publisher-tier catalogs are stored in our EU-based Postgres cluster (Frankfurt), encrypted at rest. Full data-deletion on request.
Yes — that's one of the most common use cases. Run your batch through TrapRoyaltiesPro before export, catch the rejects that would have come back from DSPs a week later.
You can mark a work as "needs manual review" and it stays in your dashboard until resolved. The CWR packet generator will skip unresolved works rather than exporting broken metadata.
Email us — we read every message.