Build a Hood Long frontend.
Without guessing.

Build a new Hood Long frontend against https://hoodlong.com.
Read these sources completely before coding:
1. https://hoodlong.com/llms-full.txt
2. https://hoodlong.com/openapi.json
3. https://hoodlong.com/webmcp-tools.json

Implement the documented wallet, open, close, reconciliation, positions,
chart, lending, loading, error, and responsive state machines. Preserve the
human review boundary. Return the implementation, architecture note, typed
API client, and completed acceptance-test matrix. Do not claim live trading
works from mocks or quote-only tests.

Treat the network object returned by markets as the runtime source of truth. Never ship a private RPC, 0x, Rialto, or price-provider key to a browser.

const API = "https://hoodlong.com/functions/v1/trade-api";

async function hoodLong(action, input = {}) {
  const response = await fetch(API, {
    method: "POST",
    headers: { "content-type": "application/json" },
    body: JSON.stringify({ action, ...input })
  });
  const data = await response.json();
  if (!response.ok || !data.ok) throw new Error(data.error || "API request failed");
  return data;
}

const { markets, network, routes } = await hoodLong("markets");
const { liquidity } = await hoodLong("market_liquidity", {
  marketId: markets[0].id
});

Only offer a market when it is returned by markets, borrowingPaused is false, and routes.long.executable is true. Refresh liquidity immediately before showing a maximum order size.

1. QuoteCall quote with market, collateral, leverage, direction, and wallet.
2. Authorize preparationCall prepare_challenge with the exact same intent, then ask the connected wallet to sign the returned message.
3. PrepareCall prepare with the challenge fields and signature. Continue only when preparation.ready is true.
4. Human reviewShow the latest quote, route, fees, liquidation level, transaction value, and expiry. Require an explicit user action.
5. Broadcast and recordSend the returned transaction through the user’s wallet, then call record with its hash.

const intent = {
  wallet: await signer.getAddress(),
  marketId,
  direction: "long",
  collateral: "0.01",
  leverage: "2",
  walletClientCapability: "native-value-v2"
};

const { challenge } = await hoodLong("prepare_challenge", intent);
const signature = await signer.signMessage(challenge.message);
const { quote, preparation } = await hoodLong("prepare", {
  ...intent,
  challengeId: challenge.id,
  challengeExpiresAt: challenge.expiresAt,
  signature
});

if (!preparation.ready) throw new Error(preparation.reason);
if (Date.parse(preparation.expiresAt) <= Date.now()) throw new Error("Preparation expired");

// Only after the user approves your visible confirmation screen:
const tx = await signer.sendTransaction(preparation.transaction);
await hoodLong("record", {
  wallet: intent.wallet,
  marketId,
  preparationId: preparation.preparationId,
  txHash: tx.hash
});

1. Find the positionCall positions for the wallet and select an open position ID.
2. Sign the intentRequest prepare_challenge with wallet and positionId, then sign its exact message.
3. Prepare the closeCall prepare_close. Display debt, estimatedCloseFee, topUpWeth, minimum WETH received, and expiry.
4. Broadcast and recordAfter explicit approval, send preparation.transaction and pass the hash to record_close.

Close preparations expire in about 20 seconds. The API computes any required top-up and rejects a top-up above the protocol’s 1 ETH safety limit. Do not infer or override it client-side.

Do not resubmit merely because indexing is delayed. Preserve the transaction hash, show an explorer link, and reconcile it until the API returns a terminal state.

For complete request schemas and examples, use the OpenAPI document. Numeric blockchain quantities returned inside routes and transactions are strings to preserve precision.

Prefer WebMCP when the user is already inside Hood Long: it preserves the visible UI, connected-wallet context, affordability checks, and confirmation queue. Prefer the HTTP API for your own application. The exact tool schemas are in webmcp-tools.json.

• Debounce quotes and do not poll executable swap quotes; request them only when the user enters review.
• Respect expiresAt, market limits, borrowing state, pool availability, wallet balance, and gas.
• Never change to, data, or value in a prepared transaction.
• Use a fresh challenge for every preparation. The wallet is limited to 12 preparations per minute.
• Short execution is not available until a dedicated short adapter is deployed; rely on route readiness instead of assuming support.