NobleCloak
How it works

One approval, start to finish.

Every organization that has ever existed runs on one question: who may do this alone, and who has to ask first. Approvals is how an AI agent asks, and how the answer comes back.

How it works

Three steps, one record

  1. 1

    The agent proposes

    Your agent reaches an action that touches money, customers or production. Policy, not your code, decides whether it needs a person, and which person.

    ar-close · run 7f3a · 13:59:02
    action
    wire_transfer
    to
    Harbor Supply
    amount
    $48,200.00
    policy
    Wire transfers need Finance approval
    state
    Run paused on its own checkpoint
  2. 2

    A person decides

    The right approver gets the request where they already work: Slack or the web inbox, with Teams and email coming soon. An approval covers one action, never the rest of the session, and a sub-agent never inherits its parent's approval.

    Slack · #finance-approvals
    NobleCloak needs a Finance approver for one action from ar-close: wire $48,200.00 to Harbor Supply.
    requested by
    D. Park (requester, cannot approve from Slack)
    choices
    Approve this action · Deny
    scope
    Covers this action only
  3. 3

    The record stays

    After a named approver decides, the agent itself resumes, exactly once. Prompt, action, policy, approver and outcome become one line in the Record of Decisions. Searchable on every plan; export comes with Business and Enterprise.

    Record of Decisions · rec_01HZ4Q7M…
    • Prompt: Close out AR for September…
    • Action: wire_transfer · $48,200.00
    • Policy: Wire transfers need Finance approval
    • Decision: approved · M. Alvarez · 14:02:11
    • Outcome: Resumed once · wire sent · gateway observed
See it applied

The same three steps, on a real task.

A bank asks an AI agent to release a wire. The policy sends the release to a named treasury officer, who decides, and the decision lands in the record. The use cases show the same pattern for other teams.

Your runtime already gives you

The pause is built in. The people are not.

A durable pause. An allow or deny check. A boolean hook per tool.

What it leaves to you, until now
  • —Who may approve, and who is asked
  • —Reaching that person where they already work
  • —Applying the answer to the action that is waiting
  • —One policy and one record across every surface
The Record of Decisions

Every prompt, the action it caused, and who said yes.

Searchable on every plan; export and SIEM feeds come with Business and Enterprise. Entries say whether the gateway saw the call or the runtime reported it. Longer history comes with the plan; examiner evidence packs are coming.

TimeActorActionDecisionByAttestation
14:02:11ar-closewire_transfer $48,200approvedm.alvarezobserved
13:47:02support-botrefund $1,150deniedj.okaforobserved
13:40:58researchsend_email (external)awaitingFinance roleasserted
13:12:30ar-closeread_ledgerallowedpolicyobserved
Deploy

One API. Designed to run where your data must live.

  • Hosted

    Our control plane, your runtime.

    Available
  • Dedicated tenant

    Your own database, private network option.

    Beta
  • Edge, in your cloud

    The same service, run from your own cloud account.

    Coming soon
Regulated

Examined? Start with the AI Trust Report.

A read-only assessment of the AI tools your own organization uses, packaged for an examiner. Built for banks, credit unions and RIAs to get a first answer, then grow into Approvals on the Enterprise plan, with Proof (coming).