Add Predge to your agent

01Any MCP host — the config block

Predge is a stdio MCP server launched with npx. Drop it into your host's MCP config with a wallet key it pays from and an optional hard spend cap. That's the whole integration:

{
  "mcpServers": {
    "predge": {
      "command": "npx",
      "args": ["-y", "@predge/whale-data-mcp"],
      "env": {
        "BUYER_PRIVATE_KEY": "0x…",
        "MAX_PRICE_USD": "0.05"
      }
    }
  }
}

• Use a dedicated, low-balance wallet for agent spending — never a main key. A few dollars of USDC covers hundreds of calls at $0.005–$0.03 each.
• MAX_PRICE_USD is enforced before any payment — the agent can't be talked into an unbounded spend.
• Base and/or Solana: set BUYER_PRIVATE_KEY (Base) and/or SOLANA_BUYER_SECRET (Solana); every 402 advertises both, the client pays whichever you funded.

02ElizaOS agents

With the MCP plugin, an ElizaOS agent adds Predge in its character file — no custom code:

{
  "name": "Your trading agent",
  "plugins": ["@fleek-platform/eliza-plugin-mcp"],
  "settings": {
    "mcp": {
      "servers": {
        "predge": {
          "type": "stdio",
          "command": "npx",
          "args": ["-y", "@predge/whale-data-mcp"],
          "env": { "BUYER_PRIVATE_KEY": "0x…", "MAX_PRICE_USD": "0.05" }
        }
      }
    }
  }
}

Your agent's research step can now call Predge's signals before it decides a trade — e.g. a Polymarket agent like Pamela weighting a smart-money consensus, or stamping resolved picks with a signed outcome for a provable track record.

03Claude Code / Claude Desktop & other hosts

Claude Code — one command:

claude mcp add predge --env BUYER_PRIVATE_KEY=0x… --env MAX_PRICE_USD=0.05 \
  -- npx -y @predge/whale-data-mcp

Claude Desktop — the same mcpServers block from §01 in claude_desktop_config.json. A packaged .mcpb for one-click install ships on the GitHub releases.

04Not on MCP? Raw x402 from any stack

Every endpoint is a plain GET gated by x402 — no MCP required. Window-shop for free (the 402 carries price + schema), then let any x402 client pay and retry:

# free: the 402 advertises price, schema and both networks
curl -i "https://x402-api-production-266e.up.railway.app/v1/signals/consensus"

# paid: any x402 client signs USDC and retries (Base or Solana)
npx x402-proxy "https://x402-api-production-266e.up.railway.app/v1/signals/consensus"

TS/JS agents can wrap fetch with @x402/fetch + @x402/evm; full machine docs at llms.txt and openapi.json.

05What your agent gets

20 pay-per-call endpoints, $0.005–$0.03 each. The ones that matter for a prediction-market agent:

predge_list_endpoints is free — call it first to discover every tool, price, and schema at runtime.

06The honest fine print

• Pay-per-call, no keys, no accounts. USDC on Base or Solana mainnet, gasless via facilitator. The wallet just pays; there's nothing to provision.
• Outcome-verified, not vibes. Win rates count resolved markets only — a trade wins when its side matches the final resolution. Consensus aggregates only wallets that clear the score threshold.
• A signal input, not a guaranteed edge. It's cheap to A/B-test as a feature or filter, and cheap to discard if it doesn't help your strategy — a full signal sweep is cents.
• Delayed 15 minutes. This is a positioning/context layer, not an HFT feed. Real-time stays with Predge Pro.
• Errors are never charged, and every paid response returns the on-chain settle transaction for your own accounting.

Full docs & quickstart → Verify a signed outcome (free)