Terms of Service

Effective date: October 28, 2026

These terms describe the rules for using the Bimatch service at www.bimatch.ai, its API and optional connected agents. Bimatch connects buyers and suppliers of AI inference. By using the service, you agree to these terms. If you do not agree, do not use the service.

1. Accounts and eligibility

You must be legally able to enter into an agreement and authorized to act for any organization you represent. Provide accurate account information and protect your login credentials, API keys and connected-provider credentials. You are responsible for activity you authorize through your account. Contact admin@bimatch.ai promptly if you suspect unauthorized access.

Google sign-in is an optional authentication method. It does not imply that Google endorses Bimatch or grants you rights to other Google services. Our Privacy Policy explains the information used for sign-in and operation of the service.

2. Marketplace and connected agents

Buyers may request inference using available models. Suppliers may connect agents and publish supported model access. Availability depends on connected suppliers, capacity, account permissions and upstream providers. A listing does not guarantee that a particular model, capacity or response time will remain available.

Connect only devices, accounts and credentials you own or are authorized to use for the intended purpose. Suppliers must have any permissions required to provide access to others and must comply with the relevant provider's terms. Possession of an account or subscription does not by itself establish permission to resell or share its access. Bimatch does not grant an exemption from provider restrictions.

3. Acceptable use

• Use the service lawfully and respect applicable intellectual property, privacy and other rights.
• Do not submit content or credentials you lack authority to share or process.
• Do not use stolen accounts, impersonate others, commit fraud, distribute malware or attempt unauthorized access.
• Do not bypass authentication, usage limits, billing controls or provider safeguards, or deliberately disrupt the service.
• Do not misrepresent supplied models, account permissions, usage or transaction records.

4. Your content and model outputs

You retain your rights in content you submit. You authorize Bimatch and the execution services involved in your request to transmit and process that content as needed to provide the requested service, as described in the Privacy Policy. These terms do not transfer ownership of your input to Bimatch.

Model output may be inaccurate, incomplete, non-unique or unsuitable for your purpose. Review and verify it before relying on it or sharing it with others. Output rights and permitted uses may also depend on the relevant model provider's terms and applicable law; Bimatch does not guarantee that output is exclusive or free of third-party rights.

5. Pricing, usage and billing questions

Where paid features are available, review the applicable prices, usage units, fees and transaction conditions shown in the service before authorizing use. Usage-based charges depend on the model and measured usage. Estimates may differ from final measured usage. Model availability and prices can change; review the applicable information before placing a new request.

Only payment, deposit or payout methods expressly enabled by the service are supported. A displayed usage balance or earnings record is not a guarantee of an available withdrawal method or a completed transfer. No particular supplier earnings or revenue are guaranteed.

For a suspected billing error, failed paid request or refund question, contact admin@bimatch.ai with the relevant request or transaction identifier. Do not send secrets or full payment credentials. We will review the records and explain the outcome. Refunds and adjustments depend on the circumstances, applicable transaction terms and law. Nothing here excludes a refund or other remedy required by law.

6. Third-party services and privacy

The service integrates with independent identity, hosting, supplier and model services. Their own terms and privacy policies may apply. We do not control their continued availability or processing practices. Our Privacy Policy describes how Bimatch handles account data, inference requests and connected-agent information, and how to request access or deletion.

7. Service changes, suspension and closure

We may maintain, change or discontinue features, and may restrict or suspend access to address security threats, abuse, violations of these terms or legal requirements. Where practical and appropriate, we will provide notice and a way to contact us about a restriction. Urgent security or legal issues may require action without advance notice.

You may stop using the service, disconnect agents, revoke API keys or connected-provider access, and request account closure by contacting admin@bimatch.ai. Closing an account does not automatically erase transaction obligations or records that must be retained. Personal information is handled as described in the Privacy Policy.

8. Availability and responsibility

Unless separately agreed in writing, Bimatch does not promise uninterrupted availability, a fixed response time, a particular model outcome or a service-level guarantee. Maintain your own copies of information important to you and assess whether the service is suitable for your intended use.

Nothing in these terms excludes or limits rights, warranties, remedies or liability that cannot lawfully be excluded or limited. These terms do not require you to waive mandatory consumer protections.

9. Updates and contact

We may update these terms as the service evolves. The effective date identifies the published version. Material changes will be communicated through the service or account contact details where appropriate. If you do not agree to revised terms, stop using the service and contact us about account closure or any outstanding transactions.

For service, billing or terms questions, contact the Bimatch service team at admin@bimatch.ai. Include enough information to identify the issue, but never send passwords or API tokens.