DevPass Supplemental Terms of Use

Effective Date: April 26, 2026
Last Updated: August 2, 2026

DevPass is a service operated by LLM Gateway(“we”, “our”, or “us”). These DevPass Supplemental Terms of Use (“DevPass Terms”) govern your access to and use of DevPass, including the website at devpass.llmgateway.io, the DevPass dashboard, related APIs, SDKs, and any DevPass-branded products or services (collectively, the “Service”).

These DevPass Terms are an addendum to, and incorporate by reference, the main LLM Gateway Terms of Use (the “Base Terms”), which form the base agreement between you and us. The Base Terms apply in full to your use of DevPass and govern all topics not specifically addressed here — including eligibility, accounts and security, intellectual property, disclaimers, limitation of liability, indemnification, dispute resolution and arbitration, and governing law. These DevPass Terms only add to or modify the Base Terms for the DevPass-specific points below.

Order of precedence. If there is a direct conflict between these DevPass Terms and the Base Terms with respect to DevPass, these DevPass Terms control for that conflict only. In all other respects, the Base Terms remain in full force and effect. Capitalized terms not defined here have the meaning given in the Base Terms.

By accessing or using DevPass, you agree to be bound by both the Base Terms and these DevPass Terms. If you do not agree, please discontinue use immediately.

1. What DevPass Is

DevPass is a flat-rate subscription that gives developers access to 200+ AI coding models through a single OpenAI-compatible API endpoint and the LLM Gateway. The Service allows you to:

Route AI requests to providers such as Anthropic, OpenAI, Google, Mistral, DeepSeek, and others through approved coding and agent tools like Claude Code, Codex, Cursor, Cline, OpenCode, OpenClaw, Hermes, and Autohand
Track usage, costs, and per-agent activity in your DevPass dashboard
Manage a single API key shared across every supported tool

DevPass is licensed solely for interactive use through approved coding and agent tools. It is nota general-purpose API: you may not use your DevPass API key to power your own applications, products, services, backends, scripts, batch jobs, or any other direct API integration. The flat-rate pricing assumes interactive, human-in-the-loop usage from a whitelisted tool — any other usage breaks the economics of the Service and is prohibited under Section 4. Embeddings, image generation, and video generation are not included in DevPass and are blocked at the gateway. If you need API access for an application or for non-inference workloads (such as embeddings, image generation, or video generation), use a standard LLM Gateway credits plan under the Base Terms instead.

2. Plans, Billing, and Fair Use

This section supplements Section 4 (Plans, Credits, and Billing) of the Base Terms. DevPass is sold as a tiered monthly subscription:

Lite, Pro, and Max tiers each include a monthly model-usage allowance, denominated in dollars of provider cost
Allowances reset at the start of each billing cycle and do not roll overat renewal; the only exception is an immediate mid-cycle upgrade, which rolls your unused allowance into the new cycle (see “Plan changes” below)

Billing is processed securely through Stripe, as described in the Base Terms. By subscribing, you authorize us to charge your payment method for the selected plan and any applicable taxes. All fees are non-refundable except where required by law. You may cancel at any time; your plan remains active until the end of the current billing period.

Plan changes. You may change tiers at any time from your dashboard. Upgradestake effect immediately by default: we charge the full price of the new tier at the time of the upgrade, your billing cycle restarts on that day, and you receive the new tier’s full monthly allowance. Any unused allowance from the cycle being replaced rolls overinto the new cycle’s allowance; rolled-over allowance expires at your next renewal and is not refunded, credited, or deducted from the upgrade price. You may instead schedule an upgrade for your next renewal: no charge is due when scheduling, you keep your current tier and allowance until the renewal, and the new tier is billed from the renewal onward (no allowance rolls over at renewal). Downgrades are scheduled for your next renewal: you keep your current tier and its allowance until the end of the period you have already paid for, the lower tier is billed from the next renewal onward, and no charge or refund is issued when you schedule the downgrade.

DevPass is intended for private, personal use by an individual developer — not for teams, companies, or other organizations (see Section 3). We may rate-limit, suspend, or downgrade accounts that show signs of automated abuse, key sharing, resale, or sustained traffic patterns inconsistent with interactive coding workflows.

3. One Account Per Developer

DevPass is sold to one developer, on one account. The flat-rate price and 3× your subscription in included usage only work because each person uses a single account in good faith. Splitting that usage across multiple accounts is the fastest way to break the deal for everyone.

To keep the pricing sustainable for the developers who use DevPass honestly, the following are not allowed:

Creating more than one DevPass account per person, household, or business entity
Reusing the same payment card, billing address, device, or IP across multiple DevPass accounts to claim the included usage more than once
Cancelling and re-subscribing under a new account to reset usage before the billing cycle renews
Using prepaid cards, virtual cards, or other payment instruments designed to obscure identity for the purpose of opening additional accounts

We automatically check the payment card used at checkout against existing DevPass subscriptions. If the same card has already been used to activate DevPass on another account, the new subscription is cancelled and access is not granted.

If we detect (manually or automatically) that the rules in this section have been broken, we may, without prior notice:

Cancel every active subscription on every related account immediately, at any point in the billing cycle
Revoke API keys and block gateway access for every related account
Refuse any future signup associated with the same person, card, or organization
Retain fees already paid for the cycle in progress, since the included usage has already been provisioned

No team or company use. DevPass is intended for private, personal, individual use only. It may not be purchased, shared, expensed, or otherwise used by or on behalf of a team, company, or other organization, and we do not offer team or multi-seat DevPass plans. If you need AI model access for multiple developers, use our pay-as-you-go LLM Gateway product under the Base Terms instead — contact contact@llmgateway.io for custom solutions and volume discounts for teams.

4. DevPass Acceptable Use

In addition to the Acceptable Use rules in Section 6 of the Base Terms, the following DevPass-specific restrictions apply. You agree not to:

Open multiple DevPass accounts or otherwise abuse the included usage allowance as described in Section 3
Use your DevPass API key directly from your own applications, backends, products, services, scripts, batch pipelines, or any other integration outside of an approved coding or agent tool. DevPass is only usable from whitelisted clients such as Claude Code, Codex, Cursor, Cline, OpenCode, OpenClaw, Hermes, and Autohand. The list of approved tools is maintained at our discretion and may change over time
Use DevPass for non-inference workloads — embeddings, image generation, and video generation are not included and are blocked at the gateway. Use a standard LLM Gateway credits plan for those use cases
Share your DevPass API key outside your own use or use a single key across unrelated parties
Attempt to circumvent rate limits, plan allowances, or authentication controls

We reserve the right to permanently banaccounts — and every related account — that engage in abuse, fraud, payment disputes filed in bad faith, or any other policy violation, including provider-level violations. Banned accounts lose access immediately; fees paid for the current billing cycle are not refunded. This supplements the suspension and termination rights in Section 11 of the Base Terms.

5. Data and Privacy

Your DevPass data is handled according to the DevPass Privacy Policy, which builds on the main LLM Gateway Privacy Policy. Per-agent metadata — token counts, costs, models, and routing information — is stored to power your dashboard, usage reporting, and per-tool insights. Request payloads and responses are not retained on DevPass, except for stateful Responses API requests, which are stored for up to 30 days so response chaining works.

6. Contact

Questions about these DevPass Terms or the Base Terms? Email contact@llmgateway.io.