"Rapid" matching MCP tools:

• ios_gamepad_stateA

  Robot Actions — Remote Device ControlB

  Present a REAL game controller to an iOS device and set its state. The device registers a virtual DualShock 4 and receives genuine controller HID, so NATIVE apps see a GCExtendedGamepad and a web page sees a W3C standard-mapping pad in navigator.getGamepads(). It shows up in Settings > General > Game Controller. No Safari page is required. HOW TO FIRE INPUT PROPERLY: • One call = ONE frame = one instant in time. A button stays pressed until you send a frame WITHOUT it, so every press needs a matching release frame — exactly like keydown then keyup. Sending press after press just holds them all down. • For anything that should look played rather than stepped — mashing, combos, a stick sweep — pass `frames` instead of calling repeatedly. The device plays the whole sequence out at `intervalMs` (default 33 ms ≈ 30 fps). A round trip per frame cannot reach that cadence, so a rapid sequence built out of single calls will always read as held buttons. • Alternate press and release inside `frames`: [{buttons:[1]}, {}, {buttons:[0,1]}, {}] is tap A, release, tap A+B, release. • Axes are [leftX, leftY, rightX, rightY], -1..1. Sweep them across frames to roll a stick; omitted axes read as 0. • READ THIS BEFORE REPORTING A STICK BUG: a stick axis can only express RIGHT and UP on `axes[0..1]`, because the report's joystick fields are unsigned. The left stick's full 360-degree analog push IS delivered, but it arrives on the D-PAD — `buttons[12..15]`, and `GCExtendedGamepad.dpad.xAxis/yAxis` for native apps, which are bipolar. Reconstruct it as x = right - left, y = down - up. Pushing left and reading `axes[0] === 0` is the EXPECTED, structural behaviour, not a fault to debug. • While a sequence is playing, this call owns the pad — a controller streamed from a live viewer is paused and resumes on its own shortly after. • Confirm the pad EXISTS with ios_gamepad_status; confirm VALUES in the app under test. Input routes to whatever holds focus, so foreground the app under test first — measuring while Settings or another app is in front reads as "nothing works".

  ConnectorOAuth

• device_gamepad_stateA

  Robot Actions — Remote Device ControlB

  Present a connected game controller to an Android device and set its state. The device sees a REAL controller — a kernel-level input device that native games and apps receive exactly as they would a pad plugged into the phone. HOW TO FIRE INPUT PROPERLY: • One call = ONE frame = one instant in time. A button stays pressed until you send a frame WITHOUT it, so every press needs a matching release frame — keydown then keyup. Press after press just holds them all down. • For anything that should look played rather than stepped — mashing, combos, a stick sweep — pass `frames` instead of calling repeatedly. The sequence plays out device-side at `intervalMs` (default 33 ms ≈ 30 fps). A round trip per frame cannot reach that cadence, so a rapid sequence built from single calls always reads as held buttons. • Alternate press and release inside `frames`: [{buttons:[1]}, {}, {buttons:[1,1]}, {}] is tap A, release, tap A+B, release. • Axes are [leftX, leftY, rightX, rightY], -1..1. Sweep them across frames to roll a stick; omitted axes read as centred. • Confirm with device_gamepad_status. Buttons and axes use W3C standard order, identical to the iOS gamepad tools — the mapping onto whatever the chosen controller reports is done for you. Pick `profile` to match the hardware you want the device to believe is attached; it changes both the reported identity and the button layout, so a game showing on-screen prompts shows the right ones. This is the tool to reach for. device_uhid_gamepad_state is the raw twin — it takes the fixed-format report directly (one profile, rotated bit order) instead of translating from W3C arrays; use it only to send an exact report byte-for-byte.

  ConnectorOAuth

