A SourceX partner should not invent a buyer relationship: a relationship claim evidence register that sorts every "we work with" line by the relationship it asserts, the record that would prove it and who may say it, and shows why buyer claims fail every row

Short answer

Make no buyer claim at all. SourceX does not publish the names of the organizations that license its datasets, its sample partner agreement says an Acquisition Partner's identity may stay confidential, and the program terms say partners never receive confidential buyer information. So a partner who writes "we place data with AI labs", shows a lab's logo or hints at who buys has either invented a relationship or repeated something it should not hold. Publish only the relationships you can document.

Visual briefFull-size diagram
A relationship diagram: your firm links to the company with a green line labeled your relationship and to SourceX with a green line labeled signed agreement; the company links to SourceX, its counterparty; SourceX links to an Acquisition Partner behind a dashed wall marked identity confidential; an orange dashed arc from your firm to the Acquisition Partner is crossed out and labeled no link to claim.
The relationships a partner can document, and the one it cannot. No real organizations are shown.

That leaves two: your relationship with each company's CEO, and your relationship with SourceX, which you may state in public once SourceX authorizes it in writing. This guide is for whoever reviews partner content, including copy an agency drafts on your behalf, and it gives that reviewer a register for sorting every relationship line before it goes out.

Why a partner cannot know who the buyer is

The program is built so that the buyer's identity never reaches you. Four published documents say so in their own words.

  • The terms, section 7: "Partners never receive access to other partners' records, applicant documents or confidential buyer information."
  • The sample agreement, section 1.9, says an Acquisition Partner "may be an AI lab, a large enterprise AI developer or an organization working with those users. Its identity and contract may remain confidential." Section 1.6 lists "buyer identities" among confidential information, and section 4.6 adds that "SourceX need not reveal confidential Acquisition Partner names, contracts, prices, margin or full acceptance evidence."
  • SourceX's investor overview lists "Acquisition Partner anonymity" among its features: "Labs can source data without revealing their roadmap or identity to the market."
  • SourceX's FAQ describes who sits across from the company: "SourceX is not a marketplace or broker that finds Acquisition Partners for a company's data: it is your direct licensing counterparty from assessment and agreement through preparation, delivery and payment."

Put together, a buyer claim has no legitimate source in a partner's hands. If it is a guess, it is invented. If it came from somewhere, it is confidential information that should not be repeated. Either way it comes out.

The claim, the audience and the commercial connection

Buyer claims usually start with a fair question. A CEO asks who would actually use the company's records, and a partner who wants to sound credible reaches for a name. Agencies reach for logos, because a strip of recognizable marks is what "credible" looks like on a landing page. Recruiters of other introducers reach for demand stories.

Each audience is misled differently. A CEO may decide to talk, or to sign, because of a buyer it believes is waiting. Another professional may join the program on the strength of relationships that do not exist. Your own clients learn something false about what you do. And the commercial connection raises the stakes: you could be paid if a company you introduce licenses data, so a credibility claim that moves a CEO also moves money toward you.

The structure itself is the honest answer. The company signs its Master Supplier Licensing Agreement and its Dataset Deal Confirmation with SourceX, and SourceX pays it. The company never contracts with "the buyer", and the partner never stands between them. The plain explainer on data buyers and the one on what a referral partner is are the pages to link when a reader wants the roles spelled out.

The relationship claim evidence register

Every relationship line in partner content asserts a link between two parties. The register names that link, the record that would prove it and who is allowed to say it.

Claim as drafted (Illustrative)Relationship it assertsRecord that would prove itWho may publish itVerdict
"We take part in SourceX's referral program"Your firm and SourceXYour signed Channel Partner AgreementYou, once SourceX authorizes it in writingPublish after authorization
"We are SourceX's official partner"A status beyond the programNone; section 7.1 says participation creates no partnershipNobodyRewrite as the first row
"We introduce companies we know to SourceX"Your firm and companies, in generalYour relationships, and each CEO's yesYou, naming no company without its CEO's consentPublish in general terms
"Our clients license data to AI labs through us"Your firm as a seller to buyersNone; companies license to SourceXNobodyRemove
A lab's name or logo anywhere on the pageYour firm and a buyerNone you could hold, under section 7 of the termsNobodyRemove
"SourceX's buyers include..."SourceX and named buyersConfidential under the agreementSourceX alone, and it publishes no namesRemove
"Your records could train the next frontier model"An implied buyer and an implied useNoneNobodyRemove; quote SourceX's own description
"We know what buyers want this quarter"Your firm and buyer demandNoneNobodyRemove; link who qualifies
"Companies we introduced have licensed data"A completed outcomeDeal records you do not see in full; SourceX says neither side publicizes a dealNobody without written consent from SourceX and the companyRemove
"SourceX licenses business data directly from companies and pays them for it"SourceX and companies, in SourceX's wordsSourceX's own FAQAnyone who quotes it exactly, with a linkPublish

Method note. The register applies SourceX's terms (version 2026-10-22.2, since replaced by version 2026-11-04, sections 1, 7 and 9), sections 1.6, 1.9, 4.5, 4.6 and 7.1 of the sample Channel Partner Agreement, SourceX's FAQ, investor overview, process page and trust page, all read on 2026-10-28. The claims in the first column are invented examples of common drafts, not quotations from any partner. Nothing here measures how often such claims appear; no such data has been published.

