galleon-defi-infralisted

# DeFi infrastructure Make the requested agent capable of its first task through maintained provider tools. Separate installed software, available credentials, authenticated access, live reads and transaction authority; success at one does not prove the next. ## Pick the needed plumbing - RPC and Alchemy: read [RPC and Alchemy](references/rpc-alchemy.md) to select a chain, verify node freshness and choose CLI or MCP transport. - Wallet ownership and Coinbase: read [Managed wallets](references/wallets.md) before selecting custody, an isolated portfolio or an agent wallet. Existing exchange access is not an onchain signer. - Paid APIs, sponsorship and scoped permissions: read [Payments and authority](references/payments.md). An HTTP 402 is a price offer, not approval to pay. - Hermes installation and tool exposure: read [Hermes wiring](references/hermes.md). Keep Hermes as the runtime; integrate its native skills, profiles and MCP configuration instead of maintaining a fork. - CLI prompts, authentication failures or stalled sessions: use [CLI recovery](references/cli-recovery.md) to distinguish missing access from transport and uncertain writes. - Broken connectivity: use [Readiness diagnostics](references/readiness.md) for a bounded, read-only probe and a precise readiness report. Start with the user's selected chain and task. Read-only research needs RPC or indexed data, not a newly created wallet. Reuse an existing compatible provider connection when its account and perm