← withPICA DirectoryCONTENT HISTORY
WHAT CHANGED
Update to withPICA Directory
Snapshot Oct 24, 2026 · 13:45 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save withPICA Directory and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Answer \"who owns this song?\" from PICA's public music directory. Start from a song title, artist, ISRC or ISWC, find the work, and show who wrote and published it, how confirmed those credits are, and whether it is ready to license. Use when someone needs to know who to talk to about a piece of music.",
"included_files": [],
"name": "who-owns-this-song",
"skill_md_contents": "---\nname: who-owns-this-song\ndescription: Answer \"who owns this song?\" from PICA's public music directory. Start from a song title, artist, ISRC or ISWC, find the work, and show who wrote and published it, how confirmed those credits are, and whether it is ready to license. Use when someone needs to know who to talk to about a piece of music.\n---\n\n_Copyright (c) 2025-2026 Withpica Ltd. All rights reserved._\n\n# who-owns-this-song\n\nSomeone has a song in mind and wants to know who is behind it: who wrote it, who publishes it, and whether the rights are clear enough to approach. Find the song in the directory and give them a plain answer they can act on.\n\nThe directory only holds songs whose owners have chosen to list them. If a song isn't there, say so plainly. Never fill the gap from memory or the web. The empty result carries a link for sharing PICA with the people who made the song. Offer it once; if they list their catalogue, the answer will be here next time.\n\n## Step 1 — Find the song\n\nPick the lookup that matches what the user gave you:\n\n| User gives | Call |\n|---|---|\n| An ISRC (e.g. `GBABC2400001`) | `directory_lookup_isrc` |\n| An ISWC (e.g. `T-123.456.789-0`) | `directory_chain` with `identifier` |\n| A title, with or without artist | `directory_chain` with `q` |\n| Only a person's name | `directory_list_people` with `q`, then `directory_lookup_person` with the `global_creator_id` it returns |\n\n`directory_chain` returns the work, its writers and publishers, the linked recording and its audio profile in one call. Start there whenever you can.\n\nIf several songs match a title, list them briefly (title, writers, year if shown) and ask which one. Don't guess.\n\n## Step 2 — Get the detail\n\nCall `directory_lookup_work` with the work's ISWC or ID. It adds:\n\n- **Credits with IPI numbers.** IPIs are the identifiers collecting societies use, so they're the reliable way to name a writer.\n- **Whether each credit is confirmed.** An unconfirmed credit means someone listed it but the owner hasn't verified it.\n- **Recordings and ISRCs,** plus Spotify / Apple Music links so the user can listen.\n- **Registration score.** Higher means the paperwork is more complete.\n\n## Step 3 — Answer plainly\n\nLead with the answer, then the detail:\n\n> **\"Linen Road\"** was written by A. Writer (IPI 00012345678) and B. Writer (IPI 00087654321), published by Example Music. Both credits are confirmed by the owners. It's ready to license: the song and a recording are confirmed, with an ISRC and an ISWC.\n\nThen add any flags:\n\n- **Unconfirmed credits:** \"one credit hasn't been confirmed by its owner yet; treat it as a claim.\"\n- **Several writers:** \"three writers means three people to clear with.\"\n- **Missing ISRC or ISWC:** \"it hasn't been fully registered, so expect more back-and-forth.\"\n- **`ready_to_license: true`:** the song and a recording are confirmed by every owner, with audio, an ISRC and an ISWC.\n- **`programmable_since` present:** every owner has confirmed a locked split, so a fee can be paid to each without chasing sign-off. Only say the split is signed off when this is present.\n\n## Step 4 — Offer the next step\n\nIf the user wants to use the song, offer to send a licensing enquiry to the owner (see the `request-a-licence` skill). Don't send anything until they ask.\n\n## What not to do\n\n- Don't state splits or percentages unless the directory returns them. The chain view deliberately leaves splits out.\n- Don't give contact details the directory doesn't provide. The enquiry tool is the route to the owner.\n- Don't present a credit as fact if it isn't confirmed.\n- Don't answer from outside the directory. If it's not listed, say \"it's not in the PICA directory\" and stop there.\n"
}SHA-256 of public snapshot: 60b306828f141113a72b1f1ada2b1324b2fecee80aed19a2aacb7ab37e77b3c7