1gateway.dev x402 offerings

Use when an agent needs an ERC-20's basics on Base before quoting, transferring or approving it. Input: address (token contract); optional holder (adds balance and share of supply) and spender (adds allowance, flags unlimited approvals). Output: JSON block+time, name, symbol, decimals, totalSupply raw and decimal, known issuer if curated. Name/symbol are self-reported. EOA or non-ERC-20: 4xx, not charged. Example: ?address=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Use when scheduling across time zones or turning a local time into UTC without guessing DST. Input: to (IANA zones or KST, PST, CET...), optional from (zone of a local time, default UTC), time (ISO 8601, Unix seconds, or now). Output: JSON UTC instant, Unix time, and per zone: local ISO time with offset, weekday, abbreviation, DST and business-hours flags, day difference. Example: ?time=2026-10-12T09:00&from=Asia/Seoul&to=America/New_York,Europe/London

Use when an agent needs what a Base address holds in one call instead of one RPC call per token. Input: address; optional tokens (up to 20 ERC-20 addresses, comma-separated; default USDC, EURC, USDbC, WETH, cbBTC, cbETH, wstETH). Output: JSON block+time, ETH balance, per-token symbol, decimals, raw and decimal balance, nonce, isContract. Chain state only, no prices. Bad input: 400, not charged. Example: ?address=0x6246eee0355Dd7A93C888fE59e1151388A0cC5a1

Use when an agent must confirm a Base transaction or payment landed: did it succeed, who paid whom, how much of which token. Input: hash. Output: JSON status (success/reverted), block+time, confirmations, from, to, ETH value, fee (L2 gas + L1 data fee), decoded ERC-20 transfers with symbol and decimal amount (first 25). Unknown or unmined hash: 404, not charged. Example: ?hash=0x284f8abed91b5631ee28bdb1ccfe78374e18c480cb2ab25f28e3bfac5210fe0b

Use when an agent must read a document as clean Markdown: web page, PDF, DOCX or Korean HWP/HWPX, tables kept. Input: url (http/https) via GET, or POST a file (multipart 'file', raw body, or JSON contentBase64+filename). Free-plan size cap → 413 before payment: HWP 48 KB, HWPX 100 KB XML. Output: JSON markdown, title, pages, sourceType, warnings. Price by detected type: HTML $0.0027, PDF/DOCX $0.0045, HWP/HWPX $0.009. Example: ?url=https://example.com/

Use when you need official Bank of Korea statistics (base rate, money supply, key indicators) as a time series. Input: stat (ECOS table code, e.g. 722Y001), cycle (A/S/Q/M/SM/D), start, end (period format of cycle), optional item (e.g. 0101000). Output: JSON series with English labels, units, observations [{period,value}] (max 1,000 rows) and source attribution. Only BOK-authored tables are served. Example: ?stat=722Y001&cycle=M&start=202401&end=202412&item=0101000

Use when you need South Korea's monthly trade for a product by HS code (e.g. 8542 chips, 870323 cars, 2710 petroleum). Data: Korea Customs Service, finalized monthly. Input: hs (2-10 digit prefix), optional month (YYYYMM, default latest), limit (1-100), sort (exports, imports, balance, total). Output: JSON totals (exports FOB, imports CIF, balance in USD, kg) with YoY % and 10-digit HSK lines with English HS descriptions and YoY. Example: ?hs=8542&month=202608

Use when you need an official daily FX rate or currency conversion (USD, EUR, KRW, JPY, CNY, GBP + 24 more). Input: base (default EUR), optional symbols (comma list), date (YYYY-MM-DD, last ~90 days; weekends use the prior fixing), amount. Output: JSON rates for the fixing date, % change vs prior fixing, converted amounts, raw ECB EUR rates. Source: ECB statistics, updated each TARGET day ~16:00 CET; reference only. Example: ?base=USD&symbols=KRW,JPY&amount=100

Use when an agent needs to know what a URL is before reading it, or to build a link preview or citation. Input: url (public http/https). Output: JSON with final URL after redirects, HTTP status, content type, title, description, site name, language, canonical, preview image, favicon, Open Graph and Twitter tags, RSS/Atom feeds, hreflang alternates, JSON-LD types, robots, first H1. No JavaScript is run. Example: ?url=https://developer.mozilla.org/en-US/

Use when you need South Korea's earliest export read: the Korea Customs 10-day provisional release (days 1-10, 1-20, full month; out on the 11th, 21st and 1st). Input: optional month (YYYYMM) and period (10, 20, full); default latest. Output: JSON exports in USD with YoY %, latest 10-day increment, 10 key items (semiconductors, cars, ships...) and 10 markets (China, US, EU, Vietnam...) with YoY and share, next release date. Example: ?month=202609

Use when you need a one-call read on South Korea's export cycle for macro, FX or chip-sector analysis. Data: Korea Customs 10-day and monthly releases. Input: none. Output: JSON headline (latest exports and YoY, semiconductor share, strongest/weakest item and market, 3-month average YoY, momentum), latest release by item and market, 12 monthly export totals with YoY, and HS 8542 integrated-circuit trade for the latest month. Example: /v1/trade/pulse

Use when an agent must check a domain: does it resolve, who hosts its DNS and mail, is email authenticated, how old is it, when does it expire. Input: domain (e.g. example.com; URLs accepted). Output: JSON DNS records (A, AAAA, CNAME, MX, NS, TXT, CAA, SOA), mail provider, parsed SPF and DMARC, DNS provider, and RDAP registration (registrar, created, expires, age in days, status, DNSSEC). No contact data. Example: ?domain=google.com

