Ora
All documentation Overview

Getting started

IntroductionQuickstart

Concepts

StateQuestionsConfidence

Question types

yes_no (noul)choicescore

Actions & workflows

OverviewDestinationsRules and templatesWebhooks and signaturesAsk by symbolWorkflows

Limits & pricing

Rate limitsPricing

API reference

POST /v1/systemoneGET /v1/modelsErrors

Resources

Models & versions

Documentation

How to call ora1: send a state and named, typed questions; get typed answers back, then act on them with rules, actions and scheduled workflows.

Getting started

  • IntroductionThis model makes fast, structured decisions for software. You send a state (the content to judge) and a set of named, typed questions ; you get back typed…
  • QuickstartGet from zero to your first answer in about 5 minutes: create a key, send one request, read the answer. Prefer clicking? See Or start in the Playground below.

Concepts

  • StateThe content every question in a request refers to: a string, an object or an array. Prefer objects with named fields for structured records. Keep content in…
  • QuestionsA request carries one or more named questions. Each is answered independently against the same state, and answers come back under the same names. Keep…
  • Confidencechoice: (p max − 1/n) / (1 − 1/n). score: 1 − (expected distance from the most likely level ÷ that distance under a uniform guess), floored at 0. yes_no has…

Question types

  • yes_no (noul)A yes/no judgment returned as the probability of yes , from 0 to 1. noul is accepted as an alias and answers in the same shape under its own name.
  • choicePick one option from 1 to 255. Criteria map option name → description; a missing description is judged by the name alone.
  • scoreAn ordinal rating over 1–10 ordered levels; position is the level, starting at 0. score is the probability-weighted average level, so it can fall between…

Actions & workflows

  • OverviewA request can say what to do with its answers. Add an actions list: each action has a rule on the answers ( when ), what to do ( slack , webhook or email …
  • DestinationsA fired action is delivered to a connection : a named destination you set up once under Settings → Connections . Requests and workflows only name it (…
  • Rules and templatesRules are checked before anything runs: an unknown question, an option a choice doesn't have, or comparing text with a number is a 422 with the exact…
  • Webhooks and signaturesA webhook action POSTs JSON to the connection's https URL, with your extra headers, X-Jev-Delivery: <run id> and X-Jev-Signature: t=<unix seconds>,v1=<hex>…
  • Ask by symbolWith ora1 , send just a symbol and leave out context (or set "context": "latest" ). We fill in the symbol's numbers from its latest completed session…
  • WorkflowsA workflow runs the same questions and actions for every symbol on a watchlist, on the days and time you choose (New York time). Each symbol is asked by…

Limits & pricing

  • Rate limitsLimits are per organization and shared by all its keys and the Playground: requests per second and input tokens per second . Each allows a one-second burst.…
  • PricingYou pay per input token ; output tokens are free. The current price per million input tokens is on the pricing page .

API reference

  • POST /v1/systemoneBase URL https://oramodel.com . Auth: Authorization: Bearer <API key> . Body: JSON, at most 4 MiB.
  • GET /v1/modelsLists model aliases. Versioned IDs are accepted in model whether or not they're listed.
  • ErrorsErrors: Ora documentation.

Resources

  • Models & versionsThere is one model to call: ora1 . It reads your request and answers with the right engine:
Create an account Open the Playground Everything here also lives in the console, next to your keys and usage.