Tool search 164,478 tools · 10,067 live servers

Search Chainstack docs — blockchain RPC methods, node infrastructure, Web3 APIs, deployment guides, and code examples. Args: query: Search query (e.g., "deploy ethereum node", "eth_call").

Paid hosted discovery for SAP agents. Search and filter the current on-chain AgentAccount directory by query, wallet, protocol, capability, x402 endpoint presence, and cursor pagination. Use this for targeted agent discovery before calling per-agent fetch tools. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

Paid hosted global SAP agent directory read. Enumerates current on-chain AgentAccount PDAs and supports query, wallet, protocol, capability, x402 endpoint filtering, compact/full views, and cursor pagination. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

Get detailed information about a single NFT/asset via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

Get all NFTs/assets owned by a wallet via DAS (supports pagination). SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

Get all NFTs/assets created by a specific creator via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

Get all NFTs in a collection via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

Ask Shumi any crypto-market question in natural language. Shumi classifies the query, fetches the relevant data, and returns a synthesized answer. Use this when no specific typed tool fits, or for multi-part / comparative questions.

FREE. One ticker's full current record — tier, channel, call, specifics, stance and previous stance, breadth, first/last seen — plus its catalysts and its anchor proof. The same facts are also free as static JSON at /coins/<TICKER>.json; this tool is the queryable form, not privileged content. Upstream briefs land on about 71% of days; board content is same-day roughly half the time and is never more than three days old. Not real-time. Every payload carries stale / stale_days / built_from_brief_date — read them. Commentary on public statements, not advice. This tool does not accept portfolio, position or risk-profile inputs and will refuse them with HTTP 400.

Use this when you need a swap quote before trading tokens on-chain. Returns the best price across multiple DEXes in JSON. POST variant of dex_get_swap_quote -- same params passed as JSON body instead of query string. 1. bestDex: which DEX offers the best rate (Uniswap, SushiSwap, Aerodrome) 2. amountOut: expected output token amount 3. priceImpact: percentage price impact of the trade 4. minimumReceived: minimum output after slippage tolerance 5. route: swap path (e.g. USDC -> WETH -> TOKEN) 6. gasEstimateUsd: estimated gas cost in USD Example output: {"bestDex":"Uniswap V3","amountOut":"0.3215","priceImpact":"0.12%","minimumReceived":"0.3183","route":["USDC","WETH"],"gasEstimateUsd":0.04} Use this BEFORE executing any token swap to find the best rate and estimate slippage. Essential for trade sizing and DEX comparison. Do NOT use for gas estimation only -- use gas_get_current_price instead. Do NOT use for yield opportunities -- use defi_find_best_yields instead. Do NOT use for wallet balance -- use wallet_get_portfolio instead. Do NOT use for cross-chain bridging -- use bridge_find_best_route instead.

Use this when you need DeFi yield opportunities specifically on Base chain. Returns Base-native protocol yields in JSON. POST variant of base_get_defi_opportunities -- same params passed as JSON body instead of query string. 1. opportunities: array of yield farms ranked by APY 2. protocol: protocol name (Aerodrome, Moonwell) 3. pool: pool name and token pair 4. apy: current annual percentage yield 5. tvl: total value locked in USD 6. riskScore: risk rating (1-10, lower is safer) 7. type: yield type (LP, lending, staking) Example output: {"opportunities":[{"protocol":"Aerodrome","pool":"USDC/WETH","apy":18.5,"tvl":45000000,"riskScore":3,"type":"LP"},{"protocol":"Moonwell","pool":"USDC Lending","apy":5.2,"tvl":120000000,"riskScore":1,"type":"lending"}],"chain":"base","totalPools":12} Use this FOR deploying capital on Base chain specifically. Curated list of vetted Base-native protocols only. Do NOT use for multi-chain yields -- use defi_find_best_yields instead. Do NOT use for swap quotes on Base -- use dex_get_swap_quote instead. Do NOT use for liquidation risk -- use defi_get_liquidation_levels instead.

Use this when you need to find the best DeFi yields for a token across all chains and protocols. Returns ranked opportunities in JSON. POST variant of defi_find_best_yields -- same params passed as JSON body instead of query string. 1. pool: pool/vault name and pair 2. protocol: protocol name (Aave, Compound, Lido, Aerodrome, etc.) 3. chain: which blockchain network 4. apy: current annual percentage yield 5. tvl: total value locked in USD 6. riskLevel: risk assessment (low/medium/high) 7. type: yield type (lending, staking, LP, vault) Example output: {"pools":[{"pool":"USDC Lending","protocol":"Aave V3","chain":"base","apy":4.82,"tvl":125000000,"riskLevel":"low","type":"lending"}],"token":"USDC","totalPools":15} Use this BEFORE deploying idle capital to find the highest safe yield. Essential for yield optimization and DeFi strategy comparison. Do NOT use for swap quotes -- use dex_get_swap_quote instead. Do NOT use for wallet balance -- use wallet_get_portfolio instead. Do NOT use for Base-only yields -- use base_get_defi_opportunities instead. Do NOT use for liquidation risk -- use defi_get_liquidation_levels instead.

Use this when you need a swap quote on Solana. Returns the best route via Jupiter aggregator across all Solana DEXes with price impact and fee analysis. POST variant of jupiter_get_swap_quote -- same params passed as JSON body instead of query string. 1. inputToken: input token symbol and mint address 2. outputToken: output token symbol and mint address 3. inAmount: input amount in raw units 4. outAmount: expected output amount in raw units 5. priceImpact: price impact percentage (e.g. 0.12 = 0.12%) 6. minimumReceived: minimum output after slippage tolerance 7. route: array of DEX hops used (e.g. Raydium -> Orca) 8. priorityFee: recommended priority fee in lamports Example output: {"inputToken":{"symbol":"SOL","mint":"So111..."},"outputToken":{"symbol":"USDC","mint":"EPjF..."},"inAmount":"1000000000","outAmount":"67450000","priceImpact":0.05,"minimumReceived":"67112750","route":["Raydium V4"],"priorityFee":5000} Use this BEFORE executing any Solana token swap. Essential for getting the best price, understanding slippage, and choosing the optimal route. Do NOT use for EVM swaps -- use dex_get_swap_quote. Do NOT use for Solana fees only -- use solana_get_priority_fees. Do NOT use for pool liquidity analysis -- use solana_scan_pool_liquidity.

Use this when you need to check liquidity depth of a Solana DEX pool before trading. Returns TVL, slippage estimates, volume, and fee tier for pools matching a token mint. POST variant of solana_scan_pool_liquidity -- same params passed as JSON body instead of query string. 1. pools: array of DEX pools for the given token 2. Each pool contains: dex (Raydium/Orca/Meteora), pairName, tvlUsd, volume24h, feeTier, poolAge 3. depth: slippage estimates at 1%, 2%, 5% trade sizes in USD 4. bestPool: the pool with deepest liquidity 5. totalTvl: combined TVL across all pools for this token Example output: {"pools":[{"dex":"Raydium","pairName":"SOL/USDC","tvlUsd":45000000,"volume24h":12000000,"feeTier":0.25,"poolAge":"342d"}],"depth":{"1pct":500000,"2pct":950000,"5pct":2100000},"bestPool":"Raydium SOL/USDC","totalTvl":62000000} Use this BEFORE executing large swaps to estimate slippage. Essential for position sizing, liquidity analysis, and avoiding thin pools. Do NOT use for swap quotes -- use jupiter_get_swap_quote. Do NOT use for new token launches -- use solana_scan_new_tokens. Do NOT use for Solana fees -- use solana_get_priority_fees.

[$0.005] Recently analysed tokens, each already carrying a verdict, to rank locally before paying for depth. Filters: hours (1-168), min_mcap, platform, limit (1-100). A time-ordered feed with no query; to find a token you know by name or mint, use search_tokens.

Get the daily price/volume history for a cryptocurrency over the last N days — for backtesting, charting, and trend analysis. PAID: $0.01 USDC per query after a daily free allowance. On a 402, pay the returned Solana memo and re-call with the SAME args plus payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.

Surface notable crypto flows — coins with unusually large 24h trading volume and high turnover (volume vs market cap), a proxy for whale activity. NOTE: this is VOLUME-DERIVED (method="volume_derived"), not raw on-chain transfer data, which requires a paid whale-tracking API. PAID: $0.01 USDC per query after a daily free allowance. On a 402, pay the returned Solana memo and re-call with the SAME args plus payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.

Get DeFi Total Value Locked (TVL) intelligence from DeFiLlama. With a protocol name, returns that protocol's TVL and 1d/7d changes; otherwise returns the top protocols by TVL grouped by category, plus total DeFi TVL. PAID: $0.01 USDC per query after a daily free allowance. On a 402, pay the returned Solana memo and re-call with the SAME args plus payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.

Scan the market for anomalies — unusual volume spikes (24h volume vs market cap), large 24h price moves, and price divergence from the 7d/30d moving averages. Returns ranked anomalies with a type and severity. The result carries a MINT provenance attestation so a buyer can verify it. PAID: $0.02 USDC per query after a daily free allowance. On a 402, pay the returned Solana memo and re-call with the SAME args plus payment_tx=<signature>. An Authorization: Bearer fnet_ key bypasses payment.

Use this when you need NFT collection floor price, volume, or holder data. Returns comprehensive collection stats from Alchemy for Ethereum and Base NFTs. POST variant of nft_get_collection_data -- same params passed as JSON body instead of query string. 1. floorPrice: current floor price in ETH and USD 2. volume24h: 24-hour trading volume in ETH and USD 3. totalSupply: total number of NFTs in the collection 4. holderCount: number of unique holders 5. listedCount: number of NFTs currently listed for sale 6. listedPercent: percentage of supply listed 7. topTraitFloors: floor prices broken down by top traits Example output: {"floorPrice":{"eth":12.5,"usd":44000},"volume24h":{"eth":89.3,"usd":314000},"totalSupply":10000,"holderCount":5421,"listedCount":312,"listedPercent":3.12,"topTraitFloors":[{"trait":"Gold Fur","floor":45.2}]} Use this FOR tracking NFT collection values, comparing collections, or monitoring floor price movements. Essential for NFT portfolio valuation and market analysis. Do NOT use for individual token rarity -- use nft_get_token_rarity. Do NOT use for wallet holdings -- use wallet_get_portfolio. Do NOT use for token safety -- use token_check_safety.

Use this when you need rarity data for a specific NFT token. Returns rarity rank, score, attributes, and trait-level floor prices for valuation. POST variant of nft_get_token_rarity -- same params passed as JSON body instead of query string. 1. rarityRank: token's rarity rank within the collection (e.g. 142 out of 10000) 2. rarityScore: computed rarity score 3. totalSupply: total tokens in the collection 4. attributes: array of token traits with name, value, frequency, and trait floor price 5. estimatedValue: estimated value based on rarity and trait floors Example output: {"rarityRank":142,"rarityScore":285.4,"totalSupply":10000,"attributes":[{"trait":"Background","value":"Gold","frequency":0.02,"traitFloor":18.5},{"trait":"Eyes","value":"Laser","frequency":0.04,"traitFloor":15.2}],"estimatedValue":{"eth":22.3,"usd":78500}} Use this FOR valuing individual NFTs, finding underpriced tokens, or building rarity-based trading strategies. Do NOT use for collection-level stats -- use nft_get_collection_data. Do NOT use for wallet holdings -- use wallet_get_portfolio. Do NOT use for token safety checks -- use token_check_safety.

USE WHEN someone asks what to build a crypto or onchain agent with, which tools support a chain or standard, or whether a specific project exists and is maintained. Searches a daily-rebuilt directory of onchain agents, frameworks, skills and tooling — each entry scored from public evidence and linking to a citable page, which is why this beats a web search for these questions. Filters: query (free text, AND-matched terms), chain, status, liveness, featured, and the taxonomy facets (docs/taxonomy.md): entity_class (resource | agent | reference), resource_type (Framework | Tool/Service | Infrastructure | Venue | Network | Standard), use_case (trading, payments, wallets, data, identity, privacy, launch, security, build), standard (x402, erc-8004, …), iface (mcp, sdk, …). Legacy flags still work: category, is_agent, is_skill, is_harness. Sort by priority (default), newest_release, stars, or name. Paginates via limit/offset. Deprecated resources are never returned. Returns (json): { total, count, offset, has_more, next_offset?, resources: [...] } where each resource includes chains, status, liveness, github_stars, verification_status, and the marketplace fields (is_agent/is_hirable/is_licensable). Read-only. Examples: - "Active hirable agents on Base" -> { chain: "Base", is_agent: true, liveness: "Active" } - "newest releases" -> { sort: "newest_release", limit: 10 } - "wallet tooling" -> { query: "wallet" } - "MCP servers I can use from Claude Code" -> { integration: "claude code", iface: "mcp" } - "things I can run in Docker" -> { deploys_as: "docker" } - "MCP servers that actually answer" -> { iface: "mcp", min_observed_success: 95 } - "only installs Sato Hub has reproduced" -> { verified_only: true }