The outer limit on describing demand. If a reader asks who uses licensed datasets, the most a partner can say is SourceX's own FAQ sentence, quoted and linked: "SourceX's customers are AI labs, model developers and research teams around the world." Add nothing to it. A "such as" list, a logo or a knowing look turns a published category into an implied buyer.

Names that are only references. SourceX itself is careful with names it does not partner with. Its trust page lists software it commonly sources from and says the names "are shown for reference only and do not imply a partnership or endorsement." A partner page deserves at least that care, and the safest version of a lab's name on a partner page is no version.

The FTC's impersonation rule, at 16 CFR 461.3(b), addresses materially misrepresenting, directly or by implication, "affiliation with, including endorsement or sponsorship by, a business or officer thereof." Whether it reaches a particular line of partner copy is a question for your counsel. The register is built to keep you well away from that question.

Check evidence, scope, timing and permission before anything is published

Run four checks on every line the register lets through.

  1. Evidence. You hold the document behind the claim: the signed agreement, SourceX's written authorization, or the CEO's own message agreeing to be mentioned.
  2. Scope. SourceX's authorization covers the wording and channels you sent it. A new channel or a reworded line is a new request; the published terms do not describe what an authorization covers, so SourceX decides.
  3. Timing. Section 9 of the terms gives the agreement a one-year term that renews only with fresh acceptance. "We take part in SourceX's program" becomes false the day yours lapses, so it comes down that day.
  4. Permission. The company's CEO decides whether the company's name appears anywhere. SourceX decides whether its name appears beside yours as a partner. Neither decision is yours to make for them.

Payout lines in the same piece go through the payout claim checklist as well; relationship and money claims tend to arrive in the same paragraph.

When a CEO asks who would buy the data

Answer without a name, and without implying one. Illustrative wording:

"I don't know, and the program is designed so that I can't. SourceX would be your counterparty: it signs with you, prepares the data and pays you. It keeps the identity of the organizations it licenses to confidential. If that matters to your decision, ask SourceX directly what it can share with you."

That answer loses nothing a CEO should rely on. A partner who names a buyer to win a meeting has handed the CEO a reason to sign that may not exist, and the CEO will remember who said it. If the CEO later wants to name a buyer in a press release or a board deck, the guide for a founder who wants a public buyer name covers what stays confidential and who decides.

If you already know an AI developer, or think you know a buyer

Some partners do know AI teams: as advisors, investors or former employees. That knowledge stays in its own lane. Never connect a team you know to SourceX, to a dataset or to a company you introduce, in content or in conversation. A rumor about who licenses from SourceX is not a fact to repeat, and a fact learned in confidence is not yours to use.

If an AI team you know is itself looking for data, that is a separate route with its own front door; the two-lane route map keeps buyer contacts and supplier introductions apart.

Correct a buyer claim that is already out

  1. Remove it at the source, and add a dated correction note where it appeared.
  2. Find every copy: agency drafts, decks, bios, email signatures, cached PDFs and pinned posts.
  3. Tell the people who relied on it. Any CEO who heard the claim from you hears the correction from you, plainly.
  4. Brief whoever wrote it. If an agency drafted the line, give it the register and require that every relationship line cites its record.
  5. Log it against the piece, with the date and what replaced the line.

Do not replace a removed claim with a vaguer version of the same idea. "Trusted by leading AI teams" is still a buyer claim.

Where the register falls short

  • Design implies relationships too. A "trusted by" logo strip, a lab's colors in a slide template or a photo at a lab's event can assert what no sentence says. Review the rendered page, not just the copy.
  • Conversation is not covered by publication review. The same rule holds on a call or at dinner, where no reviewer is present. Train the people who speak for you.
  • Bios carry history. Former employers may appear in a bio; they may not appear as a route to buyers.
  • It is not legal advice. Whether any rule applies to your content, and what it requires, is for your own counsel.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Clear your content of buyer claims first, then register as a partner and ask SourceX in writing before you name it publicly, let who qualifies describe fit in SourceX's words, and keep the program terms as the only source for what the program does.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

May we say that AI labs use data licensed through SourceX?

Only by quoting SourceX's own FAQ sentence, word for word and linked, that its customers are AI labs, model developers and research teams around the world. Add nothing to it: no names, no logos and no such-as list, because SourceX keeps Acquisition Partner identities confidential.

One of our consultants used to work at an AI lab. Can their bio say so?

Their employment history is theirs to state. What the bio must not do is connect that lab to SourceX, to your referral work or to any company you introduce, because no partner can know who licenses a given dataset.

A CEO says they will only talk if they know the buyer. What now?

Say you do not know and cannot find out, because partners receive no buyer information. The CEO can ask SourceX directly what it is able to share; whatever the answer, it comes from SourceX to the CEO, not through you.

Sources

  1. refer.sourcex.si/terms
  2. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  3. sourcex.si/faq
  4. sourcex.si/investors
  5. sourcex.si/how-it-works
  6. sourcex.si/trust
  7. ecfr.gov/current/title-16/chapter-I/subchapter-D/part…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment