AI agents

MCP endpoint

quik.space exposes a Model Context Protocol server over plain HTTP. The transport is JSON-RPC 2.0. All tool calls hit one URL.

https://quik.space/mcp

• Transport: HTTP POST, JSON body
• Protocol: JSON-RPC 2.0
• Methods: tools/list, tools/call
• Auth: none (wallet identity for paid actions)

Tools

Input schemas

{
  "name": "upload_file",
  "input_schema": {
    "type": "object",
    "properties": {
      "filename":       { "type": "string" },
      "content_base64": { "type": "string" },
      "content_type":   { "type": "string" },
      "owner_email":    { "type": "string", "format": "email" }
    },
    "required": ["filename", "content_base64"]
  }
}

{
  "name": "get_file_info",
  "input_schema": {
    "type": "object",
    "properties": {
      "share_url_or_id": { "type": "string" }
    },
    "required": ["share_url_or_id"]
  }
}

{
  "name": "extend_file",
  "input_schema": {
    "type": "object",
    "properties": {
      "share_url_or_id": { "type": "string" }
    },
    "required": ["share_url_or_id"]
  }
}

x402 payment flow

When a tool call requires payment, the server speaks x402 — the open standard that reuses HTTP 402 (Payment Required, reserved since 1997 and revived by Coinbase in 2025) to demand a stablecoin transfer before fulfilling the request.

1. 01Agent sends the JSON-RPC tool call to /mcp with no payment header.
2. 02If the tool requires payment, the server returns HTTP 402 with a JSON body describing the required amount (USDC), the chain (Base mainnet, EIP-3009 transferWithAuthorization), the recipient address, and a nonce.
3. 03Agent signs and submits a USDC transferWithAuthorization on Base. The standard is EIP-3009 with 6-decimal atomic units — $2.00 USDC is the literal integer 2000000.
4. 04Agent retries the original tool call with an X-Payment-Proof header carrying the signed authorization payload.
5. 05Server verifies the proof on Base, executes the tool, and returns HTTP 200 with the result.

Chain and asset

• Chain: Base mainnet (chain id 8453)
• Asset: USDC (Circle, native on Base)
• Atomic units: 6 decimals. $2.00 is the integer 2000000.
• Standard: EIP-3009 transferWithAuthorization signed off-chain, posted on-chain by the server.

Curl examples

upload_file (free tier)

curl -X POST https://quik.space/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "upload_file",
      "arguments": {
        "filename": "report.pdf",
        "content_base64": "JVBERi0xLjQK...",
        "content_type": "application/pdf"
      }
    }
  }'

get_file_info

curl -X POST https://quik.space/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "get_file_info",
      "arguments": {
        "share_url_or_id": "abc12345"
      }
    }
  }'

extend_file (after a 402 payment dance)

curl -X POST https://quik.space/mcp \
  -H "Content-Type: application/json" \
  -H "X-Payment-Proof: <base64-signed-eip3009-authorization>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
      "name": "extend_file",
      "arguments": {
        "share_url_or_id": "abc12345"
      }
    }
  }'

No signup. No API keys.

quik.space does not issue API keys to agents. There is no developer dashboard, no quota sheet, no plan upgrade. Identity is the wallet that signs the x402 authorization. If you can call HTTP and sign an EIP-3009 message, you can use quik.space.