Quick Start
This guide gives you two entry paths into GOAT Network agent infrastructure:
- Manual installation when you want to add AgentKit to an existing agent, app, or runtime
- CLI scaffolding when you want a ready-to-run starter project
After that, you can configure the runtime, attach a wallet provider, and execute your first on-chain action.
The official AgentKit product page positions manual installation as the recommended path for existing agents and apps. Use the CLI when you want a generated starter project.
Prerequisites
- Node.js 18+ and pnpm (or npm)
- A GOAT Network RPC endpoint. Use mainnet by default at
https://rpc.goat.network; use testnet examples withhttps://rpc.testnet3.goat.network.
Choose Your Start Path
AgentKit bundles its core dependencies (ethers, viem, zod, ioredis) so you do not need to install them separately.
Recommended Path: Manual Setup
Use this path when your agent or app already exists and you need to add GOAT Network capabilities without replacing your runtime.
Create the ActionProvider and register actions
The ActionProvider is the central registry for all actions your agent can perform.
Configure the Policy Engine
The PolicyEngine gates every action execution based on network, risk level, and write permissions.
Create the ExecutionRuntime
The runtime wraps policy evaluation, input validation, retries, idempotency, timeout, and metrics into a single run() call.
Execute an action
Every action runs through the runtime with a context object and input parameters.
CLI Scaffolding Path
The published create-goat-agent CLI generates a ready-to-run starter project with the correct AgentKit structure.
It will prompt you for:
- Project name -- your agent project folder
- Preset --
minimal(wallet only),defi(wallet + bridge + bitcoin), orfull(all 13 plugins) - Network --
goat-testnetorgoat-mainnet
The CLI generates a complete project with package.json, tsconfig.json, .env.example, and a src/index.ts with all chosen plugins pre-registered.
If you choose the CLI path, use the generated project as your baseline and then continue with the runtime, wallet, and plugin setup above.
Full Minimal Example
Here is the complete working example that combines all the steps above:
Using a Real Wallet Provider
For production use, replace the Noop adapters with real wallet providers. AgentKit ships two implementations:
NoopWalletProvider throws an error if used in production (NODE_ENV=production). Always use EvmWalletProvider or ViemWalletProvider for real deployments.
Environment Variables
Create a .env file based on the example:
The latest AgentKit network config sets goat-testnet to chain ID 48816 and uses https://rpc.testnet3.goat.network as the default testnet RPC endpoint.
Export Tools for Your AI Framework
Once you have actions registered, export them as tools for your AI framework with a single call:
See the Frameworks guide for detailed integration instructions.
Next Steps
- Plugins Reference -- browse all 13 plugins and 95 actions
- Custom Tools -- create your own actions with
customActionProvider - x402 Payments -- accept and make payments
- Runtime Configuration -- policy engine, idempotency, metrics, and hooks
- Official AgentKit site -- latest public product overview
- AgentKit GitHub repository -- source code and package updates