Terms of service

1. Who this is between

Modelvia is operated by Yo-Da Lai (ABN 84 992 526 369), an individual sole trader. This agreement is between Yo-Da Lai (“we”, “us”) and the business named on the order or account record (“you”, “the client”).

You may serve your own customers through your Modelvia account. Those customers are yours: they contract with you, not with us, and we have no relationship with them beyond holding the records your account needs. You are responsible for what your customers do with the access you give them, and for telling them what they need to know about how their data is handled.

The account begins when we confirm it in writing. There is no public self-signup during the pilot.

2. What the service is

Modelvia accepts an API request on the /v1 surface, selects an admitted model route, sends the request to that route's provider, returns the response, and records a priced receipt. Account structure, spending caps, usage and invoicing sit around that.

Which models are available, and which provider serves them, is our decision and can change. We tell you what a route can do through GET /v1/models; we do not promise that any particular upstream model stays available. See API versioning for what we do promise about the interface itself.

This is a private pilot on a single instance. We make no availability commitment and there is no service credit — see service levels. Do not use Modelvia for anything where an outage causes harm.

3. Keys and account security

• A key is shown once and stored only as a hash. We cannot recover it for you; we can revoke it and you can mint another.
• Keep keys out of browsers, client applications and source control. Requests made with your key are treated as yours and are charged to you, including requests made by someone who obtained the key.
• Tell us at yoda@yodalai.xyz as soon as you think a key or account is compromised. We will revoke on request.
• Do not share one key across separate customers of yours. Provision a key per customer and project so that revoking one does not cut off the rest, and so usage is attributed correctly.

4. Acceptable use

You must not use Modelvia, or let anyone using your account use it, to:

• break the law, infringe someone's rights, or breach a provider's own terms for the model being served;
• create or distribute material that sexualises children, incites violence, or is designed to harass, defraud or deceive a specific person;
• develop weapons, run attacks against computer systems, or generate malware;
• make automated decisions about a person's credit, employment, housing, insurance or legal rights without a human who is accountable for the decision;
• send us personal information you have no lawful basis to send, including health, biometric or government identifiers, unless we have agreed that in writing first;
• resell raw model access as if it were your own model, misrepresent which model served a request, or strip the account boundaries that keep your customers separate from each other;
• probe, load-test or reverse-engineer the service beyond your own normal use, or work around a spending cap, rate limit or refusal.

We do not read prompts to police this — we cannot, because we do not keep them. We act on reports, on provider notices, and on what the account's own usage records show.

5. Fees, invoicing and tax

Pricing is usage-based. Every request that reaches a provider produces a receipt naming the model served, the token counts and the exact charge, in Australian dollars recorded to nano-dollar precision. A request refused before dispatch — a cap, a rate limit, an unsupported parameter — costs nothing.

Charges are calculated from an immutable published rate card. Your billing account must accept a rate-card version before anything can be priced under it, and every receipt names the version that applied. A new rate card applies only after acceptance; we will not reprice work already done.

Amounts are in AUD. Whether GST applies, and whether the published amounts include it, is configured on your account and shown on the invoice; the invoice, not this page, is the statement of what is payable. Invoices are issued per billing period and are due 14 days from issue unless the order says otherwise.

Where your own customers pay through Modelvia, payments are collected through Square under your merchant account — the money is yours and the merchant relationship is yours. See subprocessors. Your invoice from us is separate from what you charge your customers.

If you think an invoice is wrong, tell us at yoda@yodalai.xyz within 30 days with the request identifiers concerned. We will reconcile against the ledger, which records every financial event in order, and correct anything that is genuinely wrong. We do not reverse a charge for work a provider actually performed.

6. Suspension and ending the agreement

We may suspend serving on your account, in whole or for one key, if:

• an invoice is more than 30 days overdue, after we have told you;
• use breaches section 4, or a provider requires us to stop;
• we reasonably believe a key is compromised, or that continuing would expose your data or someone else's;
• we must close serving to deal with a security or data-integrity incident. Spending caps and readiness checks already refuse admission automatically in those conditions.

Where we can, we tell you first; where we cannot, we tell you as soon as practicable and say why. We restore serving once the cause is resolved.

Either of us may end this agreement with 30 days' written notice. You remain liable for usage up to the end date. On termination we stop serving, revoke keys, and keep the invoice and financial records we are required to keep — see privacy.

7. Your content and ours

What you send and what comes back is yours, as between you and us. We claim no ownership of it and we do not train on it. We do not store it. To serve a request it is processed by our routing classifier when you ask for automatic routing, and by OpenRouter and the host serving the model; it is gone from our side once the response is served. We keep the accounting record of the request, never the text. See privacy.

Model output is generated text. It can be wrong, and it is not legal, medical or financial advice. Check anything you rely on. We make no warranty that output is accurate, original or fit for your purpose.

The platform, its documentation and its interfaces remain ours. You may use them to operate your integration and nothing else.

8. Liability

Nothing in this agreement excludes rights you have under the Australian Consumer Law or any other law that cannot be excluded. Where we may limit liability for a failure to comply with a consumer guarantee, our liability is limited to resupplying the service or paying the cost of resupply.

Otherwise, and to the extent the law allows: neither of us is liable for indirect or consequential loss, lost profits, lost revenue or lost data; and our total liability for all claims in any 12-month period is capped at the fees you paid us in the 12 months before the first claim arose.

That cap does not apply to your obligation to pay fees, to either party's breach of confidentiality, or to liability caused by fraud or wilful misconduct.

You indemnify us against claims brought by your own customers that arise from how you operated your service, except to the extent we caused them.

9. Changes to this agreement

We may change these terms. We will give at least 30 days' notice by email to your account contact and by publishing the new version here with its date. If a change materially reduces what you get, you may end the agreement before it takes effect without penalty. Interface changes follow the separate versioning policy.

10. Governing law and general

This agreement is governed by the laws of Queensland, Australia, and both of us submit to the non-exclusive jurisdiction of its courts.

Notices under this agreement are given by email: to us at yoda@yodalai.xyz, and to you at the account contact's email address. Security matters go to yoda@yodalai.xyz. Neither of us may assign this agreement without the other's consent, except to a successor of the whole business. If a clause is unenforceable it is severed and the rest stands. This agreement, the order and the pages it links to are the whole agreement between us.