tcg.sets

List the sets (groups) for a trading-card game — e.g. every Pokemon or Magic: The Gathering set. Pass game (a categoryId like 3, or a name like "pokemon"/"magic" — resolved against tcg.games), optional q (case-insensitive substring filter on set name), and optional limit (default 100, max 500). Each row is { groupId, name, abbreviation, publishedOn, isSupplemental }. Use the groupId as the `set` parameter on tcg.set-prices / tcg.card. total is the full match count (pre-limit). Source: TCGplayer-derived pricing via tcgcsv.com.

price
$0.0048 USDC per call
method
GET/api/tcg/sets
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The sets API is a pay-per-call tcg endpoint built for AI agents and autonomous software. List the sets (groups) for a trading-card game — e.g.

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in sets data source for an agent tool-use loop, an MCP host, or a backend that needs tcg data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
gamerequiredstringTCGplayer game: categoryId (e.g. 3) or name (e.g. "pokemon", "magic").
min 1 chars · max 60 chars
qstringCase-insensitive substring filter on set name.
max 80 chars
limitintegerMax sets to return (default 100, max 500).
min 1 · max 500

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/tcg/sets?game=example&q=example&limit=1'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/tcg/sets?game=example&q=example&limit=1' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>'

# Or use the canonical runner (handles probe → sign → retry):
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/tcg/sets?game=example&q=example&limit=1'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.tcg.sets({
  "game": "example",
  "q": "example",
  "limit": 1
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.tcg.sets(game="example", q="example", limit=1)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "tcg.sets",
    "arguments": {
      "game": "example",
      "q": "example",
      "limit": 1
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
metaobject
Example response datajson
{
  "ok": true,
  "items": [
    {
      "groupId": 1,
      "name": "example",
      "abbreviation": "example",
      "publishedOn": "example",
      "isSupplemental": false
    }
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "meta": {
    "categoryId": 1,
    "returned": 1
  }
}

FAQ

Do I need an API key to use the sets API?
No. tcg.sets is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the sets API cost?
$0.0048 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the sets API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call tcg.sets from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: sets api · tcg sets api · sets api for ai agents · x402 tcg api · sets api no api key · pay per call sets api · tcg api