Skip to content

Agent Skill · version 0.1.0

Download Fensory Funding-Rate Strategy Agent Skill

Inspect matching Hyperliquid spot and perpetual-futures markets, predicted funding, liquidity and account limits, then prepare two sequential equal-notional legs for separate review.

Download and review

Download the public file, review every instruction, then place it in the skills directory documented by the compatible client you use. Client-specific paths are omitted until each workflow is verified.

Download
curl -fsSL https://fensory.com/skills/ai-funding-rate-strategy/SKILL.md -o SKILL.md
Install in Hermes
hermes skills install https://fensory.com/skills/ai-funding-rate-strategy/SKILL.md --name fensory-funding-rate-strategy

What the skill instructs

  • Read the account and instrument before preparing an action.
  • Keep the proposal inside the user's ceiling and the account's per-order cap.
  • Show the exact symbol, side, order type and size before a write call. Include the limit price for a limit order, or the current quote and expected execution conditions for a market order, then ask for confirmation.
  • Report a prepared order, submitted order and fill as three different states.

SKILL.md

---
name: fensory-funding-rate-strategy
description: Inspect matching Hyperliquid spot and perpetual-futures markets, predicted funding, liquidity and account limits, then prepare two sequential equal-notional legs for separate review.
license: Proprietary
compatibility: Requires access to the Fensory MCP server and an eligible Fensory account. Fensory is not available to US persons.
metadata:
  author: Fensory AG
  version: "0.1.0"
  source: "https://fensory.com/skills/ai-funding-rate-strategy"
---

# Run a funding-rate strategy with an AI agent

## When to use

This guide is for an eligible non-US user who already understands spot and perpetual futures and wants an assistant to calculate, prepare and audit a small, market-neutral funding workflow under explicit account limits.

It is not a yield promise, a recommendation to collect funding, or an unattended arbitrage system. A funding rate can reverse, one leg can fail, the basis can widen and a margined short can be liquidated before the intended offset works.

## Operating rules

- Start with read tools and identify the signed-in account, market, venue and instrument before preparing an action.
- Treat the Fensory account state, open orders, positions and fills as authoritative when they differ from the conversation.
- Fensory enforces four controls on the account: a kill-switch, an access expiry, a market allow-list and a per-order cap. Client confirmation instructions are separate from those account controls.
- Never describe a perpetual future as a share or tokenized equity. State the instrument and its risks before discussing an order.
- Never substitute a different market, quote currency or instrument because the requested one is unavailable.
- Keep every proposed order within both the user's stated ceiling and the account's per-order cap.
- Do not place, cancel or replace an order until the exact symbol, side, order type and size have been shown. For a limit order, show the limit price. For a market order, show the current quote and expected execution conditions. The user must confirm that exact action.
- Stop when a required tool is unavailable, the account limit cannot be verified, the quote is stale or the instrument is ambiguous.

## Risk and scope

This file is operational guidance, not financial advice. Trading can lose the full amount committed. Perpetual futures use margin and can be liquidated. Spot assets can lose value. Stop if the instrument, current quote or account controls cannot be verified.

## Procedure

1. **Verify the two instruments.** The assistant identifies the spot token and perpetual-futures contract before comparing prices. A shared BTC label does not make UBTC native bitcoin, and a perpetual future is a derivative rather than a token balance. Tools: `get_spot_metadata`, `get_market`.
2. **Read funding, basis and liquidity.** Current and predicted funding answer who may pay whom at the next interval. Spot and perpetual prices show the basis. Both order books are required because a theoretical rate can be smaller than spread and slippage. Tools: `get_predicted_fundings`, `get_orderbook`.
3. **Read both account states.** The assistant checks balances, positions, resting orders, fees and Fensory account controls before sizing anything. An existing BTC position or order changes the net exposure of the proposed pair. Tools: `get_spot_account_state`, `get_account_state`, `get_open_orders`, `get_user_fees`.
4. **Prepare two equal-notional legs.** The analysis prepares a spot buy and an opposite perpetual-futures position of similar notional value. It does not call either write tool in the first request. The user reviews each exact leg separately. Tools: `place_hl_spot_order`, `place_perps_order`.
5. **Execute sequentially and reconcile.** After the user confirms one leg, the assistant verifies its actual fill before recalculating the second. This exposes leg risk rather than implying that two MCP calls form an atomic trade. Tools: `get_order_status`, `get_fills`, `get_open_orders`.

## Request template

Use the Fensory tools to evaluate a small funding-rate strategy on BTC. Stay read-only first. Call get_spot_metadata, get_market, get_predicted_fundings, get_orderbook for both the spot and perpetual markets, get_spot_account_state, get_account_state, get_open_orders and get_user_fees.

Identify the exact spot token and perpetual-futures contract. State that UBTC is a wrapped HyperCore spot token and that BTC perpetual futures use margin and can be liquidated. Report current spot and perp prices, their percentage difference, current and predicted funding, spread, visible depth, fees, balances, open orders, current positions, market allow-list, access expiry and per-order cap.

If predicted funding is positive, model a long-spot and short-perpetual pair with no more than $25 notional per leg. If predicted funding is zero, negative or inconsistent across the returned venues, stop after the analysis. Show the size, limit price, estimated fees and what must happen if only one leg fills. Do not describe the rate as yield or annualize one observation into an expected return.

Do not submit either leg during this request. If I later confirm the exact spot leg, place only that leg, read its order status and fills, then recalculate the required perpetual leg from the actual filled size and current market. Ask for a separate confirmation before the perpetual order. Stop if the markets do not match, either quote is stale, depth is insufficient or an account limit cannot be verified.

## Failure handling

- **Funding changes sign:** Funding is recalculated and paid hourly on Hyperliquid. A positive observation can shrink or turn negative while the position remains open, changing the economics without changing the two position sizes.
- **Only one leg fills:** A filled spot order with an unfilled short leaves outright long exposure. A filled short with no spot offset leaves a leveraged directional position. The prompt requires a predefined stop rule and a fresh calculation after the first fill.
- **The basis moves:** Spot and perpetual prices can diverge further before converging. Closing both legs at an unfavorable basis can outweigh funding received, even when the position was directionally balanced.
- **Fees exceed funding:** The workflow pays spread and trading fees on entry and exit and may pay funding instead of receiving it. Compare the actual costs with the funding payments recorded by the account rather than an annualized headline rate.
- **Margin is liquidated:** The perpetual leg remains margined. A large basis move or insufficient collateral can liquidate it while the spot leg remains, breaking the intended offset.

## Response contract

Report the account used, the exact instrument, the tools called, the controls that applied and the current order or position state. Separate a prepared order from a submitted order, and a submitted order from a fill. If no action was taken, say so directly.

## Sources

- [Hyperliquid funding documentation](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/funding)
- [Hyperliquid perpetual-futures contract specifications](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/contract-specifications)
- [Fensory MCP tools](https://fensory.com/mcp)

Product behavior and client permissions verified 2026-10-18.

Questions people ask

What does the Fensory Funding-Rate Strategy Agent Skill install?
It downloads one SKILL.md file containing operating instructions, risk boundaries, the tool sequence and a response contract. It does not install the Fensory MCP server or create an account.