FarmDash Agent Hub

Build Zero-Custody DeFi Agents

Build DeFi agents with Trail Heat research, wallet context, zero-custody transaction-control workflows, OpenAPI, MCP capability metadata, x402 access, and live readiness gates.

Direct Answer

FarmDash Agent Hub gives DeFi agents structured Trail Heat intelligence, zero-custody transaction-control workflows, OpenAPI specs, MCP discovery files, x402 API access, and live readiness gates. Users retain signing authority; discovery and source installation do not establish runtime readiness.

Build Zero-Custody DeFi Agents

FarmDash Agent Hub gives DeFi agents structured Trail Heat intelligence, zero-custody transaction-control workflows, OpenAPI specs, MCP discovery files, x402 API access, and live readiness gates. Users retain signing authority; discovery and source installation do not establish runtime readiness.

• Agent-ready Trail Heat and protocol intelligence
• Zero-custody swap quote and execution APIs
• Public OpenAPI, APIs.json, MCP, and llms.txt discovery surfaces
• Customer-controlled signing for wallet-affecting actions Open Interactive Hub

FarmDash Agent FAQ

What is FarmDash Agent Hub?

FarmDash Agent Hub is the zero-custody intelligence and control layer for DeFi agents. It combines Trail Heat research, wallet context, Signal Architect workflows, x402 access, Hyperliquid tooling, OpenAPI, and MCP capability metadata. Canonical discovery, public source distribution, npm publication, and runtime execution readiness are separate states.

Is FarmDash custodial?

FarmDash does not take custody of wallet funds or private keys. Quote and compatibility routes return plans or calldata for customer-controlled signing; advanced venue-specific operations remain separately gated and must be confirmed against the live status contract.

How do I integrate an AI agent with FarmDash?

Start with /api/v1/agent/status for live readiness, then use the unified OpenAPI contract, llms.txt, or the agent report. At the October 5, 2026 observation, MCP npm returned 404 and the advertised public source mirror lagged canonical discovery by eight tools. Keep API access, wallet authority, payment, execution, and receipt verification separate.

Does bounded authority enable unattended trading now?

USER_SIGNED spot and futures require fresh human authorization. Read current BOUNDED_AUTONOMOUS readiness at /execution-truth.json and deployment/request gates at /api/v1/agent/status. A session token, paid access, owner policy, or venue delegation cannot override those gates. Where runtime capability permits bounded execution, the customer-controlled local agent signs each action within its revocable domain-specific policy; futures additionally requires venue authority and risk/budget/replay checks. FarmDash never receives the signing key.

Implementation Status

Live now

Trail Heat intelligence, protocol discovery, the APIs.json catalog, OpenAPI and MCP discovery files, OpenClaw skills, swap quotes, simulation requirements, user-signed execution payloads, x402 payment fallback, and API key tiering.

Preview now

Control Room UX, demo supervision rows, local pause/revoke state, and authenticated receipt loading when valid session credentials exist.

Backend-backed target

Authoritative pause/revoke controls, durable policy mutation, production operator receipts, and deeper Syndicate session tooling for teams and serious agents.

This page requires JavaScript for the full interactive experience. Return to homepage to get started.