• get_anaf_debtsA

  Companero – Romanian Company DataA

  Keywords: datorii ANAF, restanțe fiscale, obligații restante, tax debts, arieratele, datorii fiscale, conformitate fiscală, ANAF.ro/restante, ANAF debt list, tax compliance, restante, datorii buget stat, asigurări sociale, șomaj, sănătate, beneficial debt, romanian tax debts, fiscal compliance check, debt history quarter. Returnează situația datoriilor fiscale ale unei firme românești după CUI, conform listei publice ANAF de restanțe (publicată trimestrial pe anaf.ro/restante). Două tier-uri (toggle prin `detail`): - `detail: "summary"` (DEFAULT, FREE): răspunde rapid la întrebarea "are firma datorii?" — `{hasDebt, totalGeneral, checkedAtQuarter, checkedAtReferenceDate}`. Folosește pentru screening sau confirmare rapidă. - `detail: "full"` (PAID, 100 credite): istoricul COMPLET multi-trimestru cu breakdown per buget (stat / asigurări sociale / șomaj / sănătate), fiecare cu valori principale / accesorii / total / contestate / necontestate. Folosește pentru evaluări detaliate, due diligence, trend analysis fiscal. IMPORTANT — pragurile de publicare ANAF: lista publică ANAF de restanțe conține DOAR firmele cu datorii fiscale peste anumite plafoane legale: - 100.000 RON pentru firme obișnuite (majoritatea) - 250.000 RON pentru contribuabili mijlocii - 500.000 RON pentru mari contribuabili Absența unei firme din listă NU înseamnă "fără datorii" — înseamnă "datoriile, dacă există, sunt sub pragul de publicare". Stări semantice cheie (interpretează cu atenție): - `hasDebt: true` → firma figurează în lista publică ANAF la trimestrul raportat (datorii peste plafon). Folosește `totalGeneral` și (în tier-ul full) detaliile pe buget. Acest fapt în sine e un semnal serios pentru due diligence. - `hasDebt: false` ȘI `checkedAtQuarter` setat → firma NU apare în lista publică ANAF la trimestrul respectiv. Semnifică "fără datorii publice materiale" — NU "fără datorii deloc". Datoriile sub prag (max 99.999 RON pentru firme obișnuite) pot exista fără să fie publicate. - `hasDebt: null` ȘI `checkedAtQuarter: null` → Companero nu a importat încă date ANAF. Singura stare reală de "informație lipsă". Când îl folosești: - "Are firma X datorii la ANAF?" - "Verifică situația fiscală a firmei cu CUI Y" - "Cât datorează firma Z la stat?" - "Istoricul datoriilor ANAF pentru firma X în ultimele trimestre" - Pre-screening B2B, KYC, factoring, credit decision Cost & caching: free pentru `detail=summary`, 100 credite pentru `detail=full`. Abonamentul Pro include istoricul complet pentru 200 de firme pe lună (lună calendaristică, deduplicat pe firmă): când apelul e acoperit de plafon, răspunsul poartă `_meta.coveredByPlan: true` și `creditsCharged: 0`. Peste plafon, `detail=full` se taxează normal. Datele se actualizează trimestrial când ANAF publică o nouă listă (~aprilie, iulie, octombrie, ianuarie). Confirmarea costului: un apel care ar consuma credite are nevoie de `confirm: true`. Fără el primești DEVIZUL (cost în credite și RON, soldul contului, alternativa gratuită dacă există) și nu se consumă nimic — reia apoi EXACT același apel cu `confirm: true`, după ce omul a acceptat costul.

  ConnectorNo auth

• handoffs.agencyA

  AI Design BlueprintA

  Authenticated: submit an agency engagement enquiry on behalf of the caller for a founder-led discovery call. Persists an AgencyHandoff row routed to the agency inbox; the user is contacted by the team for a scoped proposal. Engagement scopes: workflow sprint (rapid agentic workflow implementation), proof-of-concept (validate a specific agent design in a bounded timeframe), pilot support (co-design and validate a production-ready pilot), advisory (ongoing architectural guidance across a product team). WHEN TO CALL: the user has identified a paid hands-on expert engagement need beyond self-service learning, and explicitly asks to talk to the team or book a discovery call. ALWAYS confirm with the user before firing: this creates a sales-visible record. WHEN NOT TO CALL: for free training / partnerships discussion (use handoffs.partnership); for support / billing / access (use handoffs.operator); proactively or as a sales push. BEHAVIOR: write-only, single insert, side-effecting. Auth: Bearer <token> (any plan). Data at rest in the UK. Response confirms the ticket id + scope so the user can reference it.

  ConnectorNo auth

• handoffs.agencyA

  AI Design Blueprint DoctrineA

  Authenticated: submit an agency engagement enquiry on behalf of the caller for a founder-led discovery call. Persists an AgencyHandoff row routed to the agency inbox; the user is contacted by the team for a scoped proposal. Engagement scopes: workflow sprint (rapid agentic workflow implementation), proof-of-concept (validate a specific agent design in a bounded timeframe), pilot support (co-design and validate a production-ready pilot), advisory (ongoing architectural guidance across a product team). WHEN TO CALL: the user has identified a paid hands-on expert engagement need beyond self-service learning, and explicitly asks to talk to the team or book a discovery call. ALWAYS confirm with the user before firing: this creates a sales-visible record. WHEN NOT TO CALL: for free training / partnerships discussion (use handoffs.partnership); for support / billing / access (use handoffs.operator); proactively or as a sales push. BEHAVIOR: write-only, single insert, side-effecting. Auth: Bearer <token> (any plan). Data at rest in the UK. Response confirms the ticket id + scope so the user can reference it.

  ConnectorNo auth

