Skip to content
EN

← Return to Guides

Developer agent hubopenclawmcp

FarmDash Agent Hub Complete Manual: Skills, SDK, MCP, and Execution Authority

Integrate FarmDash skills, REST/OpenAPI, clients, and MCP with accurate installation, pricing, current execution readiness, and zero-custody boundaries.

By TitanidesLeto · Published 2026-05-13 · Updated 2026-10-07

TLDR: Start with read-only research and the least-authoritative integration that solves the task. Read the generated capability table below and live status for current USER_SIGNED and BOUNDED_AUTONOMOUS readiness. Payment, session access, venue delegation, and an owner-signed policy are different proofs. FarmDash never receives customer private keys or seed phrases. Public REST/OpenAPI and FarmDash-hosted skills are the preferred current contracts; verify public-mirror and package publication independently.

What evidence does this manual describe?

Current readiness rows derive from the canonical capability source, not the earlier editorial snapshot. Dated distribution, commercial and fee observations below were collected on October 5, 2026 against source 7cc1ade96cbe64398da51587443dc5bcd0d1c0b4; they are historical observations, not verification of this revision's deployed SHA. The editorial update date describes this guide, not registry freshness or new transaction qualification.

Live status and authority outrank prose. An operational label is not live transaction proof: this revision's observations did not run funded swaps, orders, payments, sessions, ACP jobs, or webhook delivery. Session behavior below is source-contract evidence, not exercised production mutations. Recheck status before wallet-affecting work.

Discovery is not permission, preparation is not submission, venue acknowledgement is not a fill, and a transaction hash is not settlement.

What is the Agent Hub?

The Agent Hub connects research, wallet grounding, workflow plans, risk checks, commercial access, local signing, and receipt-oriented control APIs.

Surface What it supplies What it does not establish
FarmDash-hosted OpenClaw skills Separately versioned SKILL.md contracts and supporting files Marketplace publication/review, complete bundle parity, or wallet authority
REST / OpenAPI Language-independent HTTPS schemas Every listed operation being enabled
MCP Local stdio adapter and capability manifest Current public-mirror parity, npm publication, or unattended execution
Public read-only client Dependency-free sourced reports Agent Kit signing, MCP transport, or execution
Source Agent Kit Typed integration and customer-local signing helpers in an authorized checkout Published npm SDK or available public clone target

Use the main OpenAPI for clients. Futures and swap specialist contracts overlap it; do not add their totals to the main inventory. Respect servers and operation overrides rather than mechanically prepending /api to every path. The MCP manifest is discovery, not an HTTP MCP endpoint or signing grant.

Which skill should I install first?

Start with research and wallet context. Add execution only for an explicit user task. Versions below are derived from canonical frontmatter at build time, not copied from ClawHub releases. Tool lists are highlights, not separate inventories to sum; shared tools may appear in several skills.

Skill / canonical slug Canonical version Purpose and principal MCP tools Authority boundary
Trail Intelligence / farmdash-trail-intelligence 3.1.3 get_trail_heat, get_protocol_metadata, get_protocol_risk_factors, audit_sybil_risk, simulate_points, get_historical_trailheat, find_capital_route Research; no wallet execution
Wagon Steward / farmdash-wagon-steward 0.7.2 get_wallet_balances, get_portfolio_summary, get_position_health, get_idle_capital, get_token_prices Wallet context; not settlement or realized P&L proof
Trail Marshal / farmdash-trail-marshal 1.1.2 list_workflows, plan_workflow, run_workflow, get_workflow_status Plans/run records; cannot bypass owning route gates
Signal Architect / farmdash-signal-architect 4.2.1 get_swap_quote, simulate_swap_execution, execute_swap, confirm_swap, resolve_defi_intent, optimize_portfolio Supported spot preparation/verification; generic execution disabled
Futures Strategist / farmdash-futures-strategist 3.4.0 scan_funding_rates, scan_market_conditions, get_futures_account, analyze_futures_strategy, calculate_position_size, execute_perp_order, cancel_perp_order Exact local Hyperliquid signatures and mode-specific authority
Camp Guard / farmdash-camp-guard 1.1.2 audit_allowance_risk, simulate_transaction_risk, run_risk_sentinel Risk evidence; a pass does not sign or grant authority
Supply Master / farmdash-supply-master 1.1.2 compare_yields Yield research, not automatic deposits or promised returns
Hedge Warden / farmdash-hedge-warden 1.1.2 recommend_delta_hedge Handoff only; fresh futures research/authority required
Ledger Keeper / farmdash-ledger-keeper 1.1.2 ledger_realized_pnl, ledger_tax_export Recorded activity; not tax/accounting advice
Autonomous Operator / farmdash-autonomous-operator 2.1.2 create_session, session_heartbeat, get_farming_context, patch_farming_context, get_event_stream_snapshot, verify_delegation, configure_autopilot, autopilot_cycle Session/control context; not a wallet-signing grant

