Cerebras Inference

# Fix list: Cerebras Inference

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/cerebras-inference, the October 2026 research run, assessed 19 October 2026. Grade B, 68.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 Cerebras Inference: 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. Payments & pricing, 20 out of 100, up to 10 more on the total

Why it scored 20: No machine payment protocol found in the reviewed API and billing docs (0). Public token prices (20). The $5 trial requires a verified payment method (0). Account creation and payment setup require a person (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.

## 2. Reliability, 70 out of 100, up to 6 more on the total

Why it scored 70: Public component status history (20). One major partial service disruption lasting about five hours on 25 September within the last 90 days (10). Numeric rate-limit tables, although trial figures disagree between two pages (15). SDK error classes and bounded retries with backoff (15). No public shared-inference SLA established (0). Shared inference is generally available (10).

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.

## 3. Security & auth, 70 out of 100, up to 5.3 more on the total

Why it scored 70: Revocable Bearer keys with rotation instructions (20). Paid-project boundaries, but no inference-only key permission found (10 of 20). GPT OSS documentation warns about undeclared tool calls and tells callers to validate them (10 of 15). Request and audit logs in the console (15). Trust centre lists SOC 2 Type II, with reports requiring access (15 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.

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

Made of editorial 45, provenance 71.

Why it scored 58: SDK is Apache-2.0, but the hosted cloud terms were not readable in this session (5 of 30). Privacy policy states no inference input/output retention but gives no fixed operational-log retention period (20 of 30). Dated deprecations and API-version migration guidance without a general minimum notice commitment found (10 of 20). Trust centre lists subprocessors and infrastructure controls, but full data-location details were not established (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: cerebras.ai, no registry record we could read (0 of 15)
- Terms of service: published, but our reader couldn't read it (7 of 10)
- Privacy policy: read, states 7 of the 8 things a reader expects (9.3 of 10)
- security.txt: not found (0 of 10)

## 5. Maintenance & community, 65 out of 100, up to 3.1 more on the total

Why it scored 65: Dated service update on 9 October (30), at least three changelog entries in 90 days (20), support responsiveness not established (0), official Python and TypeScript SDKs (15). Runtime dependency health and CI were not audited (0).

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.

## 6. Agent ergonomics, 85 out of 100, up to 2.4 more on the total

Why it scored 85: Model API with bounded output and compact request shape (25). Output token controls, streaming and structured outputs (20). Documented error classes and fixes (20). Bounded transient retries but no request-deduplication guarantee established (5 of 20). Defaults and official Python and TypeScript SDKs (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.

## 7. Schema & documentation, 93 out of 100, up to 1.1 more on the total

Why it scored 93: Public OpenAPI 3.1 (25), llms.txt and Markdown pages (10), documented capability and compatibility limits (16 of 20), typed inputs and constrained parameters (13 of 15), examples and error guidance (14 of 15), and API versions plus dated changelog (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.

## 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.

- Authenticated output quality, latency, throughput and billing were not tested.
- SDK dependency health and support response times were not audited.
- The central trial limits say 5 RPM while the GPT OSS page says 30 RPM. Confirm account-specific quotas in the console.
- The applicable cloud terms could not be read. The public privacy policy excludes processing on behalf of customers, so contract-specific data handling may differ.

## Weaknesses

- Trial access requires a verified payment method and ends after $5 or 30 days
- The GPT OSS model page and central rate-limit page disagree on trial request limits
- Cloud terms returned an empty page to the reader; no public shared-inference SLA was established

## 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 CEREBRAS_API_KEY and use https://api.cerebras.ai/v1 with an OpenAI-compatible client.
- Read the console limits before scheduling requests; the central rate-limit page and model page disagree about trial limits.
- Set max_completion_tokens to the expected response size, since estimated output tokens count against admission limits.
- Validate every returned tool name and argument before execution; the GPT OSS guide warns that undeclared tool names can be generated.

## What the review panel asked for

- key expiry option
- inference-only key role
- Reconcile the rate-limit pages
- Reconcile the trial limit figures
- Card-free trial

## 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.