• sandbox_backtestA

  dMoERA CreatorB

  Run a sandbox backtest of strategy code without persisting anything. This is the fastest way to test a strategy. The code is run through static checks and a full backtest on historical data, but no Strategy or StrategyVersion rows are created. Use this for rapid iteration. Args: code: Python source code implementing the Strategy contract. Must define a METADATA dict and a class extending Strategy with an on_bar(ctx) -> Signal method. See CREATOR_API.md. domain: Trading domain (e.g. "eth_usdc", "btc_usdc", "sol_usdc"). symbol: Price symbol for historical data (e.g. "ETHUSDT"). user_id: Identifier for trial tracking (used for DSR correction). Returns JSON with: success, metrics (sharpe, sortino, win_rate, total_trades, return_bps, max_drawdown, regime_breakdown, exit_reason_breakdown), or error details if validation failed.

  ConnectorNo auth

• rate_responseA

  AlmuredA

  Rate a response on one of your consultations as 'useful' or 'not_useful'; updates within 3 hours overwrite. WHEN TO USE - You are the original asker of a consultation and need to provide quality feedback that compounds into the responder's per-category expertise score. - You want to override an auto-rating produced by ask_consultation's quality heuristic. - You changed your mind within 3 hours of your first rating and want to flip the value. WHEN NOT TO USE - You are not the consultation's asker — only the asker can rate. Other agents must use report_content for moderation issues. - More than 3 hours have passed since your first rating — the value is locked and the call returns a 'rating correction window expired' error. BEHAVIOR - Mutating. Auth required: API key as Authorization: Bearer <key>. Rate-limited to 10 req/min per agent. - Idempotent within the 3-hour correction window: re-posting updates the existing rating, preserves original_value, returns a 'rating updated' confirmation. - Score deltas are not applied at rating time. They are queued and finalized by the maintenance job after the correction window closes — this prevents rapid flips from gaming expertise scores. - Computes scoring inputs at rating time: asker reputation weight, asker tier in the category, rater lifetime count, first-responder window flag (5 min from post). All persisted with the rating. - Triggers post-rating flag detection (rating-pattern anomalies) — best-effort, never blocks the response. - Optional reason (max 280 chars) is displayed publicly next to the rating. WORKFLOW - get_consultation returns response IDs and any existing ratings; pass response_id verbatim. - The 3-hour window prevents reviewer's-remorse manipulation. Decide deliberately. - Unrated responses on your consultations block your next ask_consultation call.

  ConnectorNo auth

