The JQ API

One payment. Your choice to renew.

Unlimited jq.
No application query logs.

2 USDC · 30 days · Base mainnet
No subscription, automatic renewal, or token approval.

Free queries already keep JSON, filters, results, and source URLs out of application logs. A paid pass also removes daily IP/UUID counters and REST/MCP/Zapier usage analytics. It removes the daily query cap; document and execution limits still apply.

Only need an occasional query? Pay 0.005 USDC per query with an x402 client. That option retains per-query billing receipts and short-lived retry data; the pass below avoids per-query records.

01 · Save your access key

A UUID is your secret key.

Use an existing UUID to renew or check a pass. For a new pass, generate a key here. There is no email account or password recovery.

Keep this key in a password manager. Anyone with it can use your pass. This page does not save it in cookies or browser storage, put it in URLs, or send it to analytics.

02 · Pay once, or check an existing pass

2 USDC for 30 days.

Enter a saved UUID to check your access, or generate a new one.

Connect a browser wallet with at least 2 native USDC on Base. Your wallet keeps its private key; we never ask for a seed phrase.

Need a wallet or USDC?
  1. Set up a browser wallet that supports Base, such as MetaMask. Back up its recovery phrase privately.
  2. Receive or buy native USDC on Base. Ethereum, Solana, testnet USDC, and bridged USDbC cannot pay for this pass.
  3. Return here and connect your wallet. Confirm one authorization for exactly 2 USDC. Our facilitator submits the transfer; this payment does not require ETH gas in your wallet.
Verify the payment destination

Network: Base (chain ID 8453). Asset: native USDC.

0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Recipient:

0x03dC5879020703a53062C05706D1259E3B7A1a6F

The page validates the network, asset, recipient, amount, and checkout URL before requesting a signature. It requests a single-use USDC authorization, not an allowance.

03 · Connect your client

Copy your private MCP settings.

A normal MCP client can use an already-paid UUID without a wallet. These settings also require private access explicitly, so an unpaid or expired key cannot use free-tier tracking. 

Generate or enter a UUID to create connection settings.

The configuration contains your secret UUID. Keep it out of Git and shared chats. Disable any existing anonymous jq-api connection to avoid accidentally choosing it. Restart or reconnect your client, then ask it to call get_quota; active access returns tier: "paid", with no usage count.

Use REST instead 

              
Send the UUID only in the Authorization header, never in the URL.