Pokeperps

PokePerps AI Agent Skill

Platform: PokePerps — Decentralized Perpetual Futures Exchange for Pokemon TCG Card Prices Blockchain: Solana (mainnet-beta) Backend API: https://backend.pokeperps.fun WebSocket: wss://backend.pokeperps.fun/ws/trading Program ID: 8hH5CWo14R5QhaFUuXpxJytchS6NgrhRLHASyVeriEvN Collateral: USDC (EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v)

PokePerps lets you trade perpetual futures contracts on real Pokemon Trading Card Game card prices. Prices are sourced from TCGPlayer marketplace in real-time and published on-chain via an Ed25519-signed oracle.

MCP Server (Recommended)

The easiest way for AI agents to interact with PokePerps is via the Model Context Protocol (MCP) server.

Read-only mode (no wallet required):

{
  "mcpServers": {
    "pokeperps": {
      "command": "npx",
      "args": ["@pokeperps/mcp"]
    }
  }
}

With trade execution (requires Solana keypair):

{
  "mcpServers": {
    "pokeperps": {
      "command": "npx",
      "args": ["@pokeperps/mcp"],
      "env": {
        "POKEPERPS_KEYPAIR": "/path/to/your/keypair.json"
      }
    }
  }
}

MCP Environment Variables

MCP Tools

Read-only tools (always available):

Execution tools (require POKEPERPS_KEYPAIR):

MCP Resources

• pokeperps://docs/trading-guide — Trading guide and risk parameters
• pokeperps://docs/api-reference — Full OpenAPI specification

Trading Parameters

What you can do:

• Go long (bet price goes up) or short (bet price goes down)
• Use 1x–50x leverage
• Positions have no expiry (perpetual)
• Close anytime to realize PnL
• Prices track real TCGPlayer marketplace prices

Architecture

Agent (you)
  │
  ├── REST API (https://backend.pokeperps.fun/api/...)
  │     ├── Read-only: card data, prices, markets, positions
  │     └── Transaction builders: returns params for Solana transactions
  │
  ├── WebSocket (wss://backend.pokeperps.fun/ws/trading)
  │     └── Real-time price updates, position events
  │
  └── Solana RPC (https://api.mainnet-beta.solana.com)
        └── Sign & send transactions built from API params

The backend does NOT sign or submit transactions. It provides instruction data and account addresses. You build, sign, and submit transactions client-side.

Key API Endpoints

Base URL: https://backend.pokeperps.fun

Card Discovery

Trading

Transaction Builders

Oracle

See references/API.md for full request/response schemas.

Optimized Trading Flow

1. GET /api/trading/analytics/movers       → Find opportunities
2. POST /api/cards/batch                   → Fetch details for candidates
3. GET /api/cards/{id}/signals             → Get trading recommendation
4. GET /api/trading/prepare-trade/{id}     → Validate trade
5. POST /api/trading/tx/open-position      → Execute trade
6. GET /api/trading/portfolio/{wallet}     → Monitor positions

This uses 6 API calls instead of 15+ in the traditional flow.

PnL Calculation

margin = size / leverage
fee = size * 0.0005  (0.05% on open, same on close)

For long:
  unrealized_pnl = size * (current_price - entry_price) / entry_price
  liquidation_price = entry_price * (1 - (margin - maintenance_margin) / size)

For short:
  unrealized_pnl = size * (entry_price - current_price) / entry_price
  liquidation_price = entry_price * (1 + (margin - maintenance_margin) / size)

Maintenance margin = size * 0.01 (1%)

Decision-Making Signals

Use /api/cards/{id}/signals for pre-computed analysis:

Bullish (go long):

• Positive change_24h with high activity_score
• Recent sales trending above market_price
• Decreasing listing count (supply shrinking)
• High short OI relative to long (potential short squeeze)

Bearish (go short):

• Negative change_24h and change_30d
• Recent sales trending below market_price
• Increasing listing count (supply growing)
• High long OI relative to short (potential long squeeze)

WebSocket

Connect to wss://backend.pokeperps.fun/ws/trading:

{ "type": "subscribe", "products": [123456], "accounts": ["YourWallet"] }
{ "type": "ping" }

Events: price_update, position_opened, position_closed, market_stats, account_update

Rate Limits

Error Codes

See references/API.md for full error reference.

Agent Best Practices

Minimize API Calls

Position Management

1. Check riskStatus before opening new positions — avoid if warning or danger
2. Use distanceToLiquidation for stop-loss (conservative: close if <10%, moderate: <5%)
3. Monitor fundingDirection — avoid positions that pay funding
4. Check wouldExceedOI before large trades

Security

• Always verify PDAs client-side before signing transactions
• Never expose private keys in API calls
• Validate oracleAge < 15 seconds before trading
• Check canTrade from prepare-trade before proceeding

Additional References

• references/API.md — Full API request/response schemas
• references/TRANSACTIONS.md — On-chain transaction construction, PDA derivation, Ed25519 signing
• references/EXAMPLES.md — Complete code examples (TypeScript, Python, cURL)