> ## Documentation Index
> Fetch the complete documentation index at: https://secndai.manicule.dev/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://secndai.manicule.dev/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://secndai.manicule.dev/api/mcp.
> Every agent surface: https://secndai.manicule.dev/.well-known/llms-manifest.json

# Introduction (/)

<!-- agent-signals: reading_time_min: 1 · est_tokens: 459 · updated: 2026-11-12 -->
Related: [Quickstart](/quickstart.md), [Authentication](/authentication.md), [Models](/models.md), [Changelog](/changelog.md), [Confidence and the gate](/confidence.md), [Request limits](/limits.md)

> A situation and a typed question in. A calibrated answer out.

ren-zero is Secnd's decision model. Give it the facts, ask a narrow question, and receive a structured answer with probabilities. Your application controls the available answers and what happens next.

The model is served only through the Secnd API. It does not write a conversation, generate a tool implementation, or run your business logic.

## Three question types

| Question   | Use it for                              | What to inspect                              |
| ---------- | --------------------------------------- | -------------------------------------------- |
| Choice     | Select a queue, document class, or tool | Selected option and probability distribution |
| Score      | Judge against an ordered rubric         | Level probabilities and expected score       |
| True/false | Check one explicit proposition          | Probability assigned to true                 |

## Keep decisions reviewable

A calibrated probability is a frequency statement across comparable decisions, not proof that this decision is correct. Confidence and the server-side gate help route uncertainty to a human. Test your own data and define the cost of a wrong action before enabling automation.

<Note>Private beta. This documentation describes an integration under development. The API reference is the local gateway contract snapshot; a documented proposal is not a deployed capability. Numerical examples are illustrative, not measured model results.</Note>

## Start building

* [Make your first request](/quickstart) with curl, Python, or TypeScript.
* [Choose a question type](/primitives/index) and define the answer space.
* [Understand the gate](/confidence) before connecting an action.
* [Read the failure modes](/honest-limits) and plan a human fallback.