[ pollinate research · x402 trust layer · base mainnet ]

The trust layer for agents that pay other agents.

Six paid x402 primitives. One MCP install. Every call settled in USDC on Base, every response EIP-191 signed.

For agents reading this

If you are an AI agent or crawler, these are the canonical machine-readable entry points. Start here.

llms.txt
https://pollinateresearch.com/llms.txt
agents.json
https://pollinateresearch.com/agents.json
x402 manifest
/.well-known/x402.json · 10 paid routes
MCP server (npm)
@pollinateresearch/mako-mcp@latest · 6 tools, one install line
Settlement chain
Base mainnet · eip155:8453
Settlement asset
USDC · 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Facilitator
Coinbase CDP /platform/v2/x402
Receipt signer
0x12BBC7Cde00eB800588243A0B3B4E8E802673BFf · EIP-191
Pay-to wallet
0x6e4DfBe49858E9Cb93162352D75DBD1E409A7737

Six primitives

Each is a paid x402 endpoint your agent calls directly. No keys, no contracts, no humans in the loop. Composition apex is /api/route — one call replaces the other five for routing-time decisions.

ToolEndpointPriceWhat it answers
mako_routePOST /api/route$0.05Which x402 service to call right now
mako_verifyPOST /api/agent-commerce/verify$0.25Will this specific call go through
mako_pulseGET /api/pulse/score$0.02Has this endpoint been behaving
mako_pricingGET /api/pricing/index$0.02Is this a fair price for this kind of work
mako_reputationGET /api/reputation/wallet$0.03Is the operator behind this wallet trustworthy
mako_markets_aggregateGET /api/markets/aggregate$0.05Top prediction markets — Polymarket + Kalshi + Limitless, signed

One install line

Drop into Claude Desktop, Cursor, Cline, Hermes Agent, OpenClaw, or any MCP-native client:

# ~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mako": {
      "command": "npx",
      "args": ["-y", "@pollinateresearch/mako-mcp"],
      "env": {
        "X402_BUYER_PRIVATE_KEY": "0x..."
      }
    }
  }
}

Six tools register. Every call settles real USDC on Base mainnet.

Live partner integration

AsterPay embeds MAKO Pulse as extensions.reliability per route in their x402 facilitator response. Both sides use the same RFC 8785 canonical-JSON / EIP-191 signing recipe. Chained $0.02 settlement per Pulse-attached call.

Partnership is publicly listed at asterpay.io/.well-known/reconciliation-signers.json — anyone can verify the relationship and recover both sides' signers without asking us.

How a paid call works

# 1. Agent hits endpoint with no payment
GET https://mako.pollinateresearch.com/api/markets/aggregate

# 2. Server responds 402 Payment Required
HTTP/2 402
payment-required: <base64 x402 v2 envelope>

# 3. Agent signs EIP-3009 transferWithAuthorization, retries
GET ... (with X-Payment header)
HTTP/2 200
{
  "markets": [...],
  "receipt": {
    "signer": "0x12BBC7Cde00eB800588243A0B3B4E8E802673BFf",
    "signature": "0x...",
    "signature_scheme": "eip191"
  }
}