Docs
Documentation / Ren 1.1

Models

Pin a model before tuning a workflow.

Ren 1.1 is available through the API only. Model weights are not distributed with the SDKs.

IdentifierMeaning
ren-1.1.0Ren 1.1; full release ID, released 2026-11-13
ren-latestStable alias; currently resolves to ren-1.1.0
ren-previewPreview alias; currently resolves to ren-1.1.0

A semantic version is an identifier, not a benchmark claim or a guarantee that your account can access it. In the current gateway, both aliases resolve to the configured pinned model.

bash
curl --fail-with-body https://api.secndai.com/v1/models \
  -H "Authorization: Bearer $SECND_API_KEY"

The response has a data array listing the full release ID and both aliases. Each entry includes id, aliases, release_date (date only, 2026-11-13), max_options, max_input_tokens, and price_per_million_input_tokens_usd. Decision responses return the resolved ID in both model and usage.model.

Unknown IDs, shortened IDs such as ren-1.1, and case variants such as REN-LATEST return 400 with code: "unknown_model" and a message naming ren-1.1.0, ren-latest, and ren-preview. IDs are case-sensitive.

Version changes

Pin the full ID when comparing distributions or choosing thresholds. When changing it, reevaluate the full workflow on permitted development data, including human escalation and downstream actions. An alias can change without your application code changing.

Usage and price

Every successful decision includes usage.input_tokens, usage.output_tokens (always 0), and usage.model. Input usage is measured on the complete formatted input. The price per million input tokens is operator configuration exposed by model discovery; there is no public fixed price or billing-provider integration promised here.

Local development's configured price is not a commercial offer. Agree production access and pricing with Secnd before relying on them.

Read Markdown ↗