The intent-to-outcome runtime

Tell the Internet what you want done.

Describe an outcome in a sentence. OMNIRA plans it, shows you what it will cost, asks before it acts, runs it, and proves it worked — then keeps it running.

No card · no API keys · nothing is spent in practice mode

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
You say

OMNIRA understands
Objective
Watch 3 pages
Schedule
Every 6 hours
Budget
$3.00 per month
Tell you
Only what matters

A replay of real output from practice mode, where AI is simulated and nothing is charged

How it works

A sentence goes in. A verified outcome comes out.

Not a chatbot and not a workflow builder. You state what should be true; OMNIRA works out how, and shows its working at every step.

  1. 01

    Intent

    You write a sentence. OMNIRA turns it into a typed goal — and asks when something is unclear instead of guessing.

  2. 02

    Plan

    Ordinary code, not a model, lays out the steps, picks who does each one and prices the whole thing.

  3. 03

    Authorize

    You see what it will do, cost and touch. Nothing reaches outside without your say.

  4. 04

    Execute

    It runs, retries what is temporary, switches provider when one fails, and never repeats what already worked.

  5. 05

    Verify

    A run counts as a success only if its criteria hold against what was actually stored and sent.

The rule everything follows

Models propose.
Code decides.

No model writes the plan

Plans are assembled by deterministic code from a catalogue of typed steps, so the same request always yields the same plan — and a hostile web page cannot change it.

No model grants permission

Risk tiers, budgets and approvals are rules. They are checked when the plan is made and again, step by step, as it runs.

AI only where it earns its place

If code can decide, code decides. A model is called when judgement is needed, and every call it was spared is counted.

What it does today

Three outcomes, finished rather than promised.

OMNIRA starts narrow on purpose. Ask for something outside these and it will say so plainly — or ask what you mean — instead of pretending.

Watch01

Know when a page really changes.

“Monitor these three sites every six hours. Tell me when something meaningful changes. Keep it under $3 a month.”
  • Dates, counters and reshuffles are ignored by code
  • AI is asked only about real differences
  • You hear about it only when it matters
Try this one
Follow02

A briefing with nothing you have read before.

“Research solid-state batteries every morning and only tell me information I haven't already seen.”
  • Searches Hacker News, arXiv and your feeds
  • Remembers everything it has reported
  • Stays silent when nothing is new
Try this one
Act03

Deliver every event exactly once.

“Send this JSON to my API whenever this webhook receives a new order, but never retry successful requests.”
  • A private address for your events
  • Retries timeouts, never a success
  • Tells you when delivery fails for good
Try this one
Nothing happens off the record

Every action, decision and fraction of a cent — written down.

Each run leaves an append-only ledger: what was done, who did it, which rule allowed it, how long it took and what it cost. The database itself refuses to edit or delete a line.

It is the audit trail, the debugger and the bill — the same record, so they can never disagree.

Event ledger · one runappend-only
120EXECUTION_CREATEDplan v1 · estimated $0.000775
126POLICY_ALLOWEDreading example.com was approved · tier 0
130PROVIDER_SELECTEDsafe HTTP client · score 0.74
143TOOL_CALLEDnews.ycombinator.com · 200 · 875 ms$0.00000175
184AI_SKIPPEDa deterministic check showed AI was not needed
197BUDGET_CHECKEDworst case $0.0074 · within limits
207MODEL_CALLEDjudge whether the change matters · 414 tokens in$0.000714
231VERIFICATION_PASSED4 of 4 checks hold
232EXECUTION_SUCCEEDEDno important changes · 1.05 s$0.000716
Built to be left alone

Autonomy you can walk away from.

Software that acts for you has to be bounded before it is clever. Each of these is enforced in code and covered by tests.

Stops before it overspends

Budgets per step, per run, per day and per month. Before a limit would be crossed, the run pauses and asks you.

Never sends twice

Anything that acts on the outside world is recorded first. A delivery that succeeded is not repeated — even after a crash.

Picks up where it stopped

State lives in the database, not in memory. A worker can die mid-run and another finishes the job without redoing finished steps.

Cannot be talked into it

Web pages are data, never instructions. A model can describe a change; it cannot name a recipient, a target or an action.

Secrets stay secret

Credentials are encrypted, referenced by name, resolved at the last moment and kept out of prompts, logs and the ledger.

Stays on the public Internet

Fetches are refused for private networks, local services and cloud metadata — including through redirects and DNS tricks.

Cost is a first-class constraint

Priced before it runs. Counted to the millionth of a dollar.

$0.000006

A check where nothing changed

Three pages fetched and compared by ordinary code. No model was called, so none was paid for.

$0.0007

A check where one page changed

Code filtered out the noise; a model judged the one real difference. That single call is nearly the whole cost.

$0.09

A month of watching three sites

The most likely monthly cost of checking every six hours. You see the full range, and the worst case, before you approve.

Figures are from runs in practice mode, where model prices are simulated and nothing is actually charged. Real prices come from a dated, versioned price list — a model without a price on that list is never used.

What do you want done?

You will see the plan and its cost before anything runs