Minara API

Crypto trading intelligence. Two independent concerns:

1. Calling Minara API (analysis, intent parsing, strategy) — requires MINARA_API_KEY or x402.
2. On-chain execution / signing — requires circle-wallet CLI (Circle Wallet skill) or EVM_PRIVATE_KEY (direct EOA). These are independent of each other.

Minara API auth

Use API Key when MINARA_API_KEY is set; fall back to x402 when only EVM_PRIVATE_KEY is available. x402 is for Minara API payment only — not needed for on-chain execution.

On-chain signing

A valid setup can be MINARA_API_KEY + circle-wallet configured with no EVM_PRIVATE_KEY — Circle handles all signing.

Decision logic

Step 1 — Call Minara API (analysis / intent / strategy):
  IF MINARA_API_KEY is set → use API Key auth
  ELSE IF EVM_PRIVATE_KEY is set → use x402 pay-per-use
  (Circle Wallet is NOT used for Minara API auth)

Step 2 — On-chain execution (only when user wants to trade):

  User asks to send USDC:
    → circle-wallet send <to> <amount> --from <wallet>

  User asks to swap tokens:
    → Minara intent-to-swap-tx → get params
    → IF circle-wallet configured → Circle SDK contractExecution (read {baseDir}/examples.md, Example 1)
    → ELSE IF EVM_PRIVATE_KEY → sign locally with viem

  User asks to open a perp position on Hyperliquid:
    → Minara perp-trading-suggestion → get strategy
    → Confirm with user (show entry, SL, TP, confidence, risks)
    → IF circle-wallet configured → Circle SDK signTypedData → Hyperliquid (read {baseDir}/examples.md, Example 2)
    → ELSE IF EVM_PRIVATE_KEY → sign EIP-712 locally → Hyperliquid

  User only asks for analysis / market insights / prediction:
    → No signing needed. Return Minara response directly.

Endpoints

All endpoints: POST, headers Authorization: Bearer $MINARA_API_KEY, Content-Type: application/json.

Chat

POST https://api.minara.ai/v1/developer/chat

{ "mode": "fast|expert", "stream": false, "message": { "role": "user", "content": "..." }, "chatId": "optional" }

Response: { chatId, messageId, content, usage }

Intent to Swap

POST https://api.minara.ai/v1/developer/intent-to-swap-tx

{ "intent": "swap 0.1 ETH to USDC", "walletAddress": "0x...", "chain": "base" }

Chains: base, ethereum, bsc, arbitrum, optimism.

Response: { transaction: { chain, inputTokenAddress, inputTokenSymbol, outputTokenAddress, outputTokenSymbol, amount, amountPercentage, slippagePercent } }

Perp Trading Suggestion

POST https://api.minara.ai/v1/developer/perp-trading-suggestion

{ "symbol": "ETH", "style": "scalping", "marginUSD": 1000, "leverage": 10, "strategy": "max-profit" }

Styles: scalping (default), day-trading, swing-trading. Leverage: 1–40.

Response: { entryPrice, side, stopLossPrice, takeProfitPrice, confidence, reasons, risks }

Prediction Market

POST https://api.minara.ai/v1/developer/prediction-market-ask

{ "link": "https://polymarket.com/event/...", "mode": "expert", "only_result": false, "customPrompt": "optional" }

Response: { predictions: [{ outcome, yesProb, noProb }], reasoning }

x402 (pay-per-use)

SDK handles 402 challenges automatically. See x402 docs.

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const signer = privateKeyToAccount(process.env.EVM_PRIVATE_KEY as `0x${string}`);
const client = new x402Client();
registerExactEvmScheme(client, { signer });
const fetchWithPayment = wrapFetchWithPayment(fetch, client);

const res = await fetchWithPayment("https://x402.minara.ai/x402/chat", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ userQuery: "What is the current price of BTC?" }),
});

Dependencies: @x402/fetch, @x402/evm, viem.

x402 Chat endpoint: POST https://x402.minara.ai/x402/chat — body { "userQuery": "..." }, response { content }.

Chain-specific: .../x402/solana/chat, .../x402/polygon/chat.

x402 uses a standalone EOA signer. Circle MPC wallets do not expose private keys — keep x402 and Circle wallets separate.

Circle Wallet integration

Install and set up the circle-wallet skill:

clawhub install circle-wallet
cd ~/.openclaw/workspace/skills/circle-wallet && npm install && npm link
circle-wallet setup --api-key <YOUR_CIRCLE_API_KEY>

This generates an entity secret, registers it with Circle, and stores credentials in ~/.openclaw/circle-wallet/config.json. No manual ciphertext or walletSetId management needed.

Basic operations (CLI)

circle-wallet create "Trading Wallet" --chain BASE   # Create SCA wallet on Base
circle-wallet list                                     # List wallets with balances
circle-wallet balance                                  # Check USDC balance
circle-wallet send 0xRecipient... 10 --from 0xWallet...  # Send USDC (gas-free)
circle-wallet drip                                     # Get testnet USDC (sandbox only)

Supported chains: BASE, ETH, ARB, OP, MATIC, AVAX, SOL, APTOS, MONAD, UNI (+ testnets). Run circle-wallet chains for full list.

Advanced operations (SDK)

The CLI handles USDC transfers. For DEX swaps (contractExecution) and Hyperliquid order signing (signTypedData), use the @circle-fin/developer-controlled-wallets SDK directly. The config from ~/.openclaw/circle-wallet/config.json provides apiKey and entitySecret:

import { initiateDeveloperControlledWalletsClient } from "@circle-fin/developer-controlled-wallets";
import * as fs from "fs";

const config = JSON.parse(
  fs.readFileSync(`${process.env.HOME}/.openclaw/circle-wallet/config.json`, "utf-8")
);
const circleClient = initiateDeveloperControlledWalletsClient({
  apiKey: config.apiKey,
  entitySecret: config.entitySecret,
});

SDK operations used by Minara integration:

For contract execution and signTypedData, the SDK does not expose direct methods — use fetch with the apiKey from config. The SDK handles entitySecretCiphertext generation internally for createTransaction.

For full code, read {baseDir}/examples.md.

Config

~/.openclaw/openclaw.json:

{
  "skills": {
    "entries": {
      "minara": {
        "enabled": true,
        "apiKey": "YOUR_MINARA_API_KEY",
        "env": { "EVM_PRIVATE_KEY": "0x..." }
      },
      "circle-wallet": {
        "enabled": true
      }
    }
  }
}

• minara.apiKey — Minara API Key, or set MINARA_API_KEY in env.
• minara.env.EVM_PRIVATE_KEY — EOA wallet for x402 pay-per-use. Not the Circle wallet.
• circle-wallet — enable only; credentials are managed by circle-wallet setup and stored in ~/.openclaw/circle-wallet/config.json.

Additional resources

• Full integration examples with code: {baseDir}/examples.md
• Minara docs: minara.ai/docs
• Circle Wallet skill: clawhub.ai/eltontay/circle-wallet
• Circle API docs: developers.circle.com
• Hyperliquid API: hyperliquid.gitbook.io