• get_company_networkA

  Companero – Romanian Company DataA

  Keywords: grup de firme, firme legate, rețea de firme, conexiuni firmă, company group, related companies, company network, connected companies, administrator comun, asociat comun, shared director, beneficial owner network, firme radiate, istoric administratori, due diligence, KYC, risc de contrapartidă, counterparty risk, verificare partener, legături între firme, afiliați, affiliated companies, group structure, ownership links. Returnează GRUPUL DE FIRME al unei companii românești (după CUI): alte firme conectate prin aceleași persoane (legături prin administratori și, unde sunt cunoscute, prin acționari), împreună cu istoricul factual al fiecărei persoane care leagă firmele: câte firme are în total, câte active, câte radiate, câte cu insolvență, câte cu datorii la stat. Diferență față de profilul individual (`get_company`): acest tool răspunde STRICT la dimensiunea de rețea/grup — cine leagă firma de ce alte firme și ce istoric au acele legături. Pentru profil financiar și bilanțuri folosește `get_financial_health` și `get_balance_sheets`. Două tier-uri (toggle prin `detail`): - `detail: "summary"` (DEFAULT, FREE): `{groupSize, connectorCount, deletedInGroupCount, computedAt}` — răspunde rapid la "face parte firma dintr-un grup și câte dintre firmele grupului sunt radiate?". - `detail: "full"` (PAID, 10 credite): expansiunea completă 2-hop: `connectors[]` (persoanele care leagă firma: nume, roluri, câte firme au în total, statistici — câte active/radiate/cu insolvență/cu datorii ANAF) + `groupMembers[]` (firmele din grup, deduplicate, cu starea lor și prin cine sunt conectate). Semantici cheie (interpretează corect): - Muchiile folosesc DOAR legături cu încredere high/medium din rezoluția de identitate; persoanele cu nume comune neambiguizate sunt EXCLUSE structural — nu presupune niciodată că două firme sunt legate doar pentru că administratorii au același nume. - Practicienii în insolvență (lichidatori, administratori judiciari) NU creează muchii de grup — mandatele lor sunt procedurale. - Persoanele cu foarte multe firme (>50) apar ca `isHub: true` și nu extind grupul. - Cifrele sunt fapte publice ONRC (mandate, radieri, date), nu aprecieri. O firmă radiată în istoricul unui administrator NU e, prin ea însăși, un semnal negativ: radierea voluntară e obișnuită. Absența datelor de datorii pentru firme radiate demult NU înseamnă că erau curate. - Corelarea acestor fapte într-un tipar de comportament (persoane cu firme radiate care înregistrează firme noi) NU e expusă prin acest tool și nu apare în răspuns; e o prelucrare pentru care așteptăm evaluarea de impact (DPIA, art. 35 GDPR). Nu o deduce singur din cifre și nu o prezenta utilizatorului ca pe un rezultat al platformei. - `computed: false` → rebuild-ul de rețea nu a rulat încă pentru acest set de date. Când îl folosești: - "Ce alte firme are administratorul firmei X?" / "Firme legate de X" - "Face parte firma X dintr-un grup de firme?" - "Are firma X administratori cu firme radiate în urmă?" - "Verifică istoricul oamenilor din spatele firmei X" (KYC, credit, contract nou, factoring) Cost: free pentru `detail=summary`, 10 credite pentru `detail=full`. Datele se recalculează după fiecare import ONRC lunar. Confirmarea costului: un apel care ar consuma credite are nevoie de `confirm: true`. Fără el primești DEVIZUL (cost în credite și RON, soldul contului, alternativa gratuită dacă există) și nu se consumă nimic — reia apoi EXACT același apel cu `confirm: true`, după ce omul a acceptat costul.

  ConnectorNo auth

• get_company_contractsA

  Companero – Romanian Company DataA

  Keywords: achiziții publice, licitații, contracte de stat, SEAP, SICAP, furnizor stat, achiziție directă, acord-cadru, contracte câștigate, bani publici, public procurement, public contracts, tenders, government contracts, awarded contracts, supplier to public sector, CPV, dependență de stat, due diligence achiziții, e-licitatie. Returnează implicarea unei firme românești (după CUI) în achizițiile publice, conform datelor deschise SEAP/SICAP (data.gov.ro). Vizează firma în rol de FURNIZOR (ofertant câștigător). Două tier-uri (toggle prin `detail`): - `detail: "summary"` (DEFAULT, FREE): rollup rapid — `{hasPublicContracts, contractCount, contractValue, frameworkValue, distinctAuthorities, lastAwardDate, topCpvCodes}`. Răspunde la "câștigă firma contracte publice și cât?". - `detail: "full"` (PAID, 2 credite): summary + lista contractelor recente (autoritate contractantă, CPV, valoare, tip procedură, dată) + `stateShare` — „dependența de stat": seria anuală valoare-contracte ÷ cifră de afaceri (sharePct poate depăși 100% legitim — contract multianual semnat într-un an; sharePctDisplay e plafonat la 100). Pentru due diligence detaliat și analiza dependenței de bani publici. IMPORTANT — acord-cadru vs contract: `contractValue` însumează DOAR contractele obișnuite. Acordurile-cadru repetă valoarea totală pe fiecare lot, deci sunt ținute separat în `frameworkValue` (limită superioară de capacitate, NU cheltuială efectivă). Nu le aduna. Ce spune fiecare câmp (fapte, nu verdicte — nu le transforma în concluzii despre firmă): - `distinctAuthorities` = câte autorități contractante distincte apar în contractele firmei. Mai multe autorități pe un `contractValue` mare = venituri publice împrăștiate pe mai mulți clienți; `distinctAuthorities: 1` pe un `contractValue` mare = toate veniturile publice vin de la un singur client public. Atât — raportează numărul și autoritatea, nu explicația. - `lastAwardDate` raportat la data de înregistrare a firmei = de cât timp exista firma la ultima atribuire. E un fapt datat, nu un semnal: spune intervalul, cu ambele date, și lasă concluzia utilizatorului. - `hasPublicContracts: false` → fără contracte publice cunoscute în datele importate (NU garanție că n-a avut niciodată). Când îl folosești: - "Ce contracte publice a câștigat firma X?" - "Câștigă firma Y bani de la stat?" - "Cât a luat firma Z din achiziții publice și de la cine?" - "În ce domenii (CPV) furnizează firma X către instituții publice?" - Due diligence, KYC, evaluare dependență de bani publici. Sursă: open-data SEAP/SICAP (data.gov.ro), licență deschisă. Date despre persoane juridice și cheltuieli publice (transparență — fără date personale). Confirmarea costului: un apel care ar consuma credite are nevoie de `confirm: true`. Fără el primești DEVIZUL (cost în credite și RON, soldul contului, alternativa gratuită dacă există) și nu se consumă nimic — reia apoi EXACT același apel cu `confirm: true`, după ce omul a acceptat costul.

  ConnectorNo auth

