Unofficial criticism and documentation site

chrismcmurtry.wtf

This page places Chris McMurtry’s public statements, ONCE’s published documentation, his former role at Pex, and ONCE’s current use of Vobile’s detector next to one another. It asks who benefits when one commercial chain can generate, distribute, detect, classify, and charge for AI music at scale.

This website is not affiliated with Chris McMurtry, ONCE, Pex, or Vobile. Facts are sourced and linked. Questions and interpretations are labeled as such. This is a one way informational site.

Currently documenting

Who profits from the AI music flood?

Chris McMurtry is a co-founder of ONCE, an AI-native music distributor, and an executive at the catalogue platform OpenPlay. He promotes AI-agent music distribution and says he used an agent he built to distribute more than 1,000 songs.

ONCE runs uploaded audio through Vobile’s AI Song Detector before submission. That classification decides whether ONCE bills the human rate or the higher AI rate.

McMurtry served as Vice President of Product at Pex from December 2021 until early 2024, leading data efforts for its Attribution Engine. He had already left when Vobile acquired Pex in April 2025, and when Vobile launched the AI Song Detector that November.

No single company owns the whole chain. But the links connect: music is generated, accepted at scale, inspected, classified, billed, and delivered. That may have an ordinary commercial explanation. The terms of it have not been published.

The public record

He built an API for the flood.

Complaints about “AI slop” usually target the person generating an individual song. That ignores the infrastructure required to turn isolated generations into thousands of commercial releases.

McMurtry announced that ONCE built an API and MCP layer so music could be distributed from AI systems such as ChatGPT and Claude. ONCE also invites users to generate music inside the platform before sending it through the same distribution pipeline.

“I distributed over 1,000 songs using an AI agent I built.” — Chris McMurtry, public social-media statement

This is not a distributor reluctantly accepting a new category of music. It is a company deliberately removing the human friction that once limited how quickly music could be prepared and released.

Distribution API statement ↗ ONCE MCP documentation ↗ ONCE product page ↗

The detector determines the price.

ONCE does not use Vobile’s detector merely as a neutral compliance check. The classification directly affects what the customer is charged. A track the detector flags is billed at double the human rate, whether it was generated inside ONCE or uploaded by the artist.

Human track 1 credit AI-detected track 2 credits

ONCE says the extra credit funds its Artist Compensation Fund, and published accounts of the platform put the amount routed there at roughly $0.92 of each AI dollar. That belongs in a fair account of the business. It does not answer what Vobile receives, retains, or learns from running its detector across ONCE’s stream of real-world uploads.

ONCE detection and billing guide ↗ Artist Compensation Fund ↗ McMurtry on the extra charge ↗

The company behind the detector

2021 December: Pex appoints McMurtry Vice President of Product to lead data efforts for its Attribution Engine.

2024 January: McMurtry leaves Pex for Artist Growth. In October he joins OpenPlay.

2025 April: Vobile completes its acquisition of Pex. November: Vobile launches the AI Song Detector.

Now ONCE, which McMurtry co-founded, routes uploads through that detector.

The dates matter, so state them plainly. McMurtry left Pex more than a year before Vobile bought it and nearly two years before the AI Song Detector shipped. He did not build the product ONCE now depends on, and nothing here suggests he did.

What remains is narrower and still worth asking about: a former Pex product executive co-founded a distributor that sends every upload through Pex’s successor technology. That is not evidence of improper conduct. It is a commercial relationship between two companies with overlapping history, and its terms are not public.

Pex appoints McMurtry ↗ McMurtry leaves Pex for Artist Growth ↗ Vobile acquires Pex ↗ AI Song Detector launch ↗ ONCE’s Vobile/Pex integration ↗

Call it training, validation, or improvement. The data still flows.

A company can say customer uploads are not used to “train” a model while defining that word narrowly enough to avoid the larger issue. An audio file may not automatically update model weights, but that does not mean the system learns nothing from being used.

Every ONCE upload exercises the detector against real music. The process produces a classification, confidence score, and operational evidence about what it recognizes, misses, or finds uncertain. At scale, those results can reveal new generators, false positives, edge cases, and changes in the market.

Whether the resulting work is called training, testing, calibration, benchmarking, quality assurance, internal analysis, or product improvement is beside the point.

ONCE’s terms allow uploaded content to be analyzed and processed for operating and improving its services. Vobile says it builds a database of content metadata for ongoing internal analysis and business development. Neither statement proves ONCE audio updates Vobile’s detector. Neither one closes the question.

ONCE terms ↗ Vobile privacy policy ↗

ONCE expects more AI music. The detector finds it.

McMurtry publicly praised Pex for detecting songs made with Google’s Lyria 3 shortly after its release. In the same statement, he said he expected more people to distribute Lyria 3 tracks through ONCE and that those tracks were already arriving.

“I’m expecting an increase of folks distributing Lyria 3 tracks through ONCE.app — and of course they’re already coming through.” — Chris McMurtry

The statement places both sides together without speculation: ONCE expects and accepts increasing volumes of newly generated AI music, while Vobile’s Pex technology supplies the means of identifying it and setting its price.

McMurtry’s Lyria 3 and Pex statement ↗

Content ID, for approved partners only.

ONCE’s own documentation states that delivering a release to YouTube Music does not enroll it in YouTube Content ID or create an Official Artist Channel, and that new access to both is currently limited to approved ONCE distribution partners.

Content ID is the mechanism by which a recording earns from user-generated video. Restricting new access to a partner tier, without publishing what qualifies an account for that tier, creates two classes of ONCE customer paying into the same platform for materially different results.

This is documented by the company itself, not inferred. What is missing is the reasoning and the criteria.

ONCE YouTube guide ↗ ONCE store selection documentation ↗

Direct questions

Questions Chris McMurtry and ONCE should answer

  1. What is the complete financial and technical relationship between ONCE and Vobile?
  2. Does ONCE pay Vobile per scan, per upload, under a flat agreement, or through another arrangement?
  3. What audio, metadata, classifications, confidence scores, and error information does Vobile receive?
  4. What information is retained after Vobile analyzes an ONCE upload?
  5. Is that information used for evaluation, validation, calibration, benchmarking, quality assurance, internal analysis, or future product improvements?
  6. Does the volume passing through ONCE increase the accuracy or commercial value of Vobile’s detector?
  7. Did any prior working relationship influence the choice of Vobile as ONCE’s detection provider, and was any alternative evaluated?
  8. Why build tools capable of distributing AI music at this scale while promoting technology designed to identify the resulting volume?
  9. Why is new YouTube Content ID access limited to approved partners rather than available to ordinary new releases?
  10. What qualifies an artist, label, or company as an approved partner, and can an ordinary account become one?
  11. What happens to an artist’s Content ID position if their distributor’s partner access changes again?

Why I looked

I am not pretending to be neutral.

A change to ONCE’s YouTube Content ID access disrupted a release plan I had spent a decade building. New releases were excluded while access remained available to approved partners.

That is why I looked more closely. It is not what readers are asked to rely upon. The public statements, product documentation, employment history, billing rules, and company relationship stand on their own, and every one of them is linked so you can check it yourself.

Primary sources