Fetch each manual at https://www.farmdash.one/openclaw-skills/<canonical-slug>/SKILL.md, using the exact slug above. Frameworks can load Markdown directly. Copy required supporting SKILL.json, OpenAPI, and references as well; a manual alone is not necessarily a complete bundle. Read full tool schemas for required parameters.

FarmDash files versus ClawHub publication

October 5 observations found 6/10 exact canonical ClawHub slugs, not universal publication. Camp Guard, Hedge Warden, Ledger Keeper, and Supply Master returned Skill not found. Only Signal Architect and Trail Intelligence retrieved published bundles matched pinned source semantically. Autonomous Operator, Futures Strategist, Trail Marshal, and Wagon Steward listings differed. Listing release versions and embedded manual versions are independent trains: equal versions or publisher metadata do not prove current content or a verified upload source SHA.

All FarmDash-hosted manuals matched pinned source ignoring line endings, but complete production bundle parity was 8/10: Signal Architect and Trail Intelligence had supporting SKILL.json differences. These are dated observations, not verification of a later build or external update. Do not call every skill ClawScan-reviewed, current on ClawHub, or fully mirror-identical.

USER_SIGNED versus BOUNDED_AUTONOMOUS

Capability Canonical status
spot.USER_SIGNED operational
spot.BOUNDED_AUTONOMOUS operational
futures.USER_SIGNED operational
futures.BOUNDED_AUTONOMOUS operational
solana.USER_SIGNED operational
solana.BOUNDED_AUTONOMOUS operational
ERC4337_SERVER_SUBMISSION preparation_only
GENERIC_SERVER_INTENT_EXECUTION preparation_only
MEE preparation_only
ACP deployment_prerequisite

Read canonical readiness and live deployment/request gates before execution. These rows are conditional capability contracts, not funded-production proof. USER_SIGNED requires fresh human authorization. Bounded execution requires a separate revocable domain policy and customer-agent-local signature per action, plus exact identity, scope, validity, simulation/research, risk/budget and replay checks. Commercial access cannot supply signing authority; FarmDash never receives the customer key.

In USER_SIGNED spot, the customer wallet signs and broadcasts the exact prepared transaction. USER_SIGNED futures requires fresh human authorization per order or cancel; the customer signs locally and FarmDash verifies and forwards the exact signed Hyperliquid action. Bounded futures requires a separate owner-signed futures policy, valid API-wallet venue authority and local signature per action.

USER_SIGNED is the default supported one-off mode. Fresh human authorization and the exact local signature are mandatory; an earlier plan approval is not approval of a later order/cancel.

The bounded model may omit a fresh human prompt only inside an explicit valid owner grant and where runtime capability permits it. It does not omit local signatures, authoritative simulation/research, session/account binding, scope/allowlists, validity, risk/budget, builder approval, or replay checks. A paid tier, valid grant, discovered tool, healthy session, or passing local test cannot override a deployment or request gate. Spot authority does not transfer to futures or vice versa.

Commercial entitlement, generic session policy, venue API-wallet delegation, and owner-signed bounded policy are separate. An active generic session or verified venue delegation alone is not bounded-autonomous authority. Query authority for the exact domain and identity before presenting a grant as usable.

