aircraft.profile

Identify a US-registered aircraft by tail (N-number) or icao24 Mode-S hex, AND screen its owner and operator against the OFAC sanctions list — in one call. Returns the full aircraft record (registration, manufacturer, model, type, serial, owner, operator, year built) plus a sanctions screen of the owner and operator names against OFAC SDN, with fuzzy-match confidence and a flagged boolean. OSINT, asset-tracing, sanctions-evasion investigation, due diligence. Composition of /api/aircraft/lookup + /api/law/sanctions-check (the sanctions section reports found/error independently). Note: screening is name-based and probabilistic — review flagged matches manually.

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

Overview

The profile API is a pay-per-call aircraft endpoint built for AI agents and autonomous software. Identify a US-registered aircraft by tail (N-number) or icao24 Mode-S hex, AND screen its owner and operator against the OFAC sanctions list — in one call.

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

Use cases

Parameters

NameTypeDescription
tailstring
min 2 chars · max 10 chars
icao24string
match ^[0-9a-fA-F]{6}$
thresholdnumber
min 0.1 · max 1

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/aircraft/profile?tail=xx&icao24=example&threshold=0.5'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/aircraft/profile?tail=xx&icao24=example&threshold=0.5' \
  -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/aircraft/profile?tail=xx&icao24=example&threshold=0.5'
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.aircraft.profile({
  "tail": "xx",
  "icao24": "example",
  "threshold": 0.5
})

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.aircraft.profile(tail="xx", icao24="example", threshold=0.5)

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": "aircraft.profile",
    "arguments": {
      "tail": "xx",
      "icao24": "example",
      "threshold": 0.5
    }
  }
}

Response

FieldTypeDescription
aircraftobject
ownerScreenobject
operatorScreenobject
sourcesarray
Example response datajson
{
  "aircraft": {},
  "ownerScreen": {
    "found": false,
    "error": "example",
    "flagged": false,
    "matchCount": 1,
    "matches": [
      {}
    ]
  },
  "operatorScreen": {
    "found": false,
    "error": "example",
    "flagged": false,
    "matchCount": 1,
    "matches": [
      {}
    ]
  },
  "sources": [
    {}
  ]
}

FAQ

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