Introduction

A cryptographic permission slip for each agent action, issued by the user, scoped to one action, and verified at runtime.

Overview

Humanos brings human authorization into automated workflows. Digital systems like APIs, workflows, and autonomous agents can verify in real time whether a human has approved an action. If an authorization is missing, Humanos can request it immediately through a secure, unified flow, so processes never stall on compliance or pending approvals.

By turning human decisions into programmable, verifiable events, organizations automate more confidently, reduce operational friction, and maintain full traceability of every authorization in a business process.

Base URL: https://api.humanos.tech

SDKs

Skip the raw HTTP calls. Our official SDKs wrap every endpoint in idiomatic bindings for your stack, including auto-signing and webhook decryption.

TypeScript

npm install humanos

For the full SDK documentation click here.

Python

pip install humanos

For the full SDK documentation click here.

C#

dotnet add package Humanos

For the full SDK documentation click here.

Concepts

Concept	Description
Action	A reusable policy template you publish from the dashboard. Declares userParams, the values the user approves; executionParams, the values the agent supplies at execution time; and the rules that compare them.
Mandate	A signed W3C credential of type POLICY that the user issues to your agent. It references one action plus the userParams values that bind this specific approval.
Verifiable Presentation (VP)	A short-lived, signed proof derived from a mandate. The agent presents one each time it wants to act.
Verify	Humanos checks the VP’s signatures, expiry, revocation status, and the action’s rules against the agent’s executionParams. Returns allow or deny.
Revoke	Kills a mandate. Any further VP issuance or verify call is denied.

Lifecycle

A mandate’s lifetime breaks into two flows:

• Request and approval happens once. You define an action, request a mandate, and the user accepts or rejects. On accept, Humanos issues the mandate and you persist its ID.
• Issuance and verification happens on every action. The agent issues a fresh VP from the mandate, Humanos verifies it against the agent’s executionParams, and returns allow or deny.

Walk each flow end to end in the Guides.

Audit trail

Every consequential event in a mandate’s lifecycle, whether issuance, approval, verification, or revocation, is persisted as an immutable, cryptographically signed record that you can query through the activity API. You get a complete, tamper-evident history without logging anything yourself.

W3C standards

Every entity in the Humanos ecosystem, whether an automated system, an organization, or an end user, is identified by a Decentralized Identifier, or DID, that complies with the W3C DID standard. All authorizations are encapsulated as W3C Verifiable Credentials 2.0, giving each authorization a cryptographic proof, a tamper-evident structure, and a complete audit trail.

DID 1.1

W3C standard for verifiable identities with no central registry.

VC 2.0

W3C data model for the credentials every authorization uses.