Public registry

OMLA Model Registry

Browse OMLA-licensed AI models. Each entry includes a unique wallet address, contribution splits, lineage declarations, and compliance state. Click any card for the full lineage graph and resolved splits.

How should I read each card?

Every card has five pieces of information at a glance:

  • Model name and optional domain tag — human-readable identification.
  • Compliance badge (top-right): green COMPLIANT = paid royalties recently; amber REPORTING = reports submitted, not yet paid; blue REGISTERED = no commercial use yet; orange DELINQUENT = overdue; red BLACKLISTED = removed from the ecosystem.
  • Description — the creator's one-line summary.
  • Wallet — the omla1… address that routes payments to this model. Truncated for display; click "copy" for the full string.
  • Lineage + contributors — whether this model builds on other OMLA models (upstream count) and how many contributors share this model's pool.

Click View details for the full lineage graph, resolved splits, creator identity, invocation snippet, and complaint/report links.

Verify a weight file

Paste a SHA-256 hash to check whether the exact weight bytes are OMLA-registered.

When would I use this?

Use this if you've downloaded a model from somewhere and want to know: (a) is it on the OMLA registry, (b) what does it claim about splits and license, (c) is it currently blacklisted? Commercial users should run this before deploying — it tells you exactly what royalty obligations attach to the bytes you're running.

You can compute the hash locally with sha256sum your-model.bin (or in PowerShell: Get-FileHash -Algorithm SHA256 your-model.bin). The hash never leaves your device unless you paste it here.

Register Your Model

Add your OMLA-licensed model to the public registry. Get a unique wallet address and enable automatic royalty splits.

Publish Your Model →
How the registry works end-to-end

The registry is the public surface over a PostgreSQL database hosted at Supabase. Every entry you see was registered by a creator who:

  1. Generated an Ed25519 keypair in their browser (we never see the secret).
  2. Produced a Bech32m-encoded omla1… address derived from the model's UUID.
  3. Signed the registration payload and submitted it through Supabase's row-level-security policies (gated by their email).

A single payment to any model's wallet flows recursively upstream through the lineage graph. Our resolve_splits() database function turns any model ID into a flattened list of terminal recipients and percentages. The 30%-of-greater-of-revenue-or-cost royalty rule is applied at the commercial user's end when they submit a quarterly usage report.

See the technical docs for the full spec, or the roadmap for what's still under construction.