Terms of service

These terms govern the use of Heimdallm, an inference marketplace operated by Consensus Protocol LLC, through its website, its API and its command-line tool. Using any of them accepts these terms. The privacy policy states how data is handled, and pricing states what is charged.

The service#

Heimdallm is a marketplace and does not host the models. Independent providers run them. The marketplace publishes each provider's listing, measures its endpoints, routes a request to one and records the charge. A provider is responsible for what its endpoints return and for the declarations it makes about them — price, capability, data policy and compliance. The uptime, latency, throughput and tool-call figures on the site describe past traffic, and are not a commitment about the next request.

Accounts and keys#

• Sign-in is through Google or GitHub, and an account is created at the first sign-in. The identity provider account that signs in is the holder's to secure.
• An API key spends from the account it was created in, up to the ceilings set on the key, its workspace and the account. A key is shown once and stored only as a hash, so a lost key cannot be recovered, and a leaked key should be deleted at once. Whoever holds a key can spend with it.
• An organization is a shared account. Its admins decide who joins, which keys exist and what the account may spend, and its balance belongs to the organization rather than to a member.
• An account is deleted from its Privacy tab on a 48-hour countdown that can be cancelled. Deletion forfeits the remaining balance, as the privacy policy describes.

Credit and charges#

• Billing is prepaid. A deposit credits the balance, a request is held against the balance for a conservative estimate and settles to its actual cost, and a request that would exceed the spendable balance is refused before any provider is contacted.
• The price in effect when a request is dispatched is the price billed for it. Each provider sets its own prices, and the marketplace adds no markup to them. Pricing states the platform share the marketplace takes from a provider's gross.
• Credit is not refundable and cannot be withdrawn, referral credit included. A charge the marketplace got wrong is refunded as credit, with the reason recorded in the ledger.
• A stablecoin transfer is an ordinary blockchain transaction. Only the networks and coins the Credits tab lists are credited, a transfer on any other network cannot be credited or recovered, and credit posts after the transfer confirms. A transfer from an exchange cannot be matched to an account automatically.

Requests and the providers that serve them#

• The serving provider receives the body of the request, and the user field when one is sent. What that provider does with it is governed by its own declared data policy, privacy policy and terms, which its public profile links. Read them for any provider a request is pinned to.
• Routing preferences such as data_collection: "deny" and zdr: true restrict a request to endpoints whose providers declare the matching policy. A declaration is the provider's statement. A zero-data-retention declaration shows as approved only after the marketplace has reviewed the provider's deployment.
• The sender is responsible for the content of a request and for having the right to send it.

Acceptable use#

Acceptable use excludes attacking, probing or degrading Heimdallm, a provider's endpoints, another customer's machine or any third party; evading a rate limit, a spend ceiling or the metering of a request; and sending or generating content that is unlawful to send or generate. The marketplace may refuse a request, disable a key, stop a machine or suspend an account that breaks these rules.

Coding machines#

The coding playground starts a Linux machine of the customer's own, billed for the time it runs in whole minutes. An automated infrastructure-protection system watches the machine's behaviour — the programs it runs, where it connects and which categories of file it opens — to keep one customer's machine from attacking the platform or another customer, and never reads file contents or conversations. The machine's disk is destroyed with it; the durable copy of a workspace is the one the customer's own browser holds. Data & privacy describes this in full.

Providers#

These terms apply to anyone who lists models, in addition to the rest of this page.

• Listing. A provider applies, and the marketplace may approve, reject or suspend a listing. A listing is a model-list document at an address the provider controls, which the marketplace pulls on a schedule. A provider keeps its own infrastructure and sets its own prices.
• Declarations. Prices, capabilities, data policy and compliance claims must be true. The marketplace measures endpoints with real and probe traffic, withholds a capability that a check refutes, orders routing by measured health, and treats an unmeasured figure as absent rather than as a good result.
• Probes. The marketplace's own probes are ordinary requests to an endpoint and are billed at its listed price like any other traffic.
• Earnings. Each generation records the provider's gross at its listed price, the platform share — 10% by default — and the provider's net, in exact arithmetic. A refund to a customer does not reduce the provider's earnings.
• Statements and payouts. Each UTC calendar month closes into a statement of gross, platform share and net. A payout is made in USDC on Ethereum mainnet to a wallet bound to the provider's account that has made a credited deposit. An administrator settles the statement and records the transaction hash on it, and a statement cannot be paid while no qualifying wallet is configured or while payouts are held. A paid statement is not rewritten.
• Roles. Members of a provider can see its earnings and payout settings. A provider sees what its own endpoints did and never which account, workspace or key sent a request.

Suspension and termination#

An account can be deleted by its owner at any time. The marketplace may disable keys, stop machines or suspend an account or listing that breaks these terms or endangers the service, a provider or a customer. Ledger and usage records are kept, attributed to an opaque account id, after an account closes.

Availability and liability#

The service is provided as available and without warranty of any kind, to the extent the law allows. The marketplace does not warrant any provider's output, availability, latency or fitness for a purpose.

Questions#

Support lists the channels.