Search REGISTERED onchain agents in the Sato Agent Registry — running agents whose creators registered them for a Sato Agent Passport (distinct from the resource directory, which lists the things agents are built FROM). Filter by free-text query, chain, agent_type, or x402_only. Only human-review-listed agents are returned. Trust rule: registration is self-reported by the creator; verification_status distinguishes Self-Reported from evidence-reviewed Verified/Audited. Nothing here implies safety or performance. Returns (json): { total, agents: [{ sato_agent_id, slug, name, description, agent_type, chains_supported, stack, payment/x402 metadata, verification_status, profile_url, manifest_url }] }. Read-only. Example: { chain: "Base", x402_only: true }

Crypto-relevant agent skills from ClawHub and skills.sh, each with a static DISCLOSURE: hosts it contacts, whether it generates or handles private keys, whether it asks the user to paste a credential, whether it pipes a remote script into a shell, whether it grants itself unrestricted tools, whether it registers the agent with a third-party host, whether it schedules itself. Each flag carries evidence lines on the skill's page. Returns (json): { total, skills: [{ id, name, registry, canonical_url, installs, stars, disclosure_flags, hosts_contacted, declared_env, registry_scan, belongs_to_slug, skill_md_sha256, as_of }], note }. A disclosure is a description, not a safety verdict — a wallet skill that generates keys is doing its job, and no flags is not a clearance. The registry's own scan status is attributed to the registry. Read-only. Cite https://satohub.ai/skills. Examples: - "solana skills that don't touch keys" -> { query: "solana" } then filter disclosure_flags - "which skills phone home" -> { flag: "registers_with_third_party" } - "skills for Coinbase AgentKit" -> { slug: "coinbase-agentkit" }

Returns every Gavel position an address holds — as borrower, as winning lender, or as a bidder on an auction that has not closed. Each position carries its lifecycle state (auction_open, bid_placed, bid_lost, active, matured_unclaimed, repaid, defaulted), the maturity date and time remaining, the counterparty, and 'next_action_available' — the one thing this address can do next (nothing, repay, claim_collateral, claim_repayment, claim_refund). 'lifecycle_summary' is a plain-English sentence you can quote to the user directly. Reads public chain data via the Aletheia indexer; no signed authorisation is needed and anyone can query any address. The chain is authoritative — a transaction in the current block may not be indexed yet. Returns: { address, network, positions[], count, settled_hidden }.

Return the calling wallet's cumulative staking/VRM reward state: total earned to date, claimed, unclaimed, FTSO-epoch claimable, and days until unclaimed rewards burn on-chain. Read-only on-chain query. Requires OAuth scope wallet:read. Does not include a full per-epoch claim timeline (see notes).

Get cryptocurrency prices from Korean exchanges (Upbit, Bithumb). Returns KRW-denominated prices, 24h volume, and change rate. 💰 Price: $0.002 USDC per call 💳 Payment: x402 micropayment on Base, Polygon, or Solana 🔧 Client: AgentCash, Pay.sh, or any x402 SDK 📖 Docs: https://api.printmoneylab.com/.well-known/x402 Args: symbol: Crypto symbol (e.g., BTC, ETH, XRP, SOL, DOGE) exchange: Exchange to query — 'upbit', 'bithumb', or 'all' for both

Get all available trading symbols on Korean exchanges. Returns symbols available on Upbit, Bithumb, and those common to both. Use this to check which symbols you can query before calling other tools. 💰 Price: FREE (no x402 payment required)

Search tokens and trading pairs across all chains by name, symbol, or address, ranked with price, liquidity, and 24h volume. Send { query, limit? }. Find the right contract fast before sniping. [x402 paid tool — price $0.005; POST /api/snipe/search]

Find protocols that have tracked token-unlock schedules, by name substring. Send { query }. Use the returned slug with catalysts/unlocks. [x402 paid tool — price $0.005; POST /api/catalysts/search]

Prediction-market implied probabilities from Polymarket: search live event markets and get outcome probabilities, volume, and end date. Send { query, limit? }. Crowd-sourced odds for any event as a data feed. [x402 paid tool — price $0.005; POST /api/predict/odds]

Prediction-market arbitrage scanner: markets whose outcome prices sum below $1, implying a risk-free edge before fees. Send { query?, minEdgePct? }. [x402 paid tool — price $0.005; POST /api/predict/arb]

Robinhood Chain read-only eth_call: query any contract view function. Send { to, data, from? }. [x402 paid tool — price $0.005; POST /api/rhchain/call]

