Skip to main content
D1 turns a text or JSON context into decisions over outcomes you define. Use it to route a support request, select a tool, check an answer against its sources, or decide when a person should take over.

Make a decision

With an API key from the console, try a yes/no question:
Read decisions.needs_help.p_yes for the yes score and decisions.needs_help.action for the selected action. Check model and any fallback to see which model answered. The quickstart covers account access and handling the result.

Three decision types

Mix types in one request. Results are keyed by your decision IDs. Add an abstention policy when uncertain cases should go to review.
Probabilities describe the declared alternatives. They are not a guarantee that an answer is correct. Test your wording, labels and action thresholds on representative cases before using them to automate work.

From a first request to a better decision

Build an integration

Send a request, read an action, and handle failures.

Try a real workflow

Start with the same recipes used in the console playground.

Improve with your data

Review labels, tune wording and train a version.

Connect an agent

Use the repository skill or the MCP tools.
The API Reference tab describes current customer endpoints. Its interactive calls target console.sqwish.ai and can perform real work using the key you supply.