For redistribution platforms

Integrate with OMLA

If you host or redistribute third-party AI models, this page summarizes how OMLA integrates with your platform. Three integration surfaces, declared currency preferences per creator, and publicly-visible conversion fees so nothing is hidden.

Full analysis: docs/commercial-integration.md.

Three integration surfaces

Registry lookup. GET /api/verify?hash=<sha256> — check whether a weight file is OMLA-registered, return license terms + wallet address. Upload-time dedup + license auto-population.
Inference webhook. POST /api/hoster/report — per-quarter signed volume report. Makes your platform eligible for hoster reimbursement if creators have opted in.
Currency declaration. POST /api/remitter/currency-config — declare which currencies you pay natively (Buzz, Credits, USD) and publicly-capped conversion fees for converting into creators' backup crypto.

Per-platform friction ranking

Model Marketplaces with Native Currency friction 2 · drop-in

Platforms that already have per-model license selectors, SHA-256 dedup on upload, and their own economy. Best surface: registry lookup on upload + declare your native currency. Most payouts stay inside the platform with 0% overhead; conversion fee only fires when a creator withdraws to backup crypto.

Creator-Paid Inference Platforms friction 3 · buy-in needed

Already pays creators a share of inference revenue — hoster carve-out maps cleanly onto existing economics. Registers USD as native currency. Good fit for the inference-webhook surface.

Inference Routers / Aggregators friction 3 · buy-in needed

Pass-through routers over multiple providers; per-request metering already exists. Platform credits as native currency means creators can accept credits without conversion. The routing fee stays orthogonal to the royalty.

Weight Hosting Platforms friction 4 · leadership buy-in

Primarily a weights host, not an inference host. Best surface: registry lookup at upload, adding omla-1.0 as a license identifier. Don't expect enforcement; do expect visibility.

Commodity Inference Providers friction 4 · unit-economics problem

Low-margin inference with no creator in the price stack today. Hoster fork only plausible under platform-wide creator mandate or EU AI Act Article 53 pressure. Currency mechanism softens but doesn't fix this.

Enterprise Cloud Inference friction 3 · worth courting

Catalog-style open-weight inference with enterprise compliance appetite. Potential early adopter for regulated-workload use cases.

Compute IaaS / GPU Rental friction 5 · not a fit

Infrastructure-as-a-service — the customer is the hoster, not the platform. OMLA talks to their customers directly.

Where you land depends on your platform type. If you're unsure which category fits, send us a note and we'll help map it out.

Reference integration snippet

Full example: a platform that runs inference for OMLA-registered models, wants to report volume, and pays creators in its own internal currency.

// 1. One-time: declare your currency config
await fetch('https://api.omla-ai.org/remitter/currency-config', {
  method: 'POST',
  headers: { 'Authorization': `Bearer ${PLATFORM_API_KEY}` },
  body: JSON.stringify({
    commercial_user_id: PLATFORM_COMPANY_ID,
    native_currencies: ['BUZZ', 'USD'],
    conversion_fees: [
      { from: 'BUZZ', to: 'BTC',  fee_pct: 30.0 },
      { from: 'USD',  to: 'BTC',  fee_pct:  2.5 }
    ]
  })
});

// 2. On upload: check if the weight hash is OMLA-registered
const { status, omla_address, license_terms } = await fetch(
  `https://api.omla-ai.org/verify?hash=${sha256}`
).then(r => r.json());
if (status === 'registered') {
  annotateModelPage(omla_address, license_terms);
}

// 3. At quarter close: sign + submit volume report for each hosted model
const payload = {
  hoster_claim_id: CLAIM_ID,
  quarter: '2026-Q2',
  inferences_count: counter.read('inferences'),
  tokens_processed: counter.read('tokens'),
  compute_hours: counter.read('compute_h')
};
const payload_hash = sha256(canonicalize(payload));
const payload_signature = ed25519.sign(payload_hash, HOSTER_SECRET);
await fetch('https://api.omla-ai.org/hoster/report', {
  method: 'POST',
  body: JSON.stringify({ hoster_claim_id: CLAIM_ID, payload, payload_hash, payload_signature })
});

Multi-currency: what the creator sees

Every creator declares an ordered currency preference list at registration. At least one entry must be a cryptocurrency and is marked as the backup. Payouts walk the list top-to-bottom and stop at the first currency the platform can pay natively. If none intersect, the backup crypto kicks in with the platform's declared conversion fee.

Creator prefs	Platform pays in	Result
BUZZ · USD · BTC*	BUZZ, USD	BUZZ, 0% fee
USD · BTC*	USD	USD, 0% fee
BUZZ · BTC*	USD only	BTC, USD→BTC fee (platform's declared rate)

* = backup crypto. See hosters page for the worked example and architecture §12 for the full resolution algorithm.

Talk to us

Platform-integration questions: coord@omla-ai.org. Engineering detail / API bugs: support@omla-ai.org.