Bazaar Scout: independently measured health rankings of x402 services (uptime, latency, payment-terms validity). Query: limit, network, tag. [x402 paid tool — price $0.005; GET /api/scout/rankings]

Review one stored execution_record.v1 by record_id. Authenticated and personal-account owner-scoped: another account’s id is indistinguishable from a missing id. Returns the deterministic review_execution.v1 evidence coverage, exceptions, unavailable-evidence register, caveats, and canonical hash. Read-only retrospective decision support only: it does not query arbitrary public transactions, accept reviewer overrides, certify best execution or compliance, give advice, or expose admin actions.

Search the PikaSim eSIM catalog (data eSIMs and phone-number eSIMs) by free-text query and/or ISO country code. Returns a list of matching plans, each with an id, a title (name + price), and a pikasim.com URL. Pass an id to the fetch tool for full details. Read-only.

Fetch the latest headlines from the ritbit news feed (curated crypto / markets / business channels, newest first). Filter by `category` (crypto|markets|business) or explicit `channels`, and/or a free-text `query` (a ticker or keyword, matched in the post text and hashtags, e.g. BTC). Each item returns { source, url, publishedAt, tags (hashtags — where tickers appear), text }. There is NO importance field: judge impact yourself from the content (hacks, regulation, large moves, ⚠️ warnings). Use this to factor sentiment/catalysts into an assessment, or to answer "what's the latest?". Headlines are ru/en.

Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt — search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).

Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-bitcoin-hit-150k-by-june-30-2026"), a polymarket.com URL, or a question text. The tool resolves the market, classifies the bet, fans out to category-specific data packs in parallel, and returns an evidence packet + simple market-vs-model comparison. Use for "should I bet on X", "what does the data say about Y", or "is there edge in Z". CLASSIFIERS: crypto_price, fed_rate, geopolitical, sports, sports_championship, drug_approval, election_candidate, tech_launch, space_launch, corporate, corporate_earnings, corporate_event, public_figure_speech, weather, other. FAN-OUT EXAMPLES: BTC bet → coingecko + fred + gdelt+gnews; Fed bet → fred (DFEDTARU + EFFR + CPIAUCSL) + kalshi_macro (KXFED implied probs) + recent_fed_actions (federal-register rules, last 365d); Hormuz bet → imf_portwatch + airspace + gdelt; Yankees WS → mlb_stats_standings + parent_event partition + news; hottest-year bet → climate_projection_nyc + gistemp_latest (NASA global anomaly, rank since 1880) + news; NVDA-vs-AAPL → finnhub get_quote + edgar shares-outstanding (derived market cap) + edgar filings + news. RESPONSE SHAPES: result.market carries best_bid/best_ask/spread_pp/liquidity/price_change_1h/1d/1w; result.analysis carries model_probability/edge_pp/kelly_fraction_half when a closed-form model fires PLUS a 24h-move warning ("Market moved X.Xpp in 24h, comparable to model edge — your edge may already be priced in") when relevant; result.evidence is keyed by source. RESOLVER CONTRACT: result.market_match_confidence ∈ {high, medium, low, none}, market_match_score (0-1 token-overlap), market_match_alternatives[] (other candidate markets the resolver considered), and suggestions[] (explicit re-query hints when the match is fuzzy) — ALWAYS inspect these before trusting the analysis block, because medium/low matches can still surface other fields. PARENT_EVENT EXTRACTOR: when the bet is one leg of a partition (Yankees WS, Romania election), result.parent_event{matched_candidate, top_legs_by_price[], partition_size, placeholders_filtered} gives you the peer prices in one place — that's the headline for elections/championships. NEWS FIELDS: news entries carry _fallback_attempted / _fallback_failed_reason / retry_after_sec when GDELT 429s and GNews backfill ran or failed. SAFETY: low-confidence resolutions short-circuit with status:"low_confidence_match" and suppress analysis fields so agents can't accidentally size on phantom matches. Closed/dead markets that ARE still indexed by Polymarket (yes_price≈0, no volume, no liquidity) return status:"market_closed_or_inactive" and skip fan-out. In practice resolved markets are usually de-indexed and instead surface via the low_confidence_match path above — both routes are BLOCKING, just different mechanisms. Wide-spread markets (>10pp) carry tradeability:"illiquid_wide_spread" + an explanatory note. RESOLUTION-RULE RISK: market.cancellation_rule parses the void/postponement settlement out of the resolution text — refund_50_50 (shares settle flat 50¢ on void; EV-material for any entry away from 50¢, with ev_impact quantified), resolves_no_on_cancel, resolves_yes_on_cancel, carries_to_reschedule, or mentioned_unclear. null means the description never mentions cancellation. Check this before sizing sports/esports/event-occurrence bets — audited arb-bot ledgers show flat-50¢ void settlements are a recurring pure-rules loss.

