Product · Agents
Wallets for machines.
Agents need to pay for compute, data, and APIs without revealing who they belong to or what they bought. Hvisk Agents provide isolated keypairs, programmable policies, and x402-native payments out of the box.
An agent in Hvisk is a programmable subwallet with its own keypair, spending policy, and audit log. Owners set per-transaction and daily limits in USDC equivalent. The agent transacts independently but stays bounded by your policy on-chain.
x402 by default.
When an agent hits an API that returns HTTP 402 Payment Required, it parses the payment header, decides whether the invoice is within policy, generates a proof, and settles. The response is then re-issued with the original request body intact.
HTTP/1.1 402 Payment Required
X-Payment-Required: true
X-Payment-ID: pay_5b3a8e7c2d4f1
Content-Type: application/json
{
"amount": 0.05,
"token": "USDC",
"recipient": "9xQe…",
"privacy": "full",
"expiresAt": 1730000000000
}Why it's private.
Public ledgers expose every machine-to-machine payment. Without privacy, competitors can profile an agent's spend, infer its workload, and game its routing. Hvisk Agents settle through the same privacy pool used for human payments, so the metadata leak is zero.