Question 1

What is FarmDash Agent Hub?

Accepted Answer

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.

Question 2

Is FarmDash custodial?

Accepted Answer

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.

Question 3

How do I integrate an AI agent with FarmDash?

Accepted Answer

Start with /api/v1/agent/status for live readiness, then use the unified OpenAPI contract, llms.txt, or the agent report. The public source MCP server at github.com/Parmasanandgarlic/farmdash-openclaw-skills mirrors canonical parity and is the supported source install path. Keep API access, wallet authority, payment, execution, and receipt verification separate.

Question 4

Does bounded authority enable unattended trading now?

Accepted Answer

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.

Question 5

What is the base URL for the FarmDash API?

Accepted Answer

The canonical origin is https://www.farmdash.one. Machine-readable discovery lives at /apis.json, the OpenAPI contract at /agents/openapi.yaml, the MCP capability manifest at /.well-known/mcp.json, and live readiness at /api/v1/agent/status. Route availability is governed by the live status contract rather than by static documentation.

Question 6

What are FarmDash API rate limits?

Accepted Answer

Scout provides free entry-level access at 30 requests per 24 hours per IP on eligible public surfaces. Pioneer adds 1,500 requests per day and Syndicate adds 50,000 requests per day plus higher-volume and team capabilities where deployment status supports them. Scout is keyless; paid tiers use bearer-token authentication. The live pricing and status contracts are authoritative.

Question 7

Does FarmDash have a Python SDK?

Accepted Answer

FarmDash publishes a public OpenAPI contract at /agents/openapi.yaml plus source client and SDK code, so a typed client can be generated for Python, TypeScript, JavaScript, or Go from the same schema. The @farmdash/agent-kit npm package must not be described as registry-installable until npm readback confirms publication. The source-installable MCP server is distributed separately from any npm package.

Question 8

How does authentication work for FarmDash API access?

Accepted Answer

Scout access is keyless and rate-limited per IP. Paid Pioneer and Syndicate tiers authenticate with a bearer token. Authentication grants API access only: it does not create wallet authority, delegation, or execution rights. Wallet-signed actions remain separate and require the user's own key.

Question 9

How do I get started with the FarmDash MCP server?

Accepted Answer

The canonical MCP capability manifest is at /.well-known/mcp.json and describes the current registered inventory, readiness and authority metadata. The supported install path is the public source checkout of github.com/Parmasanandgarlic/farmdash-openclaw-skills, which mirrors canonical parity and uses the stdio transport. Verify the live manifest before integrating: npm publication and ClawHub publication are separate distribution states.

Question 10

Where are the FarmDash OpenClaw skills published?

Accepted Answer

The ten canonical FarmDash OpenClaw skills are authored under the canonical repository and distributed as a public source checkout. Six are published on ClawHub and four are prepared for manual upload. The skills are semantic discovery surfaces for agents; publishing a skill does not grant execution authority or imply runtime readiness.

Question 11

How does FarmDash x402 payment work for agents?

Accepted Answer

x402 is FarmDash's per-operation API payment and access rail. On eligible exhausted Scout routes the 402 response publishes the exact amount, asset, network, destination, reset time and retry policy. If it returns STOP_RETRYING, do not repeat the same unpaid request. Valid route-bound payment proof can unlock the eligible operation once; it does not create a subscription, wallet signature, swap route, or settlement guarantee.

Question 12

Can FarmDash execute trades autonomously?

Accepted Answer

Not by default. USER_SIGNED is the default authority model: spot and futures require fresh human authorization. Bounded autonomous authority requires explicit policy and cryptographic prerequisites, and remains gated by /execution-truth.json and /api/v1/agent/status. Commercial payment, session authentication, profile visibility, and Scout, Pioneer, or Syndicate access are not signing or delegation authority. Simulation is not execution, preparation is not submission, and submission or a transaction hash is not settlement.

Question 13

Which chains does the FarmDash API support?

Accepted Answer

Compatibility EVM routing is capability-gated and currently uses LI.FI and Relay, with 0x operator-paused. The published contract includes Ethereum, Optimism, Polygon, Base, Arbitrum and Linea for the compatibility path when runtime status marks the route enabled. Solana and Hyperliquid/HyperEVM research surfaces are covered for discovery, but discovery coverage does not imply execution parity. Verify current chain support against the live status contract.

Question 14

Is there a FarmDash quickstart for agents?

Accepted Answer

Begin with /api/v1/agent/status to confirm live readiness, then read /apis.json for the endpoint index, /agents/openapi.yaml for the typed contract, and llms.txt for the agent-oriented overview. For tool-style integration, fetch /.well-known/mcp.json. Treat discovery metadata as informational only: it never grants execution authority.

Question 15

How does FarmDash simulate a swap before signing?

Accepted Answer

FarmDash can prepare and simulate swap routes without moving funds. Quotes return route plans or unsigned calldata for review; the customer's wallet signs and submits the final transaction. Simulation results are estimates and do not guarantee execution, settlement, or a specific price. The live capability manifest and status contract determine whether a route is read-only, preparation-only, or execution-capable.

Question 16

What is the difference between API access and wallet authority?

Accepted Answer

API access is commercial or free entitlement to call FarmDash surfaces and is governed by Scout, Pioneer, or Syndicate tiers. Wallet authority is the user's own signing power over their funds and is never transferred to FarmDash. Session authentication, profile visibility, and paid access each describe a different boundary; none of them grants signing, delegation, or execution authority. FarmDash never receives private keys or seed phrases.

Build Zero-Custody DeFi Agents

Direct Answer