Stability AI Developer Platform
$0.01 for new accounts; it does not recur.
https://api.stability.aiModels mentioned
The offer covers a dynamic catalog, provider-selected route, or model class without stable model IDs in this snapshot.
Equivalent paid value
How this was valued: Face value of 25 signup credits at $0.01 each; endpoint uses share the same balance and are not additive.
Limits and terms
- Signup Credits
- 25
- Credit Value USD
- 0.01
- Signup Value USD
- 0.25
- Recurrence
- No
- Expiry
- not published
- Rate Limits
- account and endpoint specific
What happens to your prompts?
Platform API content may be retained and used for model training by default; users must opt out to exclude that secondary use.
- Plan Scope
- Stability AI Developer Platform APIs, including signup-credit use.
- Prompt Retention
- Platform API content may be preserved under the standard terms; a fixed ordinary retention period is not published in the trial material.
- Response Retention
- Same as submitted content; generated assets can be handled as account/service content.
- Ordinary Logging
- Account, usage, billing, safety, security, and operational information is processed under platform terms.
- Model Training
- Platform API content may be used for data training by default; users can submit the documented opt-out.
- Product Improvement
- Content may support model and platform development unless the applicable opt-out or contractual protection applies.
- Human Or Operator Access
- Safety, support, and service operations can involve access; public trial pages do not publish a narrow operator-access rule.
- Subprocessors And Routing
- Stability and its service providers process requests across image, audio, and 3D endpoints.
- Deletion Controls
- General account/privacy controls apply; no trial-specific prompt or generated-asset purge interval is published.
- Caveat
- The training protection is opt-out rather than the free trial's default.
Governing documents
- Terms Of Service
- https://platform.stability.ai/docs/terms-of-service
Eligibility
- Account Required
- Yes
- Qualifying Signup Method
- Google social login
- Payment Method Required
- not documented
Primary sources
Before you build with Stability AI Developer Platform
Read the classification narrowly
This record has current first-party evidence for some zero-cost hosted inference. The label describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every region.
Resolve the live model route
No stable model ID is recorded. The offer may use a dynamic catalog, a provider-selected route, or a model class, so resolve the current machine-readable ID before writing a fixed production configuration. The recorded base endpoint is https://api.stability.ai, but the provider's current API reference remains authoritative for paths, authentication, and request shape.
Confirm account and billing boundaries
An account is required, so public catalog evidence cannot by itself prove the limits, balance, or billing behavior attached to your workspace. The reviewed evidence explicitly says no payment card is required. Re-check the signup flow because eligibility and billing controls can change after the snapshot. The equivalent paid value shown here prices a documented allowance where possible; it is not cash, guaranteed savings, or protection from overage.
Re-read the prompt policy for your plan
This record classifies the reviewed handling as “Not private”: Platform API content may be retained and used for model training by default; users must opt out to exclude that secondary use. Provider policies can distinguish free, paid, enterprise, opted-in, and feature-specific traffic, so verify the governing terms for the exact account and route that will receive your data.
Follow the evidence, then re-check it
The record links 7 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest governing document or live catalog when sources disagree, and submit a correction when a provider changes a material term.
Match the quota to the workload shape
Translate the published allowance into the traffic pattern you actually expect instead of comparing headline totals alone. A daily token pool can look generous while a low requests-per-minute or concurrency ceiling blocks interactive bursts; a high request limit can still fail a long-context job when input, output, or per-request tokens are capped. Separate prompt tokens from generated tokens, include retries and tool calls, and test the largest realistic payload. If the provider documents more than one limit window, the tightest window at your peak load is the practical ceiling. Research, experimental, and community access can also carry eligibility or fair-use constraints that cannot be modeled as a simple number.
Plan fallback without changing the rules
A fallback should preserve more than API syntax. Confirm that the substitute route supports the required modality, context length, streaming behavior, structured output, tools, and safety controls, then compare its prompt-retention and training terms. An OpenAI-compatible request shape does not make providers operationally or contractually equivalent. Decide which errors may trigger a retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. If deterministic output matters, record the model revision and sampling settings; rotating aliases and free-model pools can change behavior even when the endpoint remains available.
Monitor the offer as a dependency
Capture the model ID, response model field, rate-limit headers, usage fields, latency, HTTP status, and any provider request identifier for each test. Watch for authorization failures, quota exhaustion, catalog removal, policy revisions, and dashboard balance changes as separate failure modes. Re-check the provider’s live catalog and governing pages on a schedule proportionate to the workload’s importance, and keep the dated sources that supported your decision. Free capacity is especially suitable for prototypes, evaluations, fallbacks, and bounded workloads when the application can tolerate change; a production dependency still needs observability, an exit path, and an owner responsible for re-verification.
Test one complete request before scaling
Start with the smallest permitted request using the exact credential, model ID, endpoint, and account type you intend to deploy. Record the HTTP status, response headers, usage fields, latency, and any dashboard balance change. Then exercise the failure path: an invalid model, an exhausted quota, or a rate-limit response should fail clearly without silently switching to a paid route. If the provider supports streaming or tool calls, validate those features separately because a free model can expose a narrower capability set than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and avoid sending sensitive data until the observed route matches the reviewed data agreement.