OREOASISFor businesses
For work done by people and by AI helpers

Was the job done right — by someone who answers for it?

Oreoasis gives each piece of work a signed record anyone can check: the rule that was in force, what was actually done, and who signed for it. It proves how the work was done. It never does the work, and it never judges it.

@oreoasis/sdk · an AI helper's action
const client = new OreoasisClient({ apiKey, agent });
 
const receipt = await client.record({
action: { type: "tool.call", summary: "Booked SEA→LHR" },
});
 
receipt.verifyUrl;
// → oreoasis.com/verify/receipt/rcpt_8xKQ2m
signed · anchored · anyone can verify ✓
How it works

Sign. Record. Verify.

01

Sign

Whoever does the work signs the record where it happens — a person with their own key, or an AI helper with its own. Content is hashed on the spot; the raw material never leaves.

02

Record

Oreoasis checks the signature, keeps the version of the rule the work was done under, and chains the record where it can't be quietly rewritten. It records. It doesn't grade.

03

Verify

Every record gets a public link anyone can re-check in their own browser — we are never contacted for the verdict. Whoever received the work can add their own signature to it.

The problem

“Trust me” isn't proof.

  • •Work gets questioned after the fact — by a customer, an auditor, a counterparty who wasn't there.
  • •Logs, timesheets and screenshots are written by the side being questioned. Anyone can edit them, and nobody else has to believe them.
  • •And a record that can only say “followed the rule” or “broke it” punishes the people who adapt to make the work succeed.

A signed record anyone can check — naming the rule, and who answers for it — is.

Who it's for

For anyone whose work has to be believed by someone who wasn't there.

Teams running AI helpers

What the helper did, under which rule — and the named person who signed off the hard cases.

The person doing the work

A record signed as you work, that you can export and keep — never a score.

Whoever receives the work

Countersign what you accepted, over the same bytes. Check any record, free.

Whoever writes the rules

Rules with versions, an author and a review date. No one is judged against a rule that didn't exist yet.

Auditors and reviewers

Re-check any record in your own browser, or offline — without trusting anyone's backend.

Verify without trusting us

Anyone can check it. On their own device.

A record's public link serves a human summary and the machine-checkable proof. The visitor's browser re-checks the signatures itself — you don't trust our backend, and neither do they. Exported records also verify offline, with an open-source verifier.

🔒 oreoasis.com/verify/receipt/rcpt_8xKQ2m
✓ Verified
work
Fitted the kitchen door
rule
door fitting · version 3
signed by
the person who did it
accepted by
the receiver ✓
anchored
public log ✓
verified on your device — we were not contacted
The promise

Verify links never die.

A record you issue stays verifiable forever — even for a cancelled account, and regardless of your plan's retention window (that window only bounds how long you can pull your own history through the API). We anchor history we can never rewrite, and we never take a verify link offline. It's a public promise, and a switching cost that compounds in your favor.

What it never does

Proof of the process — without the surveillance.

Whether the work was good stays a named person's call; Oreoasis records how it was done. A change from the rule is recorded as neutral and classified by a named person — an error, a risk, recklessness, or an improvement worth adopting — and whoever did the work can add their own account. An adopted improvement becomes the next version of the rule, with its author's name on it if they want it. Stopping the work never counts against whoever stopped it.

  • ✕ No productivity scores
  • ✕ No personal error counts
  • ✕ No rankings of people
  • ✕ Nothing that watches people — no keystrokes, screens or location

These aren't settings we could switch on for a customer: the product has no score, count or ranking of people to switch on, and tests keep it that way. A worker's own history is theirs to export — no employer's plan can shorten it.

Pricing

Start free. Verification is free forever.

Free
$0
  • ✓Signed records
  • ✓Public verify links
  • ✓Batched anchoring
  • ✓30-day history
Pro
$29/ mo
  • ✓Everything in Free
  • ✓Per-record anchoring
  • ✓13-month history
  • ✓Evidence exports
Team
$149/ mo
  • ✓Everything in Pro
  • ✓More live API keys
  • ✓3-year history
  • ✓Remove the footer
Done-for-you

We run the workflow. You get warranted, signed work.

An engagement, not a plan — for teams who want the outcome, not the integration. AI does the routine majority, a named human owns the hard exceptions and signs off, and you get a monthly Work Certificate. Priced per warranted outcome, against the cost of labor and the unsigned mistake — a conversation, not a plan.

  • ✓We run the workflow
  • ✓Human sign-off + warranty
  • ✓Monthly Work Certificate
Talk to us →
Founding customers

$290 a year, locked for life — first 20.

The first 20 customers get Pro at $290/year and keep that price for as long as the subscription runs — through every future price change. If you'd like, we'll name you as a founding member (with your permission, never without it). It's the deal for people who back something before it's obvious.

Join the waitlist to claim it

Twenty seats, then it's gone. Pro at the regular price is $29/month; nothing else about the plan differs, and verification stays free forever either way.

Flat monthly pricing, never per seat, never per record — issue as many as you need. Retention (history) is how long you can pull your own records through the API, dashboard, and exports — the public verify link never expires. Verification is free forever, for anyone — including cancelled accounts. Sold worldwide via a Merchant of Record.

Where we are

Zero records issued. We're pre-launch, and saying so.

The counters start at zero and stay honest. The hosted service isn't reachable yet, so nobody outside can record anything with us today. The SDK on npm signs an AI helper's actions on your own machine. Built and tested in the code, but not yet published or reachable: records of work done by a person, versioned rules, changes from the rule classified by a named person, adopted improvements, the receiver's countersignature, and a worker's own export that verifies offline. The page a receiver opens to sign isn't built yet. Join the waitlist and we'll email you the moment the free tier is reachable.

Start here

Join the waitlist for early access.

We're pre-launch — self-serve signup opens the moment hosted checkout and ingest are live. Tell us below what work you need to prove, and to whom, and we'll email you the day it opens. Curious how the loop works first? The quickstart shows the whole thing.

Questions? Talk to a human

Tell us what work you need to prove and who has to believe it. A real person replies — no bot wall.