Supported spot: firm quote to verified receipt

Use the compatibility EVM lifecycle, not a research estimate as executable intent:

  1. Discover: inspect provider/chain readiness. GET /api/agents/quote provides a provider-neutral research estimate, not a firm wallet-bound execution entitlement.

  2. Acquire a firm intent: use POST /api/v1/agent/quote-intent with current required fields, wallet identity, and commercial capacity. MCP get_swap_quote implements its preview/firm distinction according to the supplied schema.

  3. Simulate: simulate_swap_execution / POST /api/v1/simulate must produce an authoritative successful, unexpired result for the exact intent.

  4. Authorize: obtain fresh user approval and sign the exact compatibility EIP-191 request locally:

    v1:FARMDASH_SWAP:{fromChainId}:{toChainId}:{fromToken}:{toToken}:{fromAmount}:{agentAddress}:{toAddress}:{nonce}

    Follow contract address normalization and milliseconds nonce rules; the compatibility nonce window is 60 seconds. Do not reconstruct an expired request from a cached summary.

  5. Prepare: execute_swap / POST /api/agents/swap verifies authorization/simulation and returns the exact payload. FarmDash does not sign or broadcast this spot transaction.

  6. Submit locally: the customer wallet reviews, signs, and broadcasts. Returned calldata is not a transaction hash or fill.

  7. Confirm: confirm_swap / POST /api/agents/confirm verifies canonical-chain receipts and committed fee fields. Cross-chain routes need destination evidence, not just source submission.

  8. Reconcile: compare actual balances, costs, and receipts. Expected quote output is not a realized result.

Firm quote-intent admission establishes commercial capacity. Its bound simulation/preparation continuation is not re-billed; this is not a bypass for unrelated routes or another firm quote. See the Signal Architect reference and Eliza integration for detailed payloads.

Providers and chains

LI.FI and Relay were enabled, configured, and firm_quote_ready. 0x is operator-paused, disabled, and excluded from primary/fallback selection. OKX is quarantined. x402 is a payment rail, not a swap provider. Provider labels are not funded-trade proofs.

Enabled EVM compatibility chains: Ethereum (1), Optimism (10), Polygon (137), Base (8453), Arbitrum (42161), and Linea (59144). Discovery coverage is broader than execution coverage. Private submission is unsupported.

Solana uses its separate native lifecycle: Jupiter firm quotes, authoritative RPC simulation, exact transaction/message and required-signer validation, customer-local Ed25519 signing, submission and finality/reconciliation. Bounded policy cannot manufacture on-chain signer authority. Read the canonical Solana rows and live request gates; firm_quote_ready=true alone is not execution or funded-transaction proof.

Supported futures: research, exact local action, venue result

Use Futures Strategist for Hyperliquid; do not silently add spot swaps or cross-sell farming. If the user declines execution, remain an analysis assistant.

  • Funding/market tools have Scout reads/previews. Scout also has signed order/cancel capacity within quota; execution is not exclusive to Syndicate.
  • Account, strategy, and sizing require Pioneer+ or eligible route-specific x402.
  • New-risk research evidence is valid for 60 seconds, not five minutes. Re-run stale research; no_trade is a valid stop.
  • Local Hyperliquid EIP-712 signatures bind the exact venue action, nonce, account/vault routing, and applicable builder terms. Preserve agentAddress, accountAddress, sessionId, mode/grant fields, and their binding rules. Independently establish account ownership and valid API-wallet venue authority.
  • FarmDash verifies signature, authority, research, and risk gates, then forwards the already signed action. It never receives the customer's Hyperliquid signing key.
  • Venue acknowledgement may be accepted/resting, rejected, or filled. Reconcile order/account state; HTTP 200 is not a fill or cancellation finality.

A genuinely risk-reducing action may receive a new-risk research/capacity exemption after authoritative classification. reduceOnly never bypasses signature, ownership, venue authority, scope, replay, builder, or other mandatory checks. Preserve protective-order execution-limit price, trigger threshold, and market/limit-trigger terms separately in the exact signed action.

