Developers

nine71 where your A&R already happens.

You have a dashboard and a process. We are not asking you to move. A drop box goes in a Notion page today with one embed, and the read on every demo is coming to your own Notion database next.

In a Notion page, today.

Notion's Embed block takes any URL. Paste this into the page your team opens every morning and there is a drop box in it. No key, no backend, nothing for your engineers to do.

Drop box in Notion

Live

In Notion: type /embed, press Enter, paste the URL. Replace your-inbox-slug with the last part of your workspace address on platform.nine71.ai.

https://nine71foundry.com/embed/?to=your-inbox-slug&theme=auto

A Notion embed is sized by the reader rather than by us, so drag it to about 620 pixels tall and it will not clip. The auto-resize on the script snippet cannot reach inside a Notion block. And this gets audio in: it does not yet put anything into Notion.

Artists drop a track, it lands in your inbox on nine71 scored against your own catalog, and the file never touches Notion or your site. The widget is a page on our origin. The Foundry developer page has the parameters, the live preview and the version for sites that can run scripts.

Every demo as a row in your database.

This is the one we are building. You connect nine71 once and pick a page. A database appears, and every demo that reaches your inbox becomes a row in it, measured and kept current as we learn more about the track.

Notion database sync

In build

Your views, filters, boards and assignees keep working, because it is an ordinary Notion database. These are the columns, and every one of them is something we measure rather than guess:

ColumnWhat it is
Track, ArtistAs the artist submitted them.
FitHow close the audio sits to your catalog, 0–100. Measured on the sound, never on the name.
Closest recordWhich of your own releases it lands nearest.
BPM, KeyMeasured from the file.
Loudness, True peakLUFS and dBTP off the master.
Released alreadyWhether the recording is out somewhere.
AI markersWhat the audio shows, stated as what it is and never as a verdict.
Sent beforeWhether you have already been sent this record under another name.
SoundA plain sentence about the record, written from the measurements.
Open in nine71A link straight to the track, to play it and see the full read.
ReceivedWhen it arrived.

What we can see is what you pick. Notion asks you which pages a connection may open, and only shows you pages you have full access to yourself. We get those and nothing else. Not your other databases, not your team's documents.

It reads one way. What you type in Notion stays in Notion. Editing a Fit number changes your dashboard and changes nothing about how we score anything, for you or for anyone else.

No date on this yet, and we would rather build it with one label than guess at the shape. If your A&R lives in Notion, say so at support@nine71.ai and you are that label.

Link previews

Needs Notion

Pasting a nine71 track link into a Notion page could unfurl it into a live card with the score and the read, the way a Figma or a Slack link does. We would like to build it.

Notion enables that for services it has approved, and there is no route we can take on our own. So it is on this page as something we want rather than something we are about to ship, and nothing else waits on it.

Not on Notion?

Any site, any dashboard

The same drop box embeds in Squarespace, Webflow, Wix, WordPress, Carrd, a hand-written page, or anywhere an iframe is allowed. One line either way, and the script version resizes itself and tells your page when a track lands.

Your own inbox, unchanged

If you already take demos somewhere (a form, an address, another platform), keep it. We are not asking you to switch off the thing your artists already know how to use.

An API, with one partner

There is no public API yet. A full-length track takes about twenty seconds to analyze, so a real one has to be submit-then-callback, and we would rather get that contract right with one design partner than publish a guess.

Questions.

Do I need a Notion integration or a key for the embed?

No. The embed is a page on our origin in an iframe, and the slug in it is the same public slug the Foundry app shows in its picker. Notion treats it like any other embedded URL.

Can I embed a single track's read instead of the drop box?

Not yet as its own embed. Today the drop box is the embeddable surface, and a track opens in Foundry. Tell us if a read panel inside your page is the thing you want and it moves up the list.

Will the sync fill in demos I have already received?

That is the plan for tracks we have measured, and it is worth asking for explicitly rather than assuming: a first sync that only starts from today is much less useful than one that brings your history.

What happens if I disconnect it?

We stop writing. Rows already in your database are yours and stay exactly where they are. Nothing on the nine71 side depends on Notion being reachable, so your inbox keeps working whether the sync does or not.

Does anything I do in Notion change my matching?

No. The sync writes one way. What teaches matching is what you do in nine71 itself, and we would design the Notion half of that with you before building it, not quietly.

Zapier, Make, Airtable, Google Sheets?

None of them yet, and they are the same project underneath. Once a demo can leave as a structured row, where it goes is mostly configuration. Notion is first because it is what we were asked for. Say which one you need at support@nine71.ai.