Terms of service

These terms govern your use of the Wuraw website, inference API, app surfaces and SDK (together, the service). They are between you — the person or entity sending requests, including any autonomous software you operate — and the entity operating the service.

If you deploy an agent that sends requests, you are responsible for what it sends and what it spends. Software acting on your behalf binds you exactly as your own keystrokes would.

Wuraw is a router. It presents one OpenAI-compatible endpoint over a catalog of models served by independent upstream providers across Dolphin, Surplus, AntSeed tiers, and it settles metered requests in USDG on Robinhood Chain.

We do not train, host, own or control the models. We are not the author of any completion. Where a model is available from more than one provider, the routing policy and observed health determine which one serves a given request, and the choice is disclosed in the response.

The service issues no accounts, no API keys and no credentials of any kind. You are not required to register, verify an identity, or be resident in any particular place. Consequently there is nothing for us to suspend at the level of a user, and no login for you to lose.

The corollary is that your wallet is the whole relationship. If you lose control of the signer, you lose the funds it holds and the ability to pay with it; we cannot restore, freeze or recover it, and we hold no backup of anything belonging to you.

A metered request that arrives without payment receives an HTTP 402 response stating the price, the asset, the network and the payee. That response is a quote, valid for the window it names. You are free to decline it by not signing, and declining costs nothing.

Signing the EIP-3009 authorization and re-sending the request is your acceptance of that price for that request. Prices are per request, quoted before the work is performed, and derived from upstream cost plus a routing fee. There is no subscription, no minimum spend, no monthly fee and no prepaid balance.

Payment settles onchain through an independent facilitator, which verifies your signature and submits the transfer. A settled payment entitles you to one execution of the request you paid for, on the model your request resolved to, at the time it was made.

It does not buy a specific provider, a stated latency, a particular output, or any right to re-run the request. Settlement is final: an onchain transfer cannot be reversed by us, by you, or by the facilitator.

If payment settles and the upstream then fails to deliver — a genuine server-side failure, not a refusal to answer and not an output you dislike — we issue a credit note against your payer address, redeemable against a subsequent request. Credit notes are the remedy in this situation, and they are the only one available, because the transfer itself is irreversible.

A completion that is wrong, unhelpful, truncated by the model, or refused by the model’s own policy is a delivered result. It is not a failure of the service and does not generate a credit note.

Dolphin serves open-weight models at no charge, rate-limited and with no payment path. It is provided as-is, may change or end without notice, and carries no availability expectation whatsoever. Do not build something you cannot afford to lose on top of it.

Rate limits on the free tier are enforced per payer address or, where none is present, per network address. Attempting to circumvent them — rotating addresses to multiply an allowance, distributing requests to evade counting — is a breach of clause 8.

You may not use the service to generate or facilitate: material that sexually exploits minors; targeted harassment; malware, exploit code or credential-theft infrastructure; content designed to impersonate a real person or organization for deception; or activity unlawful in the jurisdiction where you operate.

You may not attempt to degrade or evade the router itself — probing for unmetered access to metered models, replaying authorizations, or generating load intended to exhaust upstream capacity rather than to obtain a result.

Each upstream provider has its own acceptable-use policy, and traffic we send to a provider is subject to it. Where a provider restricts a model by use case, by content category or by territory, that restriction applies to requests routed to that provider. The router may serve such a request from a different provider where one exists and permits it; where none does, the request fails.

Routing does not exempt anyone from provider policy, and we will not represent that it does. What it changes is the scope of the constraint: a restriction binds one candidate provider rather than your access to the catalog.

You retain all rights in the prompts you send. We claim no licence to them beyond what is technically required to route and deliver the request, we do not retain them, and we do not use them to train anything.

As between you and us, output is yours to use. We make no representation that output is accurate, original, non-infringing or fit for any purpose, and rights in model output may also be affected by the terms of the model’s own provider. Nothing produced through the service is legal, medical, financial or professional advice.

We operate redundant upstream tiers precisely because individual providers fail, and the router fails over automatically. We do not offer a service level agreement on this page, and no uptime figure published in our marketing, blog or status page is a contractual commitment.

Metered requests additionally depend on facilitator availability and on Robinhood Chain itself. When settlement is degraded, metered routes may be refused while free-tier routes continue, because the free tier never touches the chain.

Published rate limits apply per payer address and may be adjusted to protect upstream capacity or to respond to abuse. A 429 response always carries a Retry-After value; treating it as a signal to back off, rather than to retry immediately, is a condition of continued access.

Because there are no accounts, our enforcement options are narrower than a conventional provider’s and we would rather be precise about them. We can decline to serve requests associated with a specific payer address, decline traffic from a network source, refuse a request that a provider would reject anyway, and remove a model from the catalog.

We cannot close your account, revoke your key, or seize a balance, because none of those things exist. A refusal to serve is prospective only — it does not touch anything you already hold or anything already settled.

The service is provided on an as-is and as-available basis, without warranties of any kind, express or implied, to the fullest extent permitted by applicable law. We disclaim responsibility for the acts, omissions, availability and policies of upstream providers, facilitators, wallet software and the settlement network.

To the fullest extent permitted by law, our aggregate liability arising from or relating to the service is limited to the total amount you settled through the router in the 30 days preceding the event giving rise to the claim. We are not liable for indirect, incidental, special or consequential damages, for lost profits, or for loss of data — including conversations stored in your own browser, which we neither hold nor can restore.

You will indemnify and hold us harmless against third-party claims arising from your use of the service in breach of these terms, including claims relating to content you submit or output you publish or act upon.

We may revise these terms. The revised version is published on this page with a new effective date and announced in the release notes; because there is no mailing list, this page is the authoritative record. Continuing to send requests after a revision is acceptance of it. Terms in force at the time of a settled request govern that request.

These terms are governed by the law of the jurisdiction in which the operating entity is established, and disputes are subject to the courts of that jurisdiction. The entity, its jurisdiction and its notice address are identified through the contact channel listed in the site footer, which is also where legal notices should be sent.

If any clause is held unenforceable, the remainder stands. This page, together with the privacy policy, is the entire agreement between us regarding the service.