Create an agent wallet in the Skyfire developer portal; complete KYA onboarding by linking the wallet to a verified principal entity (individual or business) as required by Skyfire's compliance framework
Fund the wallet by transferring USDC from an external wallet or via Skyfire's on-ramp to the agent's Skyfire wallet address; confirm the deposit is reflected in the wallet balance via the Skyfire wallet API before proceeding
Configure spending controls on the wallet: set a per-transaction maximum, a daily cumulative limit, an allowed merchant or service category allowlist, and an expiry date for the spending authority
Integrate the Skyfire wallet SDK into your agent runtime so the agent can query available balance, initiate payments to KYAPay-enabled services, and receive payment confirmation receipts programmatically
Set up withdrawal policies: configure the minimum balance threshold that triggers an alert to the principal and define whether surplus funds above a high-water mark are automatically swept back to the principal's main wallet
Known gotchas
Skyfire wallets are custodial; the principal does not hold private keys — Skyfire manages custody on their behalf, which means wallet recovery and fund access depend on Skyfire's platform availability and their KYA/KYC verification of the principal
USDC transfers to Skyfire wallets must originate from compatible chains; confirm the chain your USDC is held on is supported by Skyfire's deposit flow before initiating the transfer, as cross-chain bridging is not handled automatically
Spending control changes take effect for new transactions but do not retroactively cancel pending or in-flight payments; if you need to immediately stop an agent from spending, use the wallet suspension endpoint rather than relying on limit changes
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp