Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.humanos.tech/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Humanos brings human authorization into automated workflows. Digital systems — APIs, workflows, 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.id
The Humanos flow — an agent prepares an action, calls verify() against a mandate's scope and limits, requests user approval when out of scope, executes on the venue, and emits an anchored proof.

​
SDKs

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

TypeScript

For Node.js & TypeScript.npm install humanos

Python

For Python 3.pip install humanos

C#

For .NET.dotnet add package Humanos

​
Concepts

Humanos gives your agent a cryptographic permission slip — issued by the user, scoped to a specific action, and verified at runtime.
  • Action — a reusable policy template you publish from the dashboard. Declares userParams (values the user approves), executionParams (values the agent supplies at execution time), and the rules that compare them.
  • Mandate — a signed W3C credential (type POLICY) the user issues to your agent. 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 (one-time) — define an action, request a mandate, user accepts or rejects. On accept, Humanos issues the mandate and you persist its ID.
  • Issuance and verification (every action) — the agent issues a fresh VP from the mandate, Humanos verifies it against the agent’s executionParams, and returns allow or deny.
The full step-by-step is in the Quick Start.

​
W3C standards

Every entity in the Humanos ecosystem — automated systems, organizations, end users — is identified using a Decentralized Identifier (DID) compliant with the W3C DID standard. All authorizations are encapsulated as W3C Verifiable Credentials (VC) 2.0, giving each authorization a cryptographic proof, a tamper-evident structure, and a complete audit trail.

DID 1.1

The W3C Decentralized Identifier standard — globally unique, verifiable identities without a central registry.

VC 2.0

The W3C Verifiable Credentials data model — the credential format every authorization uses on the wire.