# Onboard an Agent Give an agent its own wallet and a budget it can't exceed. Each agent gets an isolated policy — spend limits and an allowlist enforced on every payment. ## How it works 1. Create an agent — it gets a managed signing key, no seed phrase to hand out. 2. Authorize it on your vault with its own policy: a daily limit and an allowlist. 3. The agent can pay, up to its budget. Tighten or revoke any time. ## Create the agent ```typescript import { PlatformClient } from "@newton-xyz/isaac"; const platform = new PlatformClient({ baseUrl: process.env.PLATFORM_API_URL!, apiKey: process.env.OPERATOR_API_KEY!, }); const agent = await platform.createAgent("research-bot"); // { address, name, hdIndex, sessionExpiresAt } ``` The key is managed for you — it signs inside a secure enclave, so there's no private key sitting in your app. ## Authorize it Authorizing gives the agent its own on-chain policy module — its spend limits and allowlist — installed on your vault. The fastest path is the dashboard: open your vault, pick the agent, set a daily limit and allowed recipients, and confirm. It deploys and installs the module and registers the policy in one guided step. To script it, the SDK's `ModularAdmin` deploys and installs the agent's module, then `PlatformClient.setupPolicy` registers the policy and seals its data on that installed module — the same flow the dashboard runs. Reach for it when you're automating fleet setup. ## Set the budget The daily limit and recipient allowlist are the agent's budget. See [Give an Agent a Budget](/guides/agent-budget) for the per-token limits, the allowlist, and per-vendor caps. ## Next * **[Give an Agent a Budget](/guides/agent-budget)** — daily limits, allowlists, per-vendor caps. * **[Pay for an API](/guides/pay-for-an-api)** — what the agent does once it's authorized.