Terms of service
- Service operator
- AgentRanking
- Jurisdiction
- local-vm
- Contact
- [email protected]
These terms govern use of the AgentRanking marketplace, workspace console and API. The operator may update this page when the service or legal requirements change. The current version is the text published here.
Service description
AgentRanking provides a control plane and OpenAI-compatible gateway for inference supplied by independent providers. Supply deployments execute approved model revisions; the control plane is not itself a model fleet. Availability, latency and reliability figures describe observations, not guarantees, and are shown only when measured.
Accounts and workspaces
You are responsible for activity under your account, workspaces and API keys. Keep credentials confidential. API keys share the workspace balance and cannot approve payouts or change membership. Removing a member takes effect server-side; cached client roles are not authoritative.
Prepaid credit and charges
Commercial amounts are integer microdollars. Deposits are accepted only in the native assets and networks shown by a current deposit invoice. An invoice is not credit; credit is posted only after the server verifies the transaction and the applicable finality policy. Admission reserves the maximum accepted exposure before dispatch.
Balances may include available, held, refundable and nonrefundable components. The billing ledger is the authoritative record. The interface never displays an optimistic credited balance or a fabricated successful payment.
Listings, inference and endpoints
Each listing binds an eligible deployment to an immutable rate-card revision, API profiles, assurance label and data policy. The gateway selects eligible supply and settles the exact metered charge from the workspace balance.
Shared routing and reserved-capacity endpoints are different commercial modes with different billing. Reserved capacity is exclusive runtime capacity, not ownership of a machine or arbitrary device access. Cancellation settles delivered output truthfully and does not erase a receipt.
You must hold the rights required for prompts, uploads and generated outputs, and comply with each model's published license. Data exposure is bounded by the accepted policy; stored Responses retention is opt-in and expires.
Payouts and settlement
Supply earnings are a payable, separate from customer prepaid credit. Pending earnings mature under the operator's risk and maturity policy. Crypto and fiat payout rails are distinct; a rail shown as unavailable is not a promise of instant settlement.
No treasury private key, mnemonic or transaction-signing daemon is stored on the application server. Customers and providers remain responsible for their own wallets and keys.
Availability and limits
Credit, concurrency, queue length, contract duration, payload size and traffic are bounded. Exceeding a configured limit produces an explicit error. Maintenance, chain outages and upstream price-feed outages can disable specific functions while other read-only surfaces remain available.
Receipts and tax
Itemized receipts and exports identify the price revision, units, cost, chain transaction and refund linkage where applicable. A receipt is not represented as a jurisdiction-compliant tax invoice unless operator tax configuration provides the required fields.
Suspension and termination
The operator may suspend accounts, API keys, provider devices or payouts for abuse, security risk, unpaid exposure, legal requirement or violation of the acceptable-use policy. Where practical, the reason and available recovery path are recorded. Workspace deletion is not self-service today; the workspace owner must contact the operator, who verifies ownership and applies the retention rules below.
These terms are operator-owned product content. They do not create an SLA, a tax representation or a promise of unmeasured capacity.
