Numo runs autonomous strategies that reallocate capital continuously across operating accounts, exchanges, custodians, and payment rails. Humanos sits between the agent’s decision and the actual transaction — identity, scope, amount, validity — deterministic yes or no, before any capital moves.
Strategies run autonomously. Capital is reallocated continuously across treasury, exchanges, custodians, and payment rails.
Humanos sits between the agent’s decision and the actual transaction, and checks every action before it goes through — identity, scope, amount, validity.
Agents now move money. Strategies run on their own. Execution spans treasury, exchanges, custodians, and payment rails. The rules that govern what is allowed live in code, scattered across systems, slowly drifting out of sync — and never actually checked at the moment an action happens.
Decisions are defined in one place. Agents act in another. Execution happens across multiple systems. Approvals — when they exist — are captured elsewhere. Nothing answers, in real time, whether a specific action is actually allowed.
Rules duplicated per venue. Policy changes require code deploys. Auditors reconstruct trails after the fact. The firm can show what agents did — not that any given action was allowed.
Before any capital movement, Numo’s agent calls humanos.verify(). Identity, scope, amount, and validity are checked against a signed mandate in real time. Authorized actions execute. Missing authorization is collected at runtime — not silently failed.
Within mandate, within constraints, within validity. The agent proceeds. A Proof is generated — portable, verifiable by any party.
Humanos requests approval instantly (SMS, API), collects KYC or identity verification if required, updates the mandate, and resumes execution once authorization is valid.
Five stages in chronological order. The animation on the right walks through Numo’s €50,000 capital reallocation — signed by the Treasury Lead, verified before any movement, executed across custodian.fireblocks and venue.binance.
Treasury lead authorizes scope, strategy, ceiling, and validity. Humanos issues a machine-verifiable mandate — signed once, reusable across every system that calls verify().
A strategy decides to reallocate capital. The Numo runtime assembles the action with subject, amount, and runtime context. The agent attaches the mandate via x-humanos-mandate.
Before any capital movement, the agent calls humanos.verify(). Constraints, validity, and revocation are checked in 74 ms. Deterministic yes / no.
Authorized → execution proceeds across rails. Not authorized → Humanos doesn’t fail. It collects approval or KYC in real time (SMS, API), updates the mandate, and resumes once authorization is valid.
Every action emits a cryptographic Proof — attached to the execution, portable forever. Auditors, custodians, and counterparties verify the Proof directly against Humanos; nothing reconstructs trails from internal logs.
Nothing moves on assumption. The verify call is non-optional and inline — before any capital movement, not after the fact.
Internal and external systems read from the same authorization source. No fragmentation per venue, custodian, or rail.
Standing mandates replace four-person chains. Humans sign once — not every time.
Every action produces a cryptographic Proof. Auditors look it up directly, instead of piecing together logs after the fact.
Issue a new mandate. Revoke the old one. Effective immediately, everywhere a system verifies.
Approval, KYC, or identity verification is collected the moment it’s needed. Execution resumes once authorization is valid.
Issue once. Verify anywhere — internal services, custodians, exchanges, rails.
Auditors and partners check Proofs without trusting your logs.
No new logic per venue. The integration is the verify() call.
The more systems verify against Humanos, the more valuable a Proof becomes.
Sweep, rebalance, and allocate liquidity across operating accounts and yield venues.
Allocate capital across exchanges, vaults, and on-chain protocols on autonomous schedules.
Run strategies across venues, with strict limits set for each venue, each asset, and each time window.
Coordinate inventory and quote risk across multiple environments and counterparties.
Human authorizes scope. Humanos issues a machine-verifiable mandate, reusable across every system that verifies.
Any external system runs humanos.verify(). Deterministic yes / no.
Out of scope? Request step-up authorization from the human principal in real time — API, SMS, or email.
Cryptographic Proof per action. Auditable forever. Verifiable by anyone.
At that moment, authorization must be verified, the decision must be deterministic, and the outcome must be provable. Everything else follows.
Never assumed. Never after the fact.
Nothing in between. Deterministic yes / no.
Anyone can verify it. Forever.