• raidA

  DaishiA

  OPTIONAL violence against property. Smash a structure in your region (not your own): costs 8 energy, deals 25 hp damage. If it crumbles you salvage 50% of its build materials from the rubble (floored per item, limited by carry space), and a storehouse's contents additionally spill to you (the rest is lost). Raises your PUBLIC aggression counter. Owners can repair_structure to defend.

  ConnectorNo auth

• check_index_statusA

  Rapid Indexer

  Create an index-check task that reports, per URL, whether Google currently has it in the index (indexed / unindexed). Cheap (~0.1 credit per URL) but still SPENDS CREDITS. Results arrive within a few minutes: poll get_task, then read get_task_links. Does not submit anything to Google; use submit_urls_for_indexing for that.

  ConnectorNo auth

• datagovmy_get_transit_stopsA

  hithereiamaliff-mcp-datagovmyB

  Get transit stops from GTFS data. IMPORTANT: For transit stop queries like "Show me bus stops for Rapid Penang", use this tool directly with the provider name. The tool supports common names like "rapid penang", "rapid kuantan", "ktmb", or "mybas johor" which will be automatically mapped to the correct provider and category. No need to use list_transport_agencies first.

  ConnectorOAuth

• get_gas_priceA

  TeardropA

  Get current EIP-1559 gas fees on Ethereum or Base: base fee, priority fee, next-block base fee estimate, and congestion (gas_used_ratio >0.5 busy, >0.9 very congested). Optional USD estimates cover a simple transfer and a swap-like transaction. Cached 10 seconds per chain. Use when: Use before advising a transaction — to time execution, size a gas budget, or judge congestion. Call once per decision; the 10-second cache makes rapid re-calls pointless. Limitations: Point-in-time estimate that changes every block; USD figures are rough heuristics at 21k/150k gas, not an execution quote. Ethereum mainnet and Base only. Alternatives: get_block, get_dex_quote

  ConnectorNo auth

• get_market_moversA

  kr-crypto-intelligenceA

  Get Korean market movers: 1-minute price surges/crashes (>1%), volume spikes, and top 20 tokens by trading volume on Upbit. Detects rapid price movements and unusual volume activity in Korean crypto markets. Korean retail activity often leads global price movements — early signal for traders. 💰 Price: $0.01 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

  ConnectorNo auth

• get_temperatures_cuissonA

  frigolog-haccp-mcpA

  Retourne les températures à cœur réglementaires obligatoires en cuisson par type d'aliment en restauration française (GBPH Restaurateur DGAL) : volaille 74 °C, bœuf haché 70 °C, porc 70 °C, poisson 63 °C, etc. Inclut le refroidissement rapide (de +63 °C à +10 °C en moins de 2 heures), la remise en température à +63 °C minimum et les recommandations de sécurité spécifiques aux populations sensibles (enfants, femmes enceintes, immunodéprimés). Distinct des températures de conservation disponibles via get_haccp_temperatures. [EN] Returns mandatory core cooking temperatures by food type in French catering (poultry 74°C, minced beef 70°C, fish 63°C…) plus rapid cooling and reheating rules. Optional 'type_aliment'.

  ConnectorNo auth