Use when an agent must vet or research a website in one call (lead research, security or SEO check, is this site legit). Input: url or bare domain. Output: JSON page metadata, HTTP status, HTTPS and HTTP-to-HTTPS redirect, server and hosting hints, 7 security headers, robots.txt (sitemaps, AI-crawler rules), llms.txt presence, plus domain DNS, mail provider, SPF/DMARC and RDAP registrar, age and expiry. Example: ?url=stripe.com

Use when you need actual apartment sale prices in a South Korean district for a month (property research, valuation, comps). Data: MOLIT (Korea land ministry) reported deals since 2006, updated daily. Input: region (5-digit LAWD_CD, e.g. 11680 Gangnam-gu), month (YYYYMM). Output: JSON trades with contract date, complex (Korean + romanized), area m2, floor, build year, price in KRW and USD, price per m2, deal type, cancelled flag. Example: ?region=11680&month=202609

Use when you need the official weather forecast for a point in South Korea for the next ~3-5 days. Data: KMA (Korea Meteorological Administration) village forecast on a 5 km grid, issued 8 times a day. Input: lat, lon (WGS84 decimal; Korea only). Output: JSON hourly then 3-hourly temperature C, sky, precipitation type and probability %, rain and snow amounts, humidity %, wind; plus daily min/max. Example: ?lat=37.5665&lon=126.978

Use when you need South Korea's official public holidays for a year (business-day calculation, scheduling, settlement and payroll calendars). Data: KASI (Korea Astronomy and Space Science Institute) special-day register, incl. substitute and temporary holidays once promulgated. Input: year (YYYY, 2004-2100). Output: JSON list with date, weekday, Korean and English name, isPublicHoliday, kind. Example: ?year=2026

Use when you need a quick housing-market snapshot for a South Korean district-month instead of raw trades. Data: MOLIT reported apartment sales, cancelled deals excluded. Input: region (5-digit LAWD_CD, e.g. 11680), month (YYYYMM). Output: JSON count, median/average/min/max price and price per m2 and per pyeong in KRW and USD, breakdown by size class, top complexes by volume. Example: ?region=11680&month=202609

Use when an agent needs the weather anywhere in the world. Input: lat, lon, optional hours (0-72 hourly steps, default 24), tz (IANA zone for daily summaries, default UTC). Output: JSON current temperature, symbol, wind, humidity, cloud, pressure; hourly series; daily min/max, precipitation, max wind, symbol for ~10 days. Data: MET Norway. Example: ?lat=51.5072&lon=-0.1276&tz=Europe/London

Use when an agent must price or time a Base transaction. Input: none. Output: JSON current and next base fee, priority fee tiers (slow/standard/fast from the last 20 blocks), suggested maxFeePerGas, block fullness, and typical cost of an ETH transfer, ERC-20 transfer/approve, DEX swap, NFT mint and contract deploy (L2 fee + L1 data fee) in ETH and USD. Example: /v1/onchain/base/gas

Use when an agent must check a dependency before installing or upgrading: is this exact package version vulnerable? Input: package, ecosystem (npm, PyPI, Go, Maven, crates.io, NuGet, RubyGems, Packagist...), version. Output: JSON vulnerable yes/no, counts by severity, advisories (GHSA/CVE id, summary, severity, CVSS, CWE, fixed versions, links). Data: OSV.dev. Example: ?package=lodash&ecosystem=npm&version=4.17.15

Use when an agent must see a place from above or check vegetation, water or change. Input: lat, lon, radius_m (200-10000), mode (true_color, false_color, ndvi, ndwi, moisture), date, days back, max_cloud. Picks the clearest Sentinel-2 scene by cloud share inside your area, not the whole tile. Output: JSON PNG URL (+ other modes), scene date, area cloud %, alternatives. No scene: 404, not charged. Example: ?lat=37.5665&lon=126.978

Use when an agent must see who is buying or dumping a Base ERC-20 right now (smart-money / whale flow). Input: token address, optional wallet, minutes (1-60), limit. Output: JSON DEX buys vs sells (Uniswap v2/v3/v4, Aerodrome swaps) with netflow, buy/sell ratio, top buyers and sellers, largest swaps, pools; transfer net buyers/sellers tagged contract/EOA/pool/whale; wallet drill-down. On-chain only. Example: ?address=0x4ed4E862860beD51a9570b96d89aF5E1B0Efefed

Use when an agent, test suite or CI job needs Sepolia gas now: one x402 call, no faucet login or mainnet history. Input: to (recipient address); sends 0.1 SepETH (1 SepETH: /v1/testnet/sepolia-eth/1). Output: JSON txHash (confirmed before settling), explorerUrl, amountEth, from, to. Daily limits (UTC): 5 SepETH per address (both sizes), 20 overall; checked before payment. Test ETH has no monetary value. Example: ?to=0x000000000000000000000000000000000000dEaD

Use when an agent must confirm a Solana payment or transaction landed: did it succeed, who paid whom, how much of which token. Input: signature. Output: JSON status (success/failed), slot, block time, confirmation status, fee payer, signers, fee, programs, SOL and token balance changes per account (first 25). Unknown signature: 404, not charged. Example: ?signature=5Xg1wCobkM4jAJNHE6t7B1amt4ch5wq5GrxuhQXXgoAkUPUAjVMC9tQFCvp1awUGfrqZY9L9sLdPieJ97DcDjXtC