---
title: "Stability AI Developer Platform free inference"
description: "$0.01 for new accounts; it does not recur. See verified limits, model IDs, privacy terms, and primary sources for Stability AI Developer Platform."
canonical_url: "https://freeinferencing.com/provider/stability_ai_api/"
md_url: "https://freeinferencing.com/provider/stability_ai_api.md"
last_updated: "2026-09-19"
---

# Stability AI Developer Platform

> $0.01 for new accounts; it does not recur.

## Classification

- **Directory:** Current
- **Free access:** One-time trial
- **Status:** Current trial
- **Confidence:** High
- **Payment card:** No
- **Account:** Required
- **Equivalent paid value:** $0.25 once
- **API endpoint:** `https://api.stability.ai`

## Models mentioned

No stable model IDs were recorded in this snapshot.

## Limits and terms

```yaml
signup_credits: 25
credit_value_usd: 0.01
signup_value_usd: 0.25
recurrence: false
expiry: not_published
rate_limits: account_and_endpoint_specific
```

## What happens to your prompts?

**Not private.** Platform API content may be retained and used for model training by default; users must opt out to exclude that secondary use.

Privacy is audited separately from price. Review the current governing terms before sending sensitive or regulated data.

## Data governance and agreements

```yaml
data_governance:
  review_status: reviewed
  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.
agreements:
  terms_of_service: https://platform.stability.ai/docs/terms-of-service
```

## Eligibility

```yaml
account_required: true
qualifying_signup_method: Google social login
payment_method_required: not_documented
```

## API compatibility and modalities

- **Compatibility:** Stability Rest
- **Modalities:** Image, Audio, 3d, Image / vision, Speech / audio


## Before you build with Stability AI Developer Platform

### Read the classification narrowly

This record 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 account and region. “One-time trial” should be interpreted together with the Current directory placement, High confidence, No payment-card status, and the plan-specific sources below.

### Resolve the live model route

No stable model ID is recorded. Resolve the current machine-readable ID, endpoint, authentication method, and request shape from the provider's live documentation before writing fixed production configuration.

### Match the quota to the workload shape

Translate the allowance into peak requests per minute, input and output tokens, concurrency, retries, and every daily or monthly ceiling that applies to the intended account. The first limit reached by the workload is the practical ceiling. A large token pool can still fail interactive bursts, and a high request limit can still fail long-context work. Include tool calls and retry traffic, test the largest realistic payload, and treat research, experimental, and community access as conditional on their eligibility and fair-use terms.

### Preserve billing and privacy boundaries

The recorded payment-card requirement is No, and account access is required. Confirm both in the live signup flow, set provider-side budgets when charges are possible, and observe the balance or usage fields after a complete request. The prompt-handling classification is **Not private** because Platform API content may be retained and used for model training by default; users must opt out to exclude that secondary use. Re-read the terms for the exact route and plan before sending sensitive, regulated, or proprietary content.

### Follow the evidence, then re-check it

This record links 7 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest and most specific governing document or live catalog when sources disagree. A dated finding can become stale even when the page remains online, so retain the source and snapshot that supported the decision and submit a correction when a provider changes a material term.

### Plan fallback without policy drift

A fallback should preserve modality, context length, streaming, structured output, tools, safety controls, and data terms, not only API syntax. Decide which errors may retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. Rotating aliases and free pools can change behavior without changing the endpoint, so retain the response model field and test at least one substitute route before the primary offer becomes unavailable.

### Monitor the offer as a dependency

Capture the model ID, response model, rate-limit headers, usage fields, latency, HTTP status, and provider request identifier. Watch authorization failure, quota exhaustion, catalog removal, policy revision, and balance movement as separate failure modes. Re-check the live catalog and governing sources on a schedule proportionate to the workload's importance, and keep an owner and exit path for any production dependency on volatile free capacity.

### Test one complete request before scaling

Start with the smallest permitted request using the exact credential, model ID, endpoint, region, and account type intended for deployment. Record the status, headers, usage fields, response model, latency, and dashboard balance movement. Then exercise an invalid model, quota exhaustion, or rate limit so failure is explicit and cannot silently switch to a paid route. Validate streaming, structured output, and tool calls separately because a free model can expose fewer features than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and do not send sensitive data until the observed route matches the reviewed agreement.

## Primary sources

- [Developer Platform pricing](https://platform.stability.ai/pricing): Official Pricing
- [Developer Platform documentation](https://platform.stability.ai/docs): Official Docs
- [API key and signup credits](https://kb.stability.ai/knowledge-base/where-can-i-find-my-api-key): Official Docs
- [Platform API training opt-out](https://kb.stability.ai/knowledge-base/opt-out-of-data-training-for-platform-api): Official Policy
- [Platform API Terms of Service](https://platform.stability.ai/docs/terms-of-service): Official Terms
- [Stability AI generative-models repository](https://github.com/Stability-AI/generative-models): Code Hosting Stats
- [Stability AI Developer Platform](https://platform.stability.ai/): Official Product

## Sitemap

See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.