Bounded futures preparation requires a dedicated API wallet and separate owner-signed futures policy. Durable signer enrollment remains fenced after expiry/revocation: stripping executionMode, grant, or session fields is not fresh human consent or a safe bypass. Never blindly resubmit or release durable budget holds on ambiguous timeout alone. Policy budgets are conservative admission controls, not guaranteed realized-loss ceilings or promises of profit.

Sessions, control states, and emergency action

Production advertises Pioneer+ sessions/controls. An October 5, 2026 anonymous session GET returned HTTP 402, policy session_control, 2.49 USDC on Base under the prior schedule; the current repository default is 0.02 USDC. This proves admission behavior, not session mutation success.

The following are source-contract semantics:

Control / state Meaning
Create Wallet-bound EIP-712 approval (EIP-191 compatibility), fresh single-use nonce; token returned once
Token Random capability token; only its session-bound hash is retained server-side; keep it out of URLs, visible logs, and model output
Heartbeat Expiry is 24 hours from the last heartbeat; does not renew owner policy or venue delegation
active Permitted coordination, subject to every route gate
paused Automated cycles stop; existing venue positions remain in place
Resume paused → active, or idempotent while active; cannot revive terminal states
halted Terminal; kill awaits grant revocation before halt and records audit state
expired Terminal; close awaits grant revocation, expires session, and revokes token
Emergency freeze Caller authentication is target-bound; public callers do not gain owner-wide/cross-session control
Context patch Session-scoped database-authoritative state with optimistic revision checks; context text is not authority

Use session/context/event/autopilot tools within their authenticated contracts. Controls and recommendations do not enable unattended execution. Verify exact state after revocation; revoking a FarmDash policy does not necessarily revoke venue delegation. Pause/kill does not promise positions closed or all orders cancelled.

Gated capabilities and unresolved prerequisites

Capability Observed state Boundary / prerequisites
Virtuals ACP V2 deployment_prerequisites_required; mode=disabled; preparation_ready=false; paid_workflow_ready=false All readiness checks false; not even production-ready preparation
MEE Creation/economics preparation preview; submission/settlement disabled, mee_coordinator_unconfigured Production coordinator, authoritative source/destination receipts, deployment integration evidence
ERC4337_SERVER_SUBMISSION preparation_only Grants/cycles do not provide server UserOperation construction, signing, bundler submission, or settlement
Generic FarmDashIntent v2 Durable control-plane preparation; execution disabled, execution_verifier_unconfigured Trusted adapter, server verifier, verified receipt ingestion; caller self-attestation is not settlement
Webhooks deployment_prerequisites_required Migration 028, WEBHOOK_ENCRYPTION_KEY, CRON_SECRET, scheduled durable worker; Syndicate alone cannot enable delivery
CDP/MPC wallets deployment_prerequisites_required Wallet-bound tenant key, allowed destinations, CDP credentials, tenant ledger, production integration evidence; not a server-wallet quickstart

ACP integration design, not live paid workflow

Once readiness is established, the V2 sequence is provider selection → non-spendable tender → exact customer EIP-712 approval → customer-local job creation → binding → cap-aware reservation → customer-local funding → recorded hashes → canonical funding finality → specialist evaluation → evaluator settlement receipts.

Preparation uses exact selectionId; authorization uses providerSelectionId. These are distinct request fields, not interchangeable aliases. Follow current schemas. Approval binds task/disclosure/evidence/provider-plan/economic-policy/evaluator/cap/nonce/expiry commitments. The customer-owned registered ACP client creates/funds jobs locally. FarmDash is a separately registered job-bound evaluator, not a customer wallet signer. Do not transmit keys or task plaintext to FarmDash.

Preparation needs release_mode, v2_migrations, evaluator address/key version, provider-selection store/policy/expiry, and dependency parity. Paid workflow also needs evaluator wallet/signer, trusted Base RPC, provider registry, stake/identity verification, funding ledger/RPC/decoder/confirmations/reconciliation, finality workers, and authenticated scheduler. The current gate overrides this architectural sequence. See the ACP V2 lifecycle.

