Companies
Platforms, fintechs and whoever puts AI agents to act: the authority is born from a present person.
Revocable at any time, with a receipt.
A software agent that pays, reconciles or changes records on someone's behalf needs an authority an auditor can check afterwards. At Hummand, that authority is a mandate: a person with proven presence states what the agent may do, with limits and validity, and every action of the agent is checked against it, on the spot, with a receipt.
A mandate is the authorization a person gives an AI agent, with limits and a term, revocable at any time. A delegated act is each action taken on their behalf, checked against that mandate.
No client name appears here, and no market figure. Every capability carries the label of its state: available, in accreditation or target architecture; what does not exist yet is written down, not hidden.
POST /v1/atos
{
"tipo": "mandato.agente",
"sujeito": { "ref_cliente": "operator-123" },
"mandatario": { "ref": "reconciliation-agent" },
"escopo": {
"acoes": ["reconciliation"],
"limites": { "valor": 5000 },
"validade_ate": "2026-12-31T23:59:59Z",
"revogavel": true
}
}
POST /v1/atos
{
"tipo": "ato.delegado",
"sujeito": { "ref_cliente": "reconciliation-agent" },
"delegado": {
"mandato_ref": "<mandate id>",
"acao": "reconciliation",
"valores": { "valor": 1200 }
}
}
POST /v1/mandatos/<mandate id>/revogarAgent mandate
Description
Grant, act, revoke: the agent's authority is born from a present person, and every step leaves a receipt.
1.0Grantavailable
The person opens the link, proves live presence and consents to the written scope: the permitted actions, the limits and the validity. The mandate is born with a receipt, does not change afterwards and is revocable by default.
See Mandate2.0Act under the mandateavailable
Every action of the agent is a delegated act, at level 0, with no new human: Hummand checks that the mandate exists, is valid, has not been revoked and that the action fits the scope and the limits. It resolves on the spot, and the receipt says whether it passed.
The content of the action, such as recipient or purpose, never reaches Hummand: only the category of the action and the values the scope asked to compare.
3.0Revokeavailable
A mandate falls by an API call or from the dashboard; all of an agent's, or of a client's, fall at once, with one receipt per mandate brought down. Whoever caches the authority gets the notice by webhook.
See Docs4.0The refusal is proof tooavailable
An action outside the scope, above the limit or after revocation is refused and leaves a receipt. The attempt becomes a fact the auditor checks, and shows in Alerts as an act outside the mandate.
See AlertsStep-up
Description
A new presence in the middle of a sensitive action, by whoever operates or whoever transacts. It is not login: it is the proof inside the action.
1.0Operator step-upavailable
The employee proves presence in the middle of the sensitive operation, and the receipt says who it was. In production since 2026-09-17 in Hummand's own human review queue: whoever decides a case proves presence before deciding, and the case's receipt says who reviewed it.
2.0Transaction step-uptarget architecture
A transfer above a value, a limit change, a new device: the person proves presence in the middle of the action. The policy can shorten it to level 1 with a passkey when there is a recent positive act.
See the step-up3.0Registration step-uptarget architecture
Changing e-mail, phone or payment key only with the person present. Never reuses a previous act.
4.0Dual operatortarget architecture
Two distinct people, each with presence, approving the same operation. Composite receipt, one per operator, linked by the group.
Integration
Description
One door, the API, with the published contract; the dashboard uses the same one.
1.0API and contractavailable
One POST creates any act, with the type, the subject by the client's reference and the minimum level, with idempotent creation. Versioned OpenAPI contract, and a TypeScript client generated from it.
See Docs2.0Webhooksavailable
Signed delivery, with a rotatable secret and a delivery log: act completed, receipt issued and mandate revoked, among others.
3.0Receipt verifiable without Hummandavailable
The receipt is verified with the published public key, without calling Hummand: in the browser or on the command line, offline.
See Receipt4.0Dashboard, no codeavailable
Generate the link for an act, follow mandates and revoke, with no integration, through the same door as the API.
See the Dashboard5.0Python SDK and mandate MCP serveravailable
pip install hummand brings the API client and offline verification of the receipt, with the public key pinned by whoever verifies. For an agent that speaks MCP, pip install "hummand[mcp]" adds three tools: request the mandate, check whether the action fits it, and look it up. None of them revokes.
The agent asks for authorization; the resource only executes with a receipt. The server informs the agent, and the guarantee comes from the system that executes the action, checking the receipt before acting. The server key only creates agent mandates and delegated acts.
See on PyPIHow to contract
Description
By contract, for companies and for government: scope, volume of acts, assurance level and data residency defined in the conversation. In the public sector, through the instruments of public procurement.
1.0How we charge
Per completed act, approved or rejected, with a minimum allowance in the annual contract and a lower price per act as volume grows. An act that expires or is cancelled without a result is not charged. The amount is set in the contract.
2.0Request a demo
By e-mail, with the company, the product, the act you want to prove and the approximate volume. The answer comes from the people who build the platform.
Request a demo3.0For the technical review
Security, LGPD, capabilities and what Hummand does not do are published, with the label of each item's state, for the security team and legal. The technical sheet sums up security and LGPD in two pages.
Download the technical sheet (PDF)4.0The sheet to take along
This page on one A4 sheet, for the product team and for whoever decides.
Download the sheet (PDF)Verify a receipt
Paste the JSON and the public key. No account, nothing sent: it runs in your browser.
Open the verifier