Terms of Service

1. What you're agreeing to

By creating an account or paying for ModelBrake, you agree to these terms. If you are using ModelBrake on behalf of an organization, you represent that you have authority to bind that organization to these terms.

2. What ModelBrake does

ModelBrake monitors your spend on supported providers (OpenAI, Anthropic, AWS Bedrock, Vercel) by polling their usage or cost APIs at regular intervals with a read-only credential you provide. It alerts you by email and/or webhook when it detects anomalous spend or a ceiling you set is crossed. It optionally revokes an application key if you arm the kill switch with a separate write-scoped credential.

3. What ModelBrake does not guarantee

Read this section carefully. It defines the limits of the service.

• Polling has a detection gap. OpenAI, Anthropic, and Vercel AI Gateway are polled every 15 minutes. AWS Bedrock is polled every 6 hours (and Cost Explorer data itself can lag up to 24 hours). Spend that occurs between polls is not detected until the next poll completes. A runaway loop that starts and finishes within that window will not trigger an alert.
• Vercel platform monitoring depends on Vercel's webhooks. Platform infra spend (serverless functions, bandwidth, edge requests) is monitored via Vercel Spend Management webhooks. If Vercel does not fire its webhook, or fires it late, ModelBrake has no way to detect the threshold on its own.
• Provider APIs can fail, change, or report inaccurately. If a provider's usage API is down, rate-limited, returns incomplete data, or changes its response format, polling may return stale or incorrect cost figures. ModelBrake relies on the data the provider returns.
• Revoke is best-effort. When you arm the kill switch, ModelBrake attempts to revoke the named application key through the provider's management API. That API call can fail due to rate limits, network issues, or provider outages. On OpenAI, revocation is permanent (the key is deleted, not disabled). ModelBrake is not responsible for spend that accrues if the revoke call fails.
• Anomaly detection has false positives and negatives. The 3× median-day threshold is a heuristic. A legitimately busy day can trigger a false alarm; a gradual cost increase that stays below 3× will not trigger one.
• ModelBrake is a monitoring tool, not insurance. It reduces the time between a cost spike and your awareness of it. It does not prevent all overspend, and it is not a substitute for provider-level spend limits where those exist.

4. Your responsibilities

• Provide valid, correctly scoped credentials. A key without the required read permissions will produce empty polls, not errors you can see.
• Keep your email current. Alerts go to the email on your account.
• Review alerts promptly. ModelBrake tells you something looks wrong; acting on it is yours to do.
• Do not share your account credentials or dashboard access with anyone you do not trust with your provider keys.

5. Pricing and payment

Founding members pay $29/month, locked for the life of their subscription. Payment is handled by Stripe. If payment fails, we will retry per Stripe's dunning schedule and notify you by email. Continued non-payment results in account suspension (polling stops, alerts stop). We do not offer refunds for partial months, but we will not charge you after you cancel.

6. Cancellation

You can cancel at any time through our contact page. Cancellation takes effect at the end of your current billing period. After cancellation, polling stops and your encrypted credentials are deleted within 30 days. See our Privacy Policy for full retention details.

7. Limitation of liability

To the maximum extent permitted by law, ModelBrake's total liability to you for any claim arising out of or related to the service is limited to the fees you have paid in the 12 months preceding the claim. ModelBrake is not liable for any indirect, incidental, consequential, or punitive damages, including but not limited to provider costs incurred during a detection gap, revenue lost from a revoked key, or damages arising from provider API failures.

8. Availability

We aim for high availability but do not offer an SLA. Scheduled maintenance, provider outages, and infrastructure issues can interrupt polling. We will notify you of extended outages when possible.

9. Changes to these terms

We may update these terms. Material changes (anything that affects your rights or our liability) will be communicated to active account holders by email at least 14 days before they take effect. Continued use of ModelBrake after the effective date constitutes acceptance.

10. Governing law

These terms are governed by the laws of the State of Georgia, without regard to conflict-of-law principles. Any disputes will be resolved in the courts of Fulton County, Georgia.

Contact

Questions about these terms? Get in touch.