Pricing, quota, payments, and routing fees

Tier Price Published quota Interpretation
Scout Free 30 requests / 24h per IP Eligible previews/reads and signed-call capacity; not all premium reads
Pioneer $39.99/month USDC 1,500/day Research/wallet capacity; sessions still separately authenticated
Syndicate $199/month USDC 50,000/day High-volume/teams capacity; does not enable blocked execution or undeployed webhooks

Scout access is route-specific. The October 5, 2026 GET /api/v1/agent/protocols response was a truncated/masked catalog preview: tier=scout, status=limited, count=3, masked_for_tier=true, and data_quality=catalog_preview, with encrypted numerical fields. Its advertised total catalog size does not mean those records or live quantitative metrics are available anonymously. Eligible free routes retain their quota; qualifying full access follows the route's policy. Preserve preview/masking labels downstream.

Omit Authorization for Scout; do not send fake fd_scout_free or placeholder tokens. Paid FARMDASH_API_KEY grants commercial access only. Protect/rotate it; stolen API/session tokens remain credential incidents, not harmless because they are not wallet keys.

GET /api/v1/agent/onboard can issue X-FarmDash-Scout-Grant: 4 cheap-discovery calls, 1,800-second TTL, for Trail Heat, catalog, chain breakdown, and provider-neutral estimates. It grants neither premium research nor firm-intent/execution authority. Optional setup is not required to install a skill or begin eligible research.

An eligible route's live 402 response is authoritative for amount, asset, network, destination, policy, and proof format. PAYMENT-REQUIRED, PAYMENT-SIGNATURE, PAYMENT-RESPONSE, and legacy X-Payment-Proof are route-specific payment mechanisms. Do not repeatedly retry unpaid requests or assume a default price buys a premium route. Payment grants eligible capacity, not a subscription, signature, venue delegation, owner policy, or risk clearance.

Informational payment bootstrap advertises native Base ETH direct payment, x402 USDC, and integer prepaid credit_micro. At observation nativeEthPricingAvailable=false; purchase/redemption was not tested. Wallet-signed single-firm-quote bootstrap is exact quote capacity, not autonomous authority, general credit minting, or premium-route access.

The fee schedule is labeled generated October 1, 2026; runtime overrides may differ. Combined spot routing targets: 50 bps below $10K, 40 at $10K+, 35 at $100K+, 20 at $1M+. LI.FI's 25 bps is deducted, not stacked. Gas, slippage, impact, bridge/liquidity, and token mechanics are excluded. Generic-intent 50 bps pricing does not enable disabled execution. The observed manifest advertises 1 bps futures builder fee; verify current venue terms and exact signed builder action rather than inferring charged amounts. No order-fee transaction proof was run.

Installation and framework integration

REST / OpenAPI: preferred current integration

Generate a client from public OpenAPI. Eliza Actions, LangChain tools, OpenAI/Anthropic tools, or custom backends can wrap the operations. These are integration patterns, not separately published native plugins or fixed function inventories. Match current schemas/authorization.

curl https://www.farmdash.one/api/v1/agent/status
curl https://www.farmdash.one/api/v1/agent/onboard

These are read-only starting points, not paid entitlement or authority registration.

Public read-only client: available tarball

The verified archive is @farmdash/client@1.0.0: dependency-free, read-only, Node.js 20+, source/license included, matching published checksum.

npm install https://www.farmdash.one/downloads/farmdash-client-1.0.0.tgz
npx farmdash-report

Checksum: https://www.farmdash.one/downloads/farmdash-client-1.0.0.sha256. Retrieval/checksum evidence does not claim installation was executed. This is not Agent Kit or a stdio server.

Agent Kit: authorized source only

@farmdash/agent-kit@0.1.0 exists in canonical source. Public npm metadata returned 404; the documented historical Parmasanandgarlic/farmdashbeta clone target also returned 404 unauthenticated. Whether private, moved, or deleted is not established. Do not offer it as a working public install. Developers with an authorized checkout can use agent-kit/ build/typecheck instructions; others should use REST/OpenAPI or the read-only client.

