Organization verification and tiers

Verification does two separate jobs, and the path you need depends on which one you are after.

• Being allowed to act — create Campaigns, fund them, buy data. An email address and a payment method carry most of this.
• Being allowed to be named — publish under your Organization's name where Contributors see it. This needs proof that you control the Organization, not proof that the Organization exists.

A business-registration document establishes the second job poorly: it is a public record anyone can obtain. Control of a domain or of an Organization's GitHub or Hugging Face account is what establishes it, which is why those paths exist alongside verification.

What each level establishes

The levels are not a single queue. An Organization can connect a GitHub Organization without submitting KYB, or submit KYB without connecting anything.

Allowed email domains

1. Open Settings → Domains.
2. Add the email domain your colleagues use.
3. Save.

Colleagues signing in with an address on that domain can then join without an individual invitation.

Public email providers are rejected. An allowed domain is a convenience for joining; on its own it is not evidence of control of the Organization.

Connecting a GitHub or Hugging Face Organization

1. Open Settings → Verification.
2. Select the provider and complete the sign-in.
3. Select the Organization to connect.

You must hold an admin role in that Organization on the provider. The connection records the role you held and whether the provider's own verified badge was set when the check ran, and both appear on Trust.

This attests control of that provider account. It does not attest the existence of a legal entity, and the two are shown separately.

If your Organization is already verified on GitHub or Hugging Face, this path reuses that work rather than repeating it.

Organization verification (KYB)

1. Open Settings → Verification.
2. Enter the Legal entity, Registry / tax number, and Registry country.
3. Upload supporting documents — a business licence, registration, or ownership records. Documents are stored privately and are opened only by reviewers.
4. Select Submit for review.

The Organization moves to In review. A reviewer decides it, and the outcome appears on the Verification tab.

An approved review records an assurance level on the Organization. A declined review records the reason, and you can correct the submission and submit again.

Common reasons a review is declined

Verified Organization

Verified Organization is a separate designation from KYB, and KYB alone does not produce it. It also requires an Organization reputation tier that has been sustained rather than briefly reached.

An Organization that completed KYB recently and has no reputation history yet is verified for KYB and is not a Verified Organization. Both states are shown on Trust.

What the verification mark means

The mark shown beside an Organization's name reflects Organization verification (KYB) at a sufficient assurance level. It does not reflect an allowed email domain or a connected external Organization; those appear as their own evidence on Trust.

Read each item's own status. A connected GitHub Organization does not imply KYB, KYB does not imply Verified Organization, and none of them imply eligibility for royalty compensation.

Royalty compensation

A Campaign's compensation model determines how Contributors are paid. A royalty or hybrid model pays Contributors from downstream licensing of the resulting data rather than from a fixed Reward alone, and Contributors accept their own royalty agreement before joining such a Campaign.

Selecting a royalty or hybrid model requires an agreement signed by your Organization's legal entity. This is the one capability where entity details are a requirement rather than a supporting signal: a royalty relationship names a counterparty, and it cannot name an Organization that has not signed.

This is not open yet. It becomes available when the Organization agreement is published for signature; until then a royalty or hybrid model cannot be selected regardless of the Organization's other verification state. Fixed-Reward Campaigns are unaffected.

If you are planning a royalty Campaign, completing Organization verification (KYB) first is useful — the same entity details are needed — but it is not sufficient on its own.

Paths that are not open yet

Listed so that their absence is legible rather than looking like a fault.

Troubleshooting