Use WeaveAPI to route legitimate model workloads.

These terms define the baseline rules for accounts, API keys, billing, model access, service limits, and responsible use.

Account access

You are responsible for the security of your account, API keys, and applications using WeaveAPI. Do not share keys publicly or resell access without written permission.

Service availability

We work to keep the gateway available, but upstream model providers, network conditions, capacity limits, and maintenance windows can affect availability.

Billing and quota

Usage is metered by requests, tokens, provider route, and configured pricing. Accounts may be paused if quota is exhausted, payment fails, or abuse is detected.

Model behavior

Model outputs are generated by upstream providers. You are responsible for reviewing outputs before using them in products, decisions, or customer-facing workflows.

Restrictions

Do not use WeaveAPI for malware, credential theft, spam, exploitation, illegal surveillance, harmful automation, or attempts to bypass provider safety controls.

Changes

We may update these terms as the product, provider mix, or legal requirements change. Continued use after an update means you accept the revised terms.