MCP: available but older public source mirror

Canonical registrations/schema and production discovery agree on the current catalog; actual live stdio tools/list was not run. The public Parmasanandgarlic/farmdash-openclaw-skills mirror, observed HEAD 8f12d77e885b088817fce7e8d3462eb3153dbea7, is an older distribution pinned upstream to f5a5614875183ab893ed77eecd1f6eaffe571ca9. This is dated distribution evidence. It is behind the canonical catalog, missing:

  • confirm_autonomous_swap
  • get_execution_authority
  • get_payments_bootstrap
  • prepare_autonomous_swap
  • register_execution_delegation
  • release_autonomous_reservation
  • request_execution_delegation
  • revoke_execution_authority

Public npm metadata for @farmdash/mcp-server returned 404; official MCP Registry exact/search lookups found no matching publication. Package metadata/prepared releases are not publication proof. This guide neither publishes nor syncs the mirror.

For the older mirror, with Node/npm and a local build environment:

git clone https://github.com/Parmasanandgarlic/farmdash-openclaw-skills.git
cd farmdash-openclaw-skills/mcp-server
npm ci
npm run build

This is the advertised build path, not verified current-catalog parity. Inspect installed tools/list; use current HTTP routes for missing capabilities. Do not offer npm-registry installation without successful independent readback.

Claude Desktop and Cline stdio configuration:

{
  "mcpServers": {
    "farmdash": {
      "command": "node",
      "args": ["/absolute/path/to/farmdash-openclaw-skills/mcp-server/dist/index.js"]
    }
  }
}

Cursor uses the same command and absolute args in its MCP configuration. Windows paths may use C:/Users/you/farmdash-openclaw-skills/mcp-server/dist/index.js. Restart after config changes. Leave FARMDASH_API_KEY unset for Scout; use secure client environment configuration for real paid tokens. FARMDASH_BASE_URL defaults to https://www.farmdash.one/api. Never put wallet keys or seed phrases in MCP configuration.

How do the skills compose safely?

Sense → Decide → Guard → Present → Authorize → Prepare/Submit → Verify/Reconcile is a conceptual workflow, not a guarantee every recipe executes today.

  • Research-only rotation: compare protocol and wallet evidence, inspect risk, present a plan, and stop without signing. Catalog discovery heuristics are not live quantitative Trail Heat. Retain observed/derived/editorial/stale/unavailable labels and masked Scout fields; missing upstream values are unavailable/null, not fabricated zero.
  • Delta-neutral planning: Trail Marshal describes handoffs; Supply Master/Hedge Warden provide research. Each spot/perp leg retains independent authority/readiness. A swap is not automatically a lending/HLP deposit; wallet health cannot certify both legs settled.
  • Funding capture: periodically re-evaluate funding/account conditions. Each USER_SIGNED order/cancel requires fresh human authorization and exact local signature. A session is not a scheduler guarantee or standing trading permission.
  • Idle-capital planning: inspect balances, compare sustainable yield, check approvals/route risk, and show costs. Execute only specifically supported authorized legs. Do not invent research aliases or generic deposit execution tools.

Use actual tool names/schemas. Research outputs do not guarantee points, dollar rewards, profits, or safety. Stop on user refusal, missing prerequisites, expired evidence, or ambiguous submission. Reconcile before retrying.

Zero custody does not mean zero responsibility

Customer private keys, seed phrases, wallet exports, and signer callbacks never belong in a FarmDash request or model prompt. Wallet/agent runtimes sign locally. FarmDash may receive public identities, exact signatures, API/session capability tokens, and transaction references under their distinct contracts.

Spot returns payloads for customer broadcast. Futures verifies/forwards signed venue actions. A separately gated ACP evaluator has a restricted submission role. Do not claim FarmDash never submits anything or that every state change uses one signing scheme.

Keep credentials out of URLs/logs, use dedicated bounded signers, preserve exact signed limits/expiry, and provide an emergency stop independent of the model. Recheck status/authority on failure instead of converting missing evidence into permission.

Related guides and machine contracts

Continue researching