Who it’s for

Who is Pangea.ai’s data program for?

The owner program focuses on real software and development history. Keep client-owned work outside your proposed inventory unless you can establish the necessary rights. This is an asset-licensing route, not a paid coding job.

Our fit test: can you explain what each repository does, who owns it and why its history represents useful real-world development?

Get prepared

What should you prepare?

Start with a short inventory and an ownership check. The following preparation steps are editorial guidance, not additional provider eligibility rules.

  • Repository inventory: List purpose, languages, dates, tests, documentation and development history.
  • Ownership trail: Locate founder, employee, contractor and acquisition agreements. Flag client work and shared IP.
  • Sensitive material: Identify credentials, customer information and contractual restrictions; agree on handling before access.
  • Commercial comparison: Ask how eligible tokens are measured and how the final agreement differs from an online estimate.

Use our data preparation guide to organize the inventory before sharing sensitive material.

Revenue & payments

How does payment work?

Pangea advertises indicative owner rates of $100 per million source-code tokens and $40 per million history tokens. Actual value depends on analysis and buyer demand. Its owner FAQ describes payment within 15 days after buyer funds arrive.

The separate referral program advertises 15% of referred owner receipts, including re-licenses, with no advertised cap. It describes tracked links and payment within 15 days after fees are paid out. These are provider-published terms, not verified earnings.

Data Mining Masters uses an official untracked link. An owner-supplied referral URL is still needed; no enrollment or commercial relationship is implied.

Rights & control

Which licensing terms deserve attention?

Pangea describes non-exclusive licensing with ownership retained. Its FAQ limits withdrawal once a repository enters an active licensing process and flags uncapped responsibility for an incorrect ownership warranty. Read the full agreement before granting access.

For your review, distinguish permission to inspect a repository from permission to train on it. Record excluded files and dependencies so the scope can be checked later.

  • Who can receive the licensed material, and for which purposes?
  • What happens to existing licenses after withdrawal or termination?
  • Who resolves third-party rights, privacy and confidentiality restrictions?
  • Which acceptance criteria, deductions and payment deadlines will be written into the agreement?

Explore your options

When should you compare another platform?

Compare Patronus AI for a direct-buyer route involving code and company records, or Replay for a broader company-data discussion. Compare actual proposed scope and payment triggers, not headline percentages.

Good questions, clear answers

Questions before you apply

Is the 15% paid to the code owner?

No. The advertised 15% concerns referral compensation. The owner’s payment is governed by the licensing agreement.

Can I submit code written for a client?

First establish who holds the rights. Having repository access does not establish ownership or licensing authority.

Will every repository sell repeatedly?

No. Non-exclusive licensing permits repeat deals but does not create buyer demand. Budget only against accepted written terms.

Explore this opportunity

Take the next step

Review Pangea.ai’s current requirements and describe the assets you can offer. The provider confirms acceptance, scope and commercial terms.

Review Pangea code licensing

Direct link to the provider. Inclusion does not imply endorsement or a commercial partnership. Commercial disclosure.

Sources and editorial approach

Provider information checked on 18 November 2026. Practical checklists are Data Mining Masters’ editorial guidance. This profile is based on public information, not a firsthand transaction or a guarantee of acceptance or income. How we compare platforms.