INDORANIACheck

developers · one entrance for any app

Make receipts, check them, keep them.

One entrance for developers of any app: Indusland, KashScript's builds, or yours. Our own apps use the same public API as you.

  • Issuelive

    Oreoasis

    Make receipts and ask the other side to sign.

    Read on
  • Verifybuilt, not live

    Duedale, the desk

    Decide against a rule. Not live yet.

    Read on
  • Holdlive

    The wallet component

    Keep and show receipts inside your app.

    Read on

What stays where it is

This page is the entrance. The engines keep their own addresses, so a receipt always comes from its issuer's own domain.

  • The Issue API

    api.oreoasis.com

    Oreoasis makes and keeps receipts. Its API answers today, at api.oreoasis.com. checked 2026-11-15

    how we know

    The engine's API answers. curl -sL -o /dev/null -w '%{http_code}' https://api.oreoasis.com/healthz → HTTP 200 (2026-11-15)

    live
  • Approval links

    each organisation's own approval address, <name>.sign.oreoasis.com

    Each firm gets its own address to sign on, under sign.oreoasis.com. All of them are served today. checked 2026-11-15

    how we know

    Organisations' own approval addresses resolve. nslookup kashscript.sign.oreoasis.com → resolves (2 addresses) (2026-11-15) · The passkey ceremony's route answers. curl -sL -o /dev/null -w '%{http_code}' -X POST -H 'content-type: application/json' -d '{}' https://api.oreoasis.com/api/v1/ceremony/code → HTTP 400 (2026-11-15)

    live
  • Proof pages and check pages

    oreoasis.com/proof and oreoasis.com/verify

    A proof page shows one receipt to one viewer, checked in that viewer's browser. checked 2026-11-15

    how we know

    The proof page serves. curl -sL -o /dev/null -w '%{http_code}' https://www.oreoasis.com/proof → HTTP 200 (2026-11-15) · The proof page's route answers a request with no token. curl -sL -o /dev/null -w '%{http_code}' -X POST -H 'content-type: application/json' -d '{}' https://api.oreoasis.com/api/v1/proof-pages/open → HTTP 410 (2026-11-15)

    live

Issue: make receipts with Oreoasis

live

Your app signs a receipt with its own key, on your machine, and sends it to your book. Anyone can check it with the link.

Oreoasis makes and keeps receipts. Its API answers today, at api.oreoasis.com. checked 2026-11-15

how we know

The engine's API answers. curl -sL -o /dev/null -w '%{http_code}' https://api.oreoasis.com/healthz → HTTP 200 (2026-11-15)

The Issue SDK, @oreoasis/sdk 0.1.0, is on npm under the MIT licence. checked 2026-11-15

how we know

The Issue SDK is on npm under the MIT licence. npm view @oreoasis/sdk license → license MIT, version 0.1.0 (2026-11-15)

  1. 1

    Open a book

    Sign in at oreoasis.com with your email. There is no password. Your book holds your receipts, your links and your API keys.

    oreoasis.com/signup ↗
  2. 2

    Make an API key

    In your book, make a key for the Issue API. It is shown once. Keep it as OREOASIS_API_KEY.

  3. 3

    Install the SDK

    npm i @oreoasis/sdk # or: bun add @oreoasis/sdk
  4. 4

    Sign and send a receipt

    The receipt is signed in your process with your app's own key. Inputs and outputs are reduced to codes on your machine; their content never leaves it.

    import { OreoasisClient, generateAgentKey, agentKeyFromSecret, exportAgentSecret } from "@oreoasis/sdk"; import { readFile, writeFile } from "node:fs/promises"; // Your app's signing key. Keep it: a new key on every start is a new signer every start. async function loadOrCreateKey(name: string) { const path = process.env.AGENT_KEY_PATH ?? "./.agent-key"; try { return await agentKeyFromSecret(name, await readFile(path, "utf8")); } catch { const key = await generateAgentKey(name); await writeFile(path, exportAgentSecret(key), { mode: 0o600 }); return key; } } const client = new OreoasisClient({ apiKey: process.env.OREOASIS_API_KEY!, agent: await loadOrCreateKey("my-app"), }); const receipt = await client.record({ action: { type: "tool.call", tool: "search_flights", summary: "Searched flights" }, inputs: [{ name: "query", content: "the search the user asked for" }], // reduced to a code locally outputs: [{ name: "result", content: "what came back" }], // reduced to a code locally }); console.log(receipt.verifyUrl); // the receipt's check page, on oreoasis.com
  5. 5

    Check it

    Open the receipt's verifyUrl. The page checks the signature in the viewer's own browser. Or check the receipt file on your own computer with the open checker, below.

What never goes in a receipt

  • meta is signed as written, and anyone holding the link can read it. A signed receipt cannot be taken back.
  • So meta never carries a name, an email, an account number, or words a customer wrote. Use it for a workflow id.
  • Keep your app's key as you keep any credential. Whoever holds it can sign as your app.

The receipt's page labels the time the host received it. A public time witness on every receipt is not built yet.

PROMPT-PATH §10.S: the witness on every receipt waits (OA-Q5); SPR-3 reports what the anchoring code does today.

Checked on 2026-11-05: the API answers and asks for a key. This walk-through was not run end to end that day.

