llms.txt
+27 −14
− # withPICA — music catalog management for artists, songwriters, labels, and publishers− > the memory for your music. catalog intelligence for artists, songwriters, producers, composers, labels, and publishers.− pica manages music catalog metadata, recordings, credits, agreements, and rights registrations. it enriches catalog data from global sources (ISNI, MusicBrainz, MLC, Spotify, YouTube, Discogs), reconciles identifiers across the industry identity graph, and produces registration-ready exports for collection societies and sync.− pica is mcp-first. the primary experience is: your own AI client (Claude Desktop, ChatGPT, Cursor, Gemini, Grok, or any MCP-compatible tool) connects to pica and does catalog work conversationally. your AI subscription stays with the provider — pica never sits between you and your AI, never charges for AI usage, and never marks up provider pricing.− writes — creating works, updating credits, submitting splits, requesting enrichment — happen through the model context protocol. there is no public REST API for writes. agents connect via the @withpica/mcp-server npm package (stdio transport) or the HTTP endpoint at https://withpica.com/api/mcp. the public directory additionally supports read-only REST at https://withpica.com/api/public/directory/* alongside its own MCP server (@withpica/mcp-server-directory), and each published artist site expo− - free runway: hold your whole catalog, register your works, browse and search — free, no card, no countdown. your first works run through deep-processing (the audio analysis) free too.− - resident: one small flat fee a month, generous deep-processing included, priced for where you are rather than converted from pounds — ~£5/mo developed · ₦7,500 nigeria · ~3,100 CFA · ~60-75 GHS. a fee that asks the same of you in lagos as it does in london.− - heavy users: past the included allowance you pay a little per work. pica never takes a cut of what your music earns.− - looking after other people's catalogues? a manager, publisher, label or admin pays £5.00 a month for each catalogue it looks after, plus £5.00 for its own. your first 3 clients are free for 60 days from the day each one accepts, with no card. your clients never pay while you do, and they stay the owners of their catalogues. one catalogue with more than 5,000 works? talk to us.− - authoritative figures live at [pricing](https://withpica.com/pricing); nothing here is a quote.− - machine-readable: [pricing.md](https://withpica.com/pricing.md) — the same figures as a table, computed from the same constants the till charges. an agent should read that, not this section.− - AI: your client, your subscription. pica is mcp-first — your AI lives in your own client and your AI subscription stays with the provider; pica never hosts AI or marks up provider pricing.− - BYOC (bring your own credentials): applies to cloud storage. organisations can connect their own AWS S3, Google Cloud Storage, Azure Blob, Cloudflare R2, or Backblaze B2 bucket so audio, media, and documents live in their own infrastructure. pica's default storage is included out of the box.− categories: catalog management (works, recordings, people, credits, agreements, releases), enrichment (ISNI, MusicBrainz, MLC, Spotify, YouTube, Discogs, Wikidata), identity-graph traversal (by IPI, ISNI, IPN, ISWC, ISRC), exports (CSV, JSON, PDF, CWR-mapped registration bundles, industry-ready bundles, Catalog Asset Report), audio (upload, BPM/key/energy analysis, Whisper transcription, ACRCloud fingerprinting), notifications, licensing enquiries.+ # withPICA — the record of your songs that everyone agrees on · music catalog management+ > who wrote each song and their shares, the recordings and who plays on them, who owns the master, the releases and the audio: one record, confirmed by the people on it. for songwriters, artists, producers, labels and publishers.+ pica holds the record of your songs. you add what you know, and each writer, performer and owner confirms their own part. pica shows what is confirmed, agreed, disputed or still missing.+ when you ask, pica looks a song up in public sources (MusicBrainz, the MLC, Spotify, Discogs, ISNI, YouTube) and shows what it finds as "found" until a person accepts it. it does not overwrite what people have entered. it makes exports for registering works with your collection society, and for sync and release.+ pica sits next to the tools you already use: your distributor, your society, your publisher or admin. it does not distribute music or collect royalties, and it never takes a cut of what your music earns.+ pica is AI-first. you work through the AI you already use (ChatGPT, Claude, or any MCP client) in your own words, and use the website to check and approve. your own AI client (Claude Desktop, ChatGPT, Cursor, Gemini, Grok, or any MCP-compatible tool) connects to pica and does catalog work conversationally. your AI subscription stays with the provider — pica never sits between you and your AI, never charges for AI usage, and never marks up provider pricing.+ writes — adding songs, updating credits, submitting splits, asking for a lookup — happen through the model context protocol. there is no public REST API for writes. agents connect via the @withpica/mcp-server npm package (stdio transport) or the HTTP endpoint at https://withpica.com/api/mcp. the public directory additionally supports read-only REST at https://withpica.com/api/public/directory/* alongside its own MCP server (@withpica/mcp-server-directory), and each published artist site exposes + ## guides+ plain answers to common catalogue questions, each with a short FAQ:+ - [how to get everyone on a song to agree the splits before release](https://withpica.com/guides/agree-splits-before-release)+ - [how to audit your catalogue for missing ISRCs, ISWCs and unregistered songs](https://withpica.com/guides/audit-catalogue-missing-codes)+ - [how to keep splits, agreements and registrations in one place](https://withpica.com/guides/splits-agreements-registrations-one-place)+ - [how to get collaborators to confirm their own splits](https://withpica.com/guides/collaborators-confirm-their-splits)+ - [how to manage your music catalogue with ChatGPT or Claude](https://withpica.com/guides/manage-catalogue-chatgpt-claude)+ - [split sheet template](https://withpica.com/guides/split-sheet-template)+ ## comparisons+ - [pica vs TuneRegistry](https://withpica.com/alternatives/tuneregistry) — TuneRegistry submits registrations to US organisations; pica holds the record the people on a song confirm. many use both: agree the facts in pica, register through TuneRegistry or a society.+ ## free lookups (no account)+ these search only the pica directory: songs and writers their owners chose to list. a miss means "not listed", not "doesn't exist".+ - [ISRC lookup](https://withpica.com/lookup/isrc) — a recording, the song behind it and its credits+ - [ISWC lookup](https://withpica.com/lookup/iswc) — a song, its writers and credits+ - [IPI lookup](https://withpica.com/lookup/ipi) — a listed writer and the songs they are credited on+ - free to start: hold your catalogue, ask the people on your songs to confirm, and export. no card.+ - pica never takes a cut of what your music earns.+ - AI: your client, your subscription. your AI subscription stays with the provider; pica never hosts AI or marks up provider pricing.+ - BYOC (bring your own credentials): applies to cloud storage. organisations can connect their own AWS S3, Google Cloud Storage, Azure Blob, Cloudflare R2, or Backblaze B2 bucket. pica's default storage is included.+ categories: the catalogue (works, recordings, people, credits, splits, releases, agreements), confirming and disputing credits, lookups on request (ISNI, MusicBrainz, MLC, Spotify, YouTube, Discogs, Wikidata), search by code (IPI, ISNI, IPN, ISWC, ISRC), exports (CSV, JSON, PDF, CWR-mapped registration files), audio (upload, BPM/key/energy analysis, Whisper transcription, ACRCloud fingerprinting), notifications, sharing, licensing enquiries.