Fair Use

Unlimited means unlimited.

This is for running your AI agent — at whatever scale you actually need, not just lightweight tasks. Use it freely: the catch is never your access or your bill, only speed. The harder you push, the more delivery slows to keep the pool fair — then it springs right back as you ease off, so lean, efficient usage is what stays fast. There are really only two rules: use it freely, and don't try to game the system.

♾️

1. Use it freely — efficiency keeps you fast

Use it for whatever you want, at any scale — no token meter, no overage. The trade-off is speed, and it self-corrects: the harder (or more wastefully) you push, the more delivery slows to keep things fair — and it springs right back the moment you ease off. So lean, token-light usage is what keeps you fast. Genuinely need sustained high throughput? Higher plans add headroom, up to $399/mo.

🛡️

2. Don't try to game it

Flat-rate compute works because people use it for real work, not to exploit it. So don't go hunting for ways to break or drain the system — flooding it with junk requests or deliberately burning the maximum compute just because it's “unlimited.” It only slows things down for everyone, it's self-defeating, and our safeguards rebalance against it anyway. Use it for what it's for and you'll never think about this.

What's totally fine

The stuff people second-guess on a flat plan — all of it is fair game.

  • Run your agent around the clock — 24/7, no babysitting.
  • Real workloads — big builds, batch jobs, overnight and unattended runs.
  • Long-running automations and scrapers for your own pipeline.
  • Whatever scale you actually need — light or heavy, not just lightweight tasks.
  • Connect any OpenAI-compatible tool.

Where we draw the line

The obvious stuff — outright malicious or illegal use — but it still has to be said. Cross any of these and we'll suspend the account; everything else is fair game.

  • Using the API as raw compute unrelated to AI — e.g. crypto mining.
  • Launching or coordinating denial-of-service attacks.
  • Mass scraping or harvesting where the model is just an extraction tool for someone else's content.
  • Reverse-engineering or benchmarking upstream providers against their terms.
  • Generating illegal content — fraud, harassment, CSAM.

How we keep it fast for everyone

The honest version of what makes “unlimited” sustainable — and the only time you'd ever feel a limit.

Under the hood

To make flat-rate compute work, we batch requests, route each call to the most efficient model configuration, and compact prompts behind the scenes — all without touching output quality.

When the platform is slammed

We may briefly queue or slow requests so no single account can hog the whole pool. We don't normally drop anything — we just smooth the spikes. Higher plans get priority scheduling and less batching, so they feel it less.

So when would I hit a limit?

Occasional bursts way above normal are expected and fine. Throttling only kicks in for sustained usage that's wildly out of profile for a plan — and even then it's a temporary slowdown, not a shutdown. It clears the moment your usage settles back down, and lean, efficient requests rarely feel it at all.

Built for individual developers

These plans are for you and your agents — run them as hard as you like, light or heavy, for whatever you're working on. If you want to resell compute or run a product for external customers at real scale, let's talk enterprise.

We don't read your prompts

To keep things stable we watch aggregate metrics — request volume, throughput, error rates. That's it. We don't read or analyze your prompt content.

This policy can change

It'll grow with the platform. Material changes get at least 14 days' notice. Questions about your specific use case? Reach us at contact@standardcompute.com.