• get_temperatures_cuissonA

  Frigolog HACCP — French Food Safety ComplianceA

  Retourne les températures à cœur réglementaires obligatoires en cuisson par type d'aliment en restauration française (GBPH Restaurateur DGAL) : volaille 74 °C, bœuf haché 70 °C, porc 70 °C, poisson 63 °C, etc. Inclut le refroidissement rapide (de +63 °C à +10 °C en moins de 2 heures), la remise en température à +63 °C minimum et les recommandations de sécurité spécifiques aux populations sensibles (enfants, femmes enceintes, immunodéprimés). Distinct des températures de conservation disponibles via get_haccp_temperatures. [EN] Returns mandatory core cooking temperatures by food type in French catering (poultry 74°C, minced beef 70°C, fish 63°C…) plus rapid cooling and reheating rules. Optional 'type_aliment'.

  ConnectorNo auth

• get_crypto_moversA

  CoinRithm Agent TradingA

  Free public scan of CoinRithm's tracked crypto universe for the biggest 24h price moves — top gainers or top losers, ordered by 24h change percent. Use this to DISCOVER candidates beyond your watchlist (abnormal rapid moves), then deep-analyze each candidate with get_candles (OHLC + indicators), get_market_context (sentiment, related markets) and get_news before any trade decision. Rows carry coinId, symbol, name, slug, change24hPct and priceUsd; data refreshes on the ~60s core price tick. Pass the row's coinId straight to get_candles / get_market_context — do NOT re-resolve it from the symbol, since symbols collide across listings. No API key required.

  ConnectorNo auth

• get_crypto_moversA

  CoinRithm Agent TradingA

  Free public scan of CoinRithm's tracked crypto universe for the biggest 24h price moves — top gainers or top losers, ordered by 24h change percent. Use this to DISCOVER candidates beyond your watchlist (abnormal rapid moves), then deep-analyze each candidate with get_candles (OHLC + indicators), get_market_context (sentiment, related markets) and get_news before any trade decision. Rows carry coinId, symbol, name, slug, change24hPct and priceUsd; data refreshes on the ~60s core price tick. Pass the row's coinId straight to get_candles / get_market_context — do NOT re-resolve it from the symbol, since symbols collide across listings. No API key required.

  ConnectorNo auth

• cheapest_charging_along_routeA

  MapMapA

  Find the best EV charge points along a route, with the REAL extra travel time of stopping at each one — never a straight-line guess. Provide `origin` + `destination` (a route is computed) or an existing route's `geometry_polyline6`, plus optional `connectors` ("ccs", "type2", "chademo", "type1", "tesla", "domestic", "other"), `min_kw` (e.g. 50 for rapid only), `available_only` and `max_detour_minutes` (default 10). Charge points come from operator-published feeds, are costed through the routing engine with your costing (a `truck` profile makes detours respect dimensional/ADR restrictions) and ranked most powerful first, since minutes off the clock are bought with kilowatts. Each result carries max_power_kw, connector_standards, best_connector, evse_count, detour_minutes/detour_km and, where a live feed backs it, available_now. IMPORTANT: there is no national charge-point registry — every deployment covers only the operators it has onboarded, so ALWAYS show the returned `coverage_note` alongside the results. An empty `results` means "none from these operators within the detour budget", NEVER "there are no chargers here". Statuses are live only when availability_live is true; otherwise they are the values captured at the last ingest and must not be described as current. `say` is ALWAYS present and is the whole answer as one short spoken line, composed by the gateway with the coverage already inside the claim rather than appended to it: it scopes its superlative to the operators this deployment holds, and an empty result's line says the emptiness is about those operators. Prefer reading it verbatim to writing your own summary. Requires the MapMap gateway; answers a clear error when the deployment has no charge-point dataset. Display the returned charging_attribution with the results.

  ConnectorNo auth

• verify_custom_domainA

  TessryxA

  Check the DNS TXT challenge for a claimed domain and, on success, take the global (hostname -> tenant) binding and start certificate issuance. Call this ONCE after the human confirms they have added the DNS records from create_custom_domain. DNS can take minutes to propagate, so do NOT poll this in a loop — if verified is false, tell the human it may take a few minutes and check back later (the server throttles rapid re-checks). Read get_custom_domain to watch the certificate go from CERT_PENDING to ACTIVE. First-to-verify wins: verifying is what actually claims the hostname.

  Connector

  Destructive

  OAuth

• preview_capabilityA

  Rafid Intelligence NetworkC

  Free preview of a paid capability: checks whether useful data/analysis is available for a given input, before paying — proof of "I have information for this request," never the paid analysis itself. No payment, charge or account is ever involved. Not every capability supports preview (status is "unavailable" when it doesn't). Recommended flow: discover -> preview -> evaluate -> pay -> execute.

  ConnectorNo auth