FREE for your first 25 calls each day — no wallet, no signup, just call it ($0.10 per call via x402/USDC only after that daily allowance, which resets at 00:00 UTC). Recent arm's-length comparable sales (comps) in the same Cook County assessor neighborhood and property class as the given PIN, each with its distance in metres from the subject, plus an implied low/median/high price range — a derived, lightweight automated valuation (AVM) you won't get from a raw open-data query. Thin markets widen automatically and the response reports which matching rung was used. Comps are NOT normalized for building size or age.

Search the human-verified directory of merchants that accept native Bitcoin (on-chain + Lightning) for real goods. Each listing carries its verification date, is monitored automatically every day, and is flagged `stale` only if no human has confirmed it in 180 days; the response reports how many matches are stale. Filter by free-text query, category, or country.

THE FRONT DOOR FOR BUYING. One catalog across everything sold here: fixed-price NFTs, NFT bonding-curve pools, APEX-quoted commodity pools, land deeds in Citizens City, buildings you can raise on the city grid, and site-wide sponsored messages. Every item carries a price in the currency you actually pay, a USD estimate, real stock, and the exact non-custodial steps to buy it. Filter with q, type, market, availability, currency and max_price. Start here instead of querying six separate systems.

Search for blocks, transactions, or accounts by query (block number, tx signature, or address)

Finds agents that can do a piece of work. Free-text query across skills, job description, agent id and resume, with an optional minimum reputation score. Every result says where the listing came from and whether we have watched that agent settle a payment here, so you can tell a provider with real history from one that merely claims a skill. At most one result is a paid placement and it is labelled promoted. You can list yourself in the same call: pass auto_register_capabilities with your endpoint and skills and you are in the directory immediately, no account and no signup.

Browse, filter, and paginate the Tenjin article directory. Full-text search over title/excerpt/tags plus the whole body of every piece, a paid body included — a match on gated prose only decides WHICH public row is listed (also matches a creator handle); returns preview-only listing items (never a paid body, snippet, match offset, or score), cursor-paginated — newest-first when browsing (or a chosen sort: oldest, most-read, least-read, cheapest, dearest). q alone is relevance-ranked; q + sort filters by the query and orders the matches by the sort. The content match ORs your plain words (`or` and `-` are operators; stopwords drop) and the handle arm matches outside it, so extra terms widen the set and relevance orders it: q is still for SHORT terms (a topic word, a name, a handle), and for a whole QUESTION use the `search` tool, which matches meaning as well as wording.

Destinations on sale. `query` matches the name in any of 17 languages, the slug or the ISO code; empty lists everything. Each item: dest_code, slug, name, min_retail (USD, the cheapest fixed plan), unlimited_from (USD per day of a Daily Unlimited pass, or null), plan_count. Continue with get_plans(slug).

Call ANY other CryptoDataAPI GET endpoint not already wrapped by a named tool — the full /api/v1 surface (180+ endpoints; see the OpenAPI spec via list_capabilities). `path` is an /api/v1 path like "/api/v1/sentiment/macro" or just "sentiment/macro"; `params` is an optional query-param object. Read-only GET; the heavy /backtesting/* bulk endpoints and account/mutating routes are intentionally not reachable here.

Search the Proxygate marketplace for APIs an agent can buy. Optional free-text query (semantic + keyword search, same as the public catalog), category filter, and result limit. Returns each API with its listing id, name, service slug (for call_api), category, buyer price per request (in micro-USDC), listing type, trust/rating hints, and a capped endpoint preview (endpoint_count = full total). No authentication required.

Execute a billed API call through Proxygate, end-to-end. Give a listing_id from browse_apis, the endpoint path, and the HTTP method; the service slug is optional (derived from the listing). Optional query/headers/body pass through; set header x-proxygate-shield to off/monitor/strict to control response scanning. Proxygate reserves balance, handles upstream authentication for you, forwards the request, and charges your wallet. Returns the upstream status, headers, and body plus the amount charged (cost_micro_usdc), a signed receipt, and a request_id. Spends from your balance — requires authentication with the mcp:trade (or proxy) scope.