User Agreement

Effective date: July 29, 2026

This User Agreement explains the core rules for creating and using a Modelflare account. It works together with our Terms of Service, Top-up and Refund Policy, Platform Usage Rules, Privacy Policy, Supported Countries and Regions, pricing, documentation, and any other policies we publish.

Modelflare is operated by Havenbyte LLC. By creating an account, signing in, creating an API key, adding funds, calling an API, or otherwise using the service, you agree to this User Agreement and the other applicable policies.

1. Account Eligibility

You may use Modelflare only if you are legally allowed to do so, are located in a supported country or region, and are not subject to sanctions, embargoes, or other restrictions that prohibit access to the service.

If you use Modelflare on behalf of an organization, you represent that you have authority to bind that organization and that the organization is responsible for your use.

2. Account Security

You are responsible for keeping your login credentials, OAuth access, passkeys, API keys, tokens, devices, and workspaces secure. Do not publish or share API keys in public repositories, chat rooms, client-side applications, logs, screenshots, browser extensions, or other places where unauthorized parties may access them.

You are responsible for all activity under your account and API keys, including activity by teammates, contractors, agents, tools, scripts, or downstream users. If you believe your account or key has been compromised, delete or rotate the key and contact support promptly.

3. API Keys, Groups, and Models

API keys control access to model groups and billing. You must use the correct group for the model you want to call. A key assigned to the default group may not be able to access production model groups.

Model names, protocols, availability, pricing, limits, and supported features may change. You should check the model catalog, pricing page, usage logs, and documentation before relying on a model in production.

4. Credits, Billing, and Refunds

Modelflare is a prepaid, usage-based service unless we agree otherwise in writing. You are responsible for charges generated by your account, API keys, projects, agents, and integrations.

Purchased and promotional credits may be used only for Modelflare services. They are not bank deposits, electronic money, securities, or cash equivalents, and they do not earn interest.

Top-ups and refunds are governed by our Top-up and Refund Policy, which explains the refund window, unused paid credits, treatment of bonus credits, refund processing fee, refund method, and account reconciliation. By confirming a top-up payment, you agree to that policy. A payment-provider refund may result in credits being deducted, negative remaining credits, and suspension of the account and its API keys until any resulting refund debt is resolved.

5. Acceptable Use

You must follow our Platform Usage Rules. You may not use Modelflare for illegal, harmful, abusive, fraudulent, exploitative, infringing, unsafe, or unauthorized activity. You may not use Modelflare to scrape, copy, train, fine-tune, distill, evaluate, benchmark, or improve a competing model or model-routing service unless we approve it in writing.

You are responsible for your users and downstream integrations. If you embed Modelflare into your own products, agents, tools, bots, or workflows, you must provide appropriate disclosures and safeguards.

6. Customer Content

You are responsible for the inputs you submit and for reviewing outputs before relying on them. AI outputs may be wrong, incomplete, outdated, biased, misleading, or unsuitable for your use case.

Do not submit sensitive personal information, payment card data, medical records, government identification documents, authentication credentials, trade secrets, or other highly sensitive data unless you have confirmed that your use case and all applicable policies permit it.

7. Service Changes and Availability

Modelflare depends on models, infrastructure, payment providers, identity providers, networks, and other third-party services. We may change, suspend, limit, replace, or discontinue models, service routes, groups, endpoints, prices, payment methods, account features, or documentation where needed for reliability, security, legal compliance, provider changes, cost changes, or business reasons.

We may limit, suspend, or terminate access if we believe an account, API key, request, payment method, user, region, or integration presents risk, violates policy, causes harm, or threatens service stability.

8. Support

Support is provided through the official support channels published on our website, including in-dashboard support tickets and support@modelflare.dev. Support may require request IDs, timestamps, account identifiers, payment records, usage logs, or other information needed to investigate the issue.

9. Changes

We may update this User Agreement from time to time. Updated versions become effective when posted or on the date stated in the notice. Continued use of Modelflare after an update means you accept the updated agreement.

10. Contact

For account, billing, support, or policy questions, contact us through in-dashboard support or email us at support@modelflare.dev.