Detail
What the agent actually receives
You do not hand the agent a credential. You grant it delegated authority — bounded by scope and time — that lets it request actions the H33 runtime evaluates against the current policy. The agent never sees your private keys.
What happens on every action
Every payment the agent executes carries a signed authority chain: authority_hash + policy_hash + evidence_hash + preconditions → decision_hash. This chain travels with the payment and is exportable to compliance systems. Later, any action is replayable from the receipt alone.
What happens if the agent is compromised
You revoke the delegation. The agent's future actions stop being valid, even if the agent still has network access. Existing receipts remain valid audit records; new signature attempts fail.
How this differs from IAM roles
AWS IAM or Okta service accounts give an agent a credential. Steal it, become the agent. H33 gives the agent authority-to-request; the credential itself never leaves the H33 runtime. Compromise cost is bounded by the delegation, not by the credential.