Deployed routes, as they answered an empty request on 2026-11-05
  • POST /api/v1/receipts401your app's own signed receipt (the SDK's record)
  • GET /api/v1/engagements401Client Sign-off: engagements and milestones in your book
  • POST /api/v1/approvals/notes400a reviewer's approval on a link
  • POST /api/v1/proof-pages/open410a proof page's one copy, for one viewer
  • POST /api/v1/internship-weeks400Hours that Count: a student's week
  • POST /api/v1/track-records/open410a firm's public track record
  • POST /mcp401the issuer's MCP server

400, 401 and 410 mean the route exists and refused an empty or unsigned request. The full reference is Oreoasis's product contract, which is not public yet.

Verify: decisions at the desk

built, not live

Not yet live

The desk is being built in Duedale's own code (ECOSYSTEM d92). Its API arrives with it. This is what it is being built to do.

  • A packet of receipts and a rule's version go in.
  • Yes, not yet, or to a person comes out, with the lines of the rule that decided it.
  • An automatic yes can be worked out again by anyone holding the packet and the rule's version.
  • A rule's criteria are an OpenID4VP query (DCQL) with a DMN condition. Packets arrive by presentation, never by lookup.
  • The desk reads receipts only through the open checker and OpenID4VP, never through an engine's database.
  • A refusal is never automatic: only a named person says no.

The desk's API is built with the desk. It is not live. checked 2026-11-15

how we know

The desk's first cut is in Duedale's history (SPR-2). git -C "Duedale 2.0" cat-file -e de0bd8f^{commit} → present: de0bd8f SPR-2: the decisions desk, first cut — packages/desk and apps/desk, practice-ready… (2026-11-15)

Live today: the open checker

live

Check a receipt yourself, free, without asking us. In a browser at indorania.org/verify, or on your computer with @kashscript/attest (Apache-2.0).

npx -y @kashscript/attest@0.1.8 verify <receipt.json> --key <key.txt> --signer-did <did>

This form was tested with this site's practice receipts, from an empty folder, on Windows only (2026-09-24).

Hold: keep receipts in a wallet

live

@kashscript/wallet lets an app keep receipts for its user and show them, one copy for each viewer. Indusland's app is meant to embed it.

npm i @kashscript/wallet@alpha
  • Licence: Apache-2.0. It is an alpha, so its interface may still change.
  • The person holds the key. No person's key is ever kept on a server.
  • Chakor, our own wallet app, is built on it. Chakor has never run on a phone.
  • The design: receive by OpenID4VCI from the issuer's own address, and show by OpenID4VP. Neither is tested against another wallet yet.

@kashscript/wallet is on npm as an alpha. Its licence is Apache-2.0. checked 2026-11-15

how we know

The wallet component is on npm as an alpha, under Apache-2.0. npm view @kashscript/wallet license → license Apache-2.0, version 0.1.0-alpha.6 (2026-11-15)

Chakor, the wallet, is built. It has never run on a phone, and its trust list names no issuer. checked 2026-11-15

how we know

Chakor's device report is still empty. grep -E 'Every cell is empty because nothing has been run on' Indorania/apps/chakor/README.md → the line is there (2026-11-15) · The signed trust list names no issuer. grep -E '"issuers":\s*\[\s*\]' Indorania/apps/site-indorania/public/trust/ecosystem.v1.json (in the signed payload) → the line is there (2026-11-15)

The MCP servers

  • Oreoasis's MCP serverlive

    https://api.oreoasis.com/mcp, with a key from your book

    For an issuer's own agents and tools. Its tools draft and read. None approves or signs.

    Oreoasis's MCP server answers and asks for a key. Its tools draft and read. None approves or signs. checked 2026-11-15

    how we know

    The MCP server asks for a key. curl -sL -o /dev/null -w '%{http_code}' -X POST -H 'content-type: application/json' -d '{}' https://api.oreoasis.com/mcp → HTTP 401 (2026-11-15)

  • The door's MCP serverroadmap

    not yet live

    For a person's own agent, to gather a packet for a door. The person always sends it.

    An MCP server for a person's own agent, to gather a packet, is not built. The person always sends it. checked 2026-11-15

    how we know

    Agents prepare and people sign (d84 F). the entry of d84 in ECOSYSTEM.md holds "Agents prepare and people sign" → the phrase is there (2026-11-15)

How an organisation gets a book and a key

  1. 1Open a book at oreoasis.com. You sign in by email, with no password. Open a book ↗
  2. 2Make an API key in your book. It is shown once.
  3. 3Run practice links first. They say practice, and no customer should rely on them.
  4. 4For a customer's link, your organisation's own approval address is set up by hand. None is served yet.
  5. 5A desk for deciders comes with the desk. It is not live yet.

Scope and price are agreed in writing and invoiced by hand. There is no self-serve billing.

d73(a)3; d84(c); content/status.ts `prices`.

What is open

  • Open under Apache-2.0: the formats, the checker (@kashscript/attest), the wallet component and Chakor.
  • The Issue SDK, @oreoasis/sdk, is MIT.
  • Each engine's core stays private until there is a named reason to open it. Its APIs and SDKs stay open.

ECOSYSTEM d87; npm view license, 2026-11-05.

Not yet true

The desk's API is not live.

No organisation's own approval address is served yet, so every link says practice.

A public time witness on every receipt is not built.