Public registry

OMLA Model Registry

Browse OMLA-licensed AI models. Every entry is a public, signed manifest: model identity, lineage, the royalty split, payee wallets, and the payment pointers commercial users pay directly. Nothing here is access-controlled — the registry is the product.

Cover graphic: a grid of registered model cards with one highlighted — every model, on record
How should I read each card?

Every card gives you five things at a glance:

  • Model name and optional domain tag — human-readable identification.
  • Registry status badge (top-right): green ACTIVE = the manifest is in good standing and resolvable; orange REVOKED = the record's good standing was pulled (its manifest still resolves, and payers can see why); red DELISTED = removed from listings for fraud, legal, or DMCA reasons. Status is about registry integrity only — OMLA no longer tracks anyone's payment compliance.
  • Description — the creator's one-line summary.
  • Payee & split chips — how many payee wallets this model pays, and the share it retains (for example "retains 5%"). Everything else flows upstream through the lineage.
  • Lineage — whether this model builds on other OMLA models (upstream count). Original models retain 100%.

Click View details for the full public manifest: lineage graph, split table, payee wallets with payment pointers, the manifest hash, and a live "resolve $100" demo.

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 its manifest say about the split and payees, (c) what is its registry status? Commercial users should run this before deploying — the manifest tells you exactly where your self-assessed royalty flows.

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.

Publish Your Model

Publish your model's signed manifest: identity, lineage, your split within the license caps, and the public payment pointers commercial users pay directly.

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

The registry is a set of signed, static JSON manifests — plus this searchable view over them. Every entry you see was published by a creator who:

  1. Generated an Ed25519 keypair in their browser (we never see the secret).
  2. Derived a Bech32m-encoded omla1… payee address and attached public payment pointers — Lightning, on-chain, a Stripe link, PayPal.Me, or their own invoicing URL — to each payee wallet.
  3. Declared lineage and a royalty split within the license caps, then signed the whole manifest — the signature covers the split and the payment pointers.

When a commercial user owes royalties, they self-assess 30% of the greater of attributable revenue or run cost, resolve the model's published split recursively with the open omla-resolve algorithm — a fine-tune retains at most 5%, so most of the money flows to the original creators — and pay each payee wallet directly. OMLA serves the manifests and signed snapshots. It computes nothing per-payer, holds no funds, and keeps no records of usage, payers, or payments — because it never receives them.

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