1 · Choose a label
everything in the ZIPs goes to this label2 · Drop ZIPs
audio is kept, so it can be re-embedded laterHow this is measured
Each ZIP is uploaded whole and unpacked by the analysis rig, which keeps every audio file, skips records already in this label, and computes both the DSP fingerprint and the MERT embedding. Duplicates are detected on a normalized key, so SGR100_-_Reelow_-_Conga-Ratulations and Reelow – Conga-Ratulations (Extended Mix) count as the same record.
“This ZIP mixes several labels” compares the prefix in each filename against the label name and parks everything that does not match in an Unknown label, keeping its audio, so it can be re-filed later. It reads nothing from the audio, so a correctly-attributed record named plainly is parked too. Tick it only for an export you know is mixed and know is named LABEL_Artist - Title.
Ingest queue
uploads stay here until the rig has unpacked themNothing queued yet.
Catalog
| Title | Artist | Label | Tempo | Added |
|---|
How this is measured
Search matches the normalized key as well as the title, so pasting a filename finds the record even when it went in under a different spelling.
Tempo is the measured BPM, rounded to a whole number. “holdout” marks a record deliberately kept out of its label’s profile; “mert” marks one that carries a MERT embedding.
The structure
Loading…
Access codes
invitations — revocable, never shown twiceA code is an invitation: the holder redeems it on Foundry with their own account.
| Code | Workspace | Issued to | Created | Last used |
|---|
How this is measured
A code no longer opens anything by itself. It is an invitation: the holder signs into (or makes) a nine71 account on Foundry and redeems the code there, which files them as an admin of the organization it names. Every dashboard is opened by an account — there are no user‑less sessions to hand around.
Revoking an invite code stops it being redeemed again. Revoking a member’s own grant row (the org · admin rows minted by redemption) closes their session within a minute: the gate re-reads this table on every request and caches the answer for 60 seconds.
“Last used” is the last request the gate saw on that grant; a code that was never redeemed reads “never used”.
Management requests
One organization asking to look after another’s workspace. We decide the label ones.
| Who is asking | To manage | Decided by | Note | Asked |
|---|
How this is measured
One organization asking to look after another’s workspace — a parent company over its labels, a management team over an artist. We decide the label ones. A request to manage somebody’s personal account is theirs to answer, and shows here only so the conversation is visible.
Approving here mints no code. The manager organization’s members already hold grants; approval widens what those open, so nothing new appears in the code table above and there is nothing extra to revoke.
Organization claims
Companies asking for their own side of nine71. Approving lets the person in.
| Who | Organization | Kind | Note | Asked |
|---|
How this is measured
Companies asking for their own side of nine71 — labels, agencies, management. Their inbox exists and is CLOSED from the moment they file; approving lets the person in, and opening the inbox to demos stays a separate, deliberate switch.
Approving mints the organization grant whose sessions open every workspace under the organization; it shows in the code table as org · role. Revoke stamps both halves.
overview
What this organization is
how we describe youThis sets the words used for your company across the console and on your public pages. It does not change what you can do here.
What each one means
Label — you have a workspace: an inbox demos arrive in and a catalogue your sound is measured from. Only a label is ranked against a track.
Parent company — you hold labels. Your rooms are theirs, and the organization screens aggregate across them.
Management — you look after artists rather than releases. The inbox and the rails are the same; the catalogue is not the point.
Manage an artist
with the code they sent youEnter the code the artist sent you; they approve it on their account.
How this is measured
An artist who wants you in their corner issues a management code on Foundry and sends it to you. Entering it here files your request — they approve or decline it on their account, and approval opens their inbox in this console.
Without a code the request is refused: an organization cannot knock uninvited, which is why there is no artist picker here. Whoever gave you the code told you the name.
Your catalog
The records this label is measured against.
All demos across
Every label in one queue. To listen or decide, open that label from Workspace in the sidebar.
How this is measured
Every label in one queue, so you can see where each demo belongs. To listen or decide, open that label from Workspace in the sidebar — its inbox is where triage happens.
Match is organization-only: how each demo scores against every one of your labels, with the label it was sent to outlined. The receiving label never sees this comparison.
How it arrived is one of three: sent straight to the label without running a match, tested on the label and then sent, or came up in the producer’s top matches. A demo sent straight is scored after the fact and may be low; nobody filtered it.
Uploads across
Tracks your team sent in, ranked against every label in the group. Each label sees only its own entry.
How this is measured
Match is how the track scores against each label's own catalogue — a percentile inside that label's spread, banded on cuts fitted across the whole corpus (high / middle / low). The label a track was sent to is outlined. A label with fewer than eight tracks reads “not calibrated” rather than a band.
An upload marked “all labels” was sent to the group as a whole: every label finds it in its own Uploads with its own score; nobody sees a sibling's.
Nothing here joins the catalogue. An upload is measured against a label's sound and never becomes part of it.
Add tracks
from this computerUpload codes
for people who have the folderA code opens nine71.ai/drop/ for whoever holds it. A code for the whole organization lets them pick a label, or all of them; a code for one label sends everything there.
Demos sent to
Add tracks
from this computerYour drop box
Put this on your own site and demos land in the inbox you are looking at. It is an iframe of our page, so the audio and the sign-in stay on our side — your site never handles either.
Changing any of these changes the snippet. Nothing is saved on our side — the settings live in the URL you paste, so you can keep two boxes with different looks on two pages.
Preview
The snippet
paste into your siteYour page can listen for it:
window.addEventListener('nine71:submitted', e => { … })
Keys and webhooks
what exists, and what does notThe drop box needs no key. It is our page in an iframe, so the sender signs in to us and uploads to us; the only thing your snippet carries is which inbox the track is for, and that is already public. A key pasted into the HTML of a public website is not a secret — it would be something to rotate and revoke that protected nothing.
A read API — your inbox, your scores, pulled into your own tools — is a different question, and that one does need a key because it reads things only you may see. It is not built. Say the word and it goes on the list.
Until then: Notion and the data integrations are on the nine71 developer page, and the artist-facing drop box is on the Foundry developer page.
Upload codes
for people who have the folderA code opens nine71.ai/drop/ for whoever holds it; everything they send lands here. Revoke it when the round is over.
Waitlisted
Held while you were paused. They arrive in your inbox when you reopen.
How this is measured
Held while you were paused — these arrive properly when you reopen. Listening from here is fine; nothing is delivered or triaged until the door opens.
Waiting is how long each send has been held. Reopening the inbox is the one act that delivers, and it delivers everything that waited.
catalog
Add records — drop audio here, or click to choose files
Your own releases. They join the catalog straight away; the fingerprint and your sound profile are rebuilt on our side shortly after, and scores do not move until they are.
Send your whole catalog
a ZIP, up to 2 GB — Refresh for progressNothing sent yet.
What happens to it
The archive goes straight to our storage from your browser; it does not pass through the page. Our rig unpacks it, keeps every audio file, skips records already in your catalog, and measures each one. Duplicates are caught on a normalized key, so SGR100_-_Reelow_-_Conga-Ratulations and Reelow – Conga-Ratulations (Extended Mix) count as the same record.
Your sound profile is rebuilt after that, on our side. Scores do not move until it is. The audio is kept, which is what makes a better measurement a re-run rather than a re-upload.
| Title | Artist | Tempo | Added |
|---|
How this is measured
A record counts toward your profile only if it carries a fingerprint and is not held out. “in profile”, “held out” and “no fingerprint” on a row say which of those is true of it.
Tempo is the measured BPM, rounded to a whole number; a dash means it has not been measured yet. Search matches the filename as well as the title and artist.