OMNIA / MODEL HUB

For suppliers — publish your own model capacity on Omnia

Apply for an account, review is done by an administrator, and after approval you manage your own upstream credentials, quotes and listings. Omnia is the intermediary, not the seller.

How the supplier side works

A supplier submits one application with its company name, contact, email and a self-chosen password. An administrator reviews the application. Approval creates a supplier account, a supplier profile and an initial verification record; the supplier then signs in at the supplier console with the password set at application time.

The supplier publishes its own quotes for a model, region, price, latency, throughput and service level. Buyers see those quotes, Omnia routes among eligible suppliers, meters the call and produces a recomputable bill. A buyer-side transaction fee of 5 percent is charged on each successful call.

  • Administrators review applications, freeze accounts, set the platform fee and arbitrate disputes.
  • Administrators do not enter upstream addresses or keys for an onboarded supplier and cannot change its prices.
  • Payment is not connected in the development build; settlement reports are produced per supplier but no funds are cleared.

What you control in the supplier console

The upstream base URL, authentication scheme, encrypted API key, custom headers, timeout and retry policy are entered by the supplier itself. Keys are encrypted at rest with authenticated encryption and can be rotated or removed by the supplier at any time. When a call is routed, the platform forwards it using those credentials and never displays the stored value.

Listings, per-million-token input / cached-input / output prices, region, model version, service tier and availability are all published and changed by the supplier. A listing can be suspended without deleting its history.

Verification and trust records, bound to the supplier entity

Admission checks compare model fingerprints and run capability, performance and availability tests. Listings are then sampled with scheduled probes. Fingerprint and probe records carry the supplier identifier, and the results are aggregated into one verification status and one five-level grade per supplier entity, not just per listing.

Grade changes are written to an append-only history and reduce routing priority, limit traffic or suspend a listing. The same records are visible to the supplier that owns them.

Bitcoin-anchored evidence

Audit records are batched into a Merkle tree and exported as offline-verifiable anchor packages. The SHA-256 digest of each package is submitted to public OpenTimestamps calendars in three stages: stamp (pending calendar receipt), upgrade (complete Bitcoin attestation with a block height) and verify (independent re-check against Bitcoin).

Only a 32-byte digest leaves the server; audit text and business data never go on a public chain. The proof establishes that the digest existed before a specific Bitcoin block. It does not prove that the content was true, and it is not a court ruling on admissibility.

Questions and answers

Do I have to send my upstream API key to an administrator?

No. After approval you enter it yourself in the supplier console. It is encrypted at rest, never shown again, and can be rotated or removed by you. The platform holds the encrypted credential only to forward the calls you accepted.

Can Omnia change my published prices?

No. Quotes and listings belong to your supplier account. An administrator can freeze a supplier or suspend a listing for enforcement, but cannot edit your prices or upstream credentials.

What does the Bitcoin timestamp actually prove?

It proves that the hash of an anchor package existed before a specific Bitcoin block was mined. It does not prove the underlying business data is accurate, and a pending calendar receipt is not yet a completed proof.

Apply to become a supplier

One application per company. An administrator reviews it; after approval you sign in at the supplier console with the password you set here.

Supplier console