StepFun API

# Fix list: StepFun API

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/stepfun-api, the October 2026 research run, assessed 12 October 2026. Grade E, 44.4 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on StepFun API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Reliability, 28 out of 100, up to 14.4 more on the total

Why it scored 28: No status page read. status.stepfun.ai refused our reader by robots.txt and the shell couldn't connect, so we couldn't establish whether it is a status page or read any history. Scored absent for both lines, with 5 for unreadable history, and named in the open questions (0 + 5). Rate limits published with numbers per tier, from 5 concurrent, 100 RPM and 500,000 TPM to 130, 2,600 and 13,000,000 (15). The error and exception guides say to retry 429, 500, 503 and 504 after a short delay, with no Retry-After header, backoff schedule or idempotency guidance (8 of 15). No SLA found in the terms or pricing (0). Step 5 Preview is labelled a preview (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 2. Security & auth, 41 out of 100, up to 10.3 more on the total

Why it scored 41: Model reading. Bearer API keys, revocable by deletion. Organisations can create one key per project, billed to a project's credit with a per-member cap. No scopes or read-only keys found (20 of 30). Training on API data is not off by default in plain words. The privacy policy (effective 7 August 2026) says StepFun may use and retain data to improve its models, including training and fine-tuning where law and program terms permit, and the terms name early-access programmes as one such case. No opt-out found (5 of 20). No retention period for prompts and outputs and no zero-retention option. IP addresses are kept three years (3 of 15). The console's usage details list each billed call by key, model and date, with export (8 of 15). No security.txt, bug bounty or certification found. A DPA with breach notification exists (5 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 3. Payments & pricing, 20 out of 100, up to 10 more on the total

Why it scored 20: No machine payment protocol (0). Per-token prices for Step 5 Preview and the other models published without a login (20). No free API allowance found. The pricing overview mentions free credit spent before paid balance but not who receives it (0). Browser sign-up and a prepaid top-up, with identity verification for individual rate-limit tiers (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 4. Schema & documentation, 53 out of 100, up to 7.6 more on the total

Why it scored 53: No OpenAPI or similar machine-readable contract found. The API reference is Markdown pages (0). llms.txt at platform.stepfun.ai/docs/llms.txt, and every page has a Markdown copy (10). The Chat Completions reference describes each parameter with its default, and the model page lists what Step 5 Preview supports, but little on when not to use an option (12 of 20). Tool definitions take JSON Schema parameters, structured output takes a JSON Schema with `strict: true`, and `reasoning_effort` is an enum of low, medium and high. No `tool_choice` parameter is documented (11 of 15). Worked requests and responses on each page, and an error table of eight codes with causes and fixes, but no error bodies (12 of 15). No API changelog. A model lifecycle page with dated retirements and announcement pages (8 of 15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 5. Agent ergonomics, 68 out of 100, up to 5.2 more on the total

Why it scored 68: Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool calls through Chat Completions, Responses and Messages, with no documented way to force or forbid a call (15 of 20). Strict JSON Schema output on Step 5 Preview (13 of 15). Prompt caching with a published cache-hit price at a tenth of the miss price (15). 1M-token context and 64k output (15). No batch endpoint found (0). No official SDK. The docs use the OpenAI and Anthropic clients against compatible endpoints (0). Eight error codes with a fix each, plus `finish_reason` handling for length, content filter and tool calls (10 of 15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 6. Maintenance & community, 50 out of 100, up to 4.4 more on the total

Why it scored 50: Model reading. The image models `step-2x-large` and `step-image-edit-2` were retired on 10 October 2026, and a Step 5 Preview price change is announced for 14 October (30). No stated notice period. The 10 October image retirement had a dated notice page and the July retirements a migration table, but we couldn't date when either notice went up (4 of 12). One retirement date in the last 90 days, 10 October, with nine models retired on 8 July just outside that window (6 of 8). Dated announcements, a Discord server and platform@stepfun.com for support. We didn't test whether either answers (10 of 15). No official SDK (0 of 15, 0 of 10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## 7. Transparency & trust, 58 out of 100, up to 3.7 more on the total

Made of editorial 51, provenance 65.

Why it scored 58: Closed service with clear terms under Hong Kong law, with HKIAC arbitration and liability capped at six months of fees. Some earlier Step models have open weights, which doesn't change the hosted service (15). The privacy policy, terms and DPA agree that data may be used for training under program terms, but the terms' licence to Content is broad and perpetual, no retention period is given for prompts and outputs, and no subprocessor list was found (12 of 30). A model lifecycle page with dated retirements and replacements (14 of 20). Servers are disclosed as in the United States. The DPA gives general authorisation for subprocessors without a published list (10 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Domain age: stepfun.ai, no registry record we could read (0 of 15)
- Status page: not found (0 of 10)
- security.txt: not found (0 of 10)

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: status.stepfun.ai, refused by robots.txt for our reader and unreachable from the shell. Whether StepFun publishes a status page and its incident history
- unchecked: the release date of Step 5 Preview. No first-hand page gave one, and press reports were not used
- unchecked: whether the international platform also changes Step 5 Preview's cache-hit price on 14 October 2026. Only the China docs announce it
- unchecked: who receives the free credit the pricing overview mentions, and how much
- No authenticated call was made. That `step-5-preview` answers on api.stepfun.ai rests on the model page, pricing page and API references, which list it
- No StepFun listing existed before. This listing covers the whole API with Step 5 Preview as its flagship model, in line with the other model-vendor APIs in this category

## Weaknesses

- Step 5 Preview is labelled a preview, and no release date or support commitment was found
- No free API allowance found, and individual accounts need identity verification for tiered limits
- No OpenAPI file, no official SDK and no batch endpoint found
- The privacy policy allows training on user data where law and program terms permit, with no zero-retention option found
- No SLA, security.txt or certification found

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Set `max_tokens` yourself. It defaults to unlimited on Step 5 Preview, and reasoning tokens are billed as output
- Use `response_format` with `type: json_schema` and `strict: true` when the shape matters. JSON Mode alone isn't schema-checked
- Back off and retry on 429, 500, 503 and 504. The docs give no Retry-After header or backoff schedule
- Expect HTTP 451 or `finish_reason: content_filter` when content fails StepFun's review, and don't retry the same input
- Use api.stepfun.ai for the international platform. api.stepfun.com is the China platform with yuan pricing

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.