flight.airport-board

Live airport activity board. For an airport (ICAO like KSFO or IATA like SFO), returns recent/upcoming departures or arrivals — flight ident, registration, aircraft type, origin/destination airports, status, scheduled/estimated/actual gate times, gate and terminal. Choose the board with type. Real-time operational data for an airport; complements flight.status (single flight) and flight.route-schedule.

price
$0.0180 USDC per call
method
GET/api/flight/airport-board
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.
tier
Tier 2 — LLM/render upstream included

Overview

The airport board API is a pay-per-call flight endpoint built for AI agents and autonomous software. Live airport activity board.

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 airport board data source for an agent tool-use loop, an MCP host, or a backend that needs flight data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
airportrequiredstringAirport code, ICAO (KSFO) or IATA (SFO).
min 3 chars · max 4 chars · match ^[A-Za-z0-9]+$
typestringDefault departures.
one of: departures | arrivals | scheduled_departures | scheduled_arrivals
limitinteger
min 1 · max 30

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/flight/airport-board?airport=xxx&type=departures&limit=15'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/flight/airport-board?airport=xxx&type=departures&limit=15' \
  -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/flight/airport-board?airport=xxx&type=departures&limit=15'
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.flight.airportBoard({
  "airport": "xxx",
  "type": "departures",
  "limit": 15
})

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.flight.airport_board(airport="xxx", type="departures", limit=15)

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": "flight.airport-board",
    "arguments": {
      "airport": "xxx",
      "type": "departures",
      "limit": 15
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
metaobject
Example response datajson
{
  "ok": true,
  "items": [
    {
      "ident": "example",
      "identIata": "example",
      "registration": "example",
      "aircraftType": "example",
      "origin": {
        "icao": "example",
        "iata": "example",
        "name": "example",
        "city": "example",
        "timezone": "example"
      },
      "destination": {
        "icao": "example",
        "iata": "example",
        "name": "example",
        "city": "example",
        "timezone": "example"
      },
      "status": "example",
      "scheduledOut": "example",
      "estimatedOut": "example",
      "actualOut": "example",
      "scheduledIn": "example",
      "estimatedIn": "example",
      "actualIn": "example",
      "gateOrigin": "example",
      "gateDestination": "example",
      "terminalOrigin": "example",
      "terminalDestination": "example"
    }
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "meta": {
    "airport": "example",
    "type": "example"
  }
}

FAQ

Do I need an API key to use the airport board API?
No. flight.airport-board 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 airport board API cost?
$0.0180 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 airport board 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 flight.airport-board 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: airport board api · flight airport board api · airport board api for ai agents · x402 flight api · airport board api no api key · pay per call airport board api · flight api