Integrations
Arcanum sits at one point in your stack: the moment an agent pays. Whatever framework the
agent runs on, replace its direct USDC transfer with arc.executeUSDC and the wallet’s
policy applies.
Circle Wallets as the agent’s key
arcanum-sdk/circle (Node.js only) uses a Circle developer-controlled wallet as the agent
signer, so the private key never sits on the agent’s server. Circle signs each transaction,
and the SDK checks every signature against the request before sending it.
import { circleWalletAccount } from "arcanum-sdk/circle"
const agentSigner = circleWalletAccount({
apiKey: process.env.CIRCLE_API_KEY as string,
entitySecret: process.env.CIRCLE_ENTITY_SECRET as string,
walletId: process.env.CIRCLE_WALLET_ID as string,
address: process.env.CIRCLE_WALLET_ADDRESS as `0x${string}`,
})Then add that address as a signer on the wallet with addSigner, like any other agent key.
Safe as the wallet owner
Teams that keep their treasury in a Safe can make the Safe the wallet’s owner. Every rule change then needs the Safe’s signers, and council members can be the wallet’s approvers.
await ownerClient.writeContract({
address: guardedWallet,
abi: GuardedWalletAbi,
functionName: "configureEscalation",
args: [councilMembers, 2, 3600],
})Agent frameworks
The pattern is the same for ElizaOS, Coinbase AgentKit, Virtuals and custom agents: expose a payment tool that calls the SDK, and keep the agent’s own wallet client for everything else.
const payTool = async (to: `0x${string}`, amount: bigint, reason: string) => {
const result = await arc.executeUSDC({ to, amount, reason })
return result.verdict // the agent can read ALLOW, ESCALATE, DENY or FREEZE
}Turn off automatic retries for the payment tool. If the SDK throws
TransactionRecoveryError, the payment may already have gone through. Use reconcileUSDC
with the saved transaction hash instead of paying again. See the
TypeScript SDK.