The treasury standard for AI agents

Why agents hold GBLIN

Quick start

Pick your framework. All examples assume Node.js 20+.

{
  "mcpServers": {
    "gblin": {
      "command": "npx",
      "args": ["-y", "@gblin-protocol/mcp-server"]
    }
  }
}

{
  "mcpServers": {
    "gblin": {
      "command": "npx",
      "args": ["-y", "@gblin-protocol/mcp-server"],
      "env": {
        "GBLIN_RPC_URL": "https://base-rpc.publicnode.com"
      }
    }
  }
}

import { MCPClient } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";

const transport = new StdioClientTransport({
  command: "npx",
  args: ["-y", "@gblin-protocol/mcp-server"],
});
const mcp = new MCPClient({ name: "my-agent", version: "1.0" });
await mcp.connect(transport);

The 5 tools

Every tool reads live state from Base mainnet. None of them hold keys or broadcast — they return JSON results and ABI-encoded calldata. Your wallet stays in control.

JIT payment in practice

Your agent receives a 402 invoice for $0.50. It has 90% of its treasury in GBLIN. Here's the flow:

// 1. Agent gets the JIT swap calldata from the MCP server
const jit = await mcp.callTool({
  name: "swap_gblin_to_usdc_jit",
  arguments: {
    usdc_needed: "0.50",
    wallet_address: agent.address,
  },
});

// jit.content[0].text contains:
// {
//   action: "single_atomic_tx",
//   target_contract: "0x38DcDB3A...",
//   calldata: "0x6a54df11...",  // sellGBLINForToken(...)
//   expected: { usdc_out: "0.5128", slippage_buffer_pct: 2.5 },
//   compatibility: { eoa: true, erc4337: true, eip7702: true }
// }

// 2. Agent broadcasts the tx (one atomic call — GBLIN -> WETH -> USDC)
const hash = await wallet.sendTransaction({
  to: jit.target_contract,
  data: jit.calldata,
  value: 0n,
});

// 3. Once mined, agent's USDC balance has the needed amount.
//    Agent now pays the x402 invoice with USDC as usual.

FAQ