"author:fjgg007-bit" matching MCP tools:

• analyze_business_vertical

  agent-ready-kit

  Use this immediately after scan_site to give the user a 'what this means for my business' framing. Detects the site's business vertical (auto dealership, law firm, healthcare, home services, ecommerce, digital agency, etc.) from JSON-LD schema + scraped text. Returns expected AI-search lift %, current competitor adoption %, and a positioning pitch tailored to the vertical. **If `should_ask_user` is true, the detection is low-confidence — ASK THE USER what category their business is in before continuing, rather than acting on the guessed vertical.** Also returns the site title and meta description so the calling agent can render a Site Summary card.

  Connector

• read_datasheet

  sheetsdata-mcp

  Read from a component's datasheet. Two modes: **Section mode** (default): Returns a named section. Start with section='summary' to get an overview and a list of available_sections. Then request specific sections by name. Section names are dynamic — any heading in the actual datasheet works (e.g. 'register_map', 'i2c_interface', 'power_management'). If a section name isn't found, automatically falls back to search mode. **Search mode**: Semantic search within the part's datasheet. Best for targeted questions (register bit fields, I2C config, specific specs). Use when you need to find specific information rather than a whole section. First call for a new part triggers extraction (30s-2min). Subsequent calls are cached. **Datasheet vs Reference Manual**: Manufacturer datasheets cover high-level specs, pinout, absolute maximum ratings, and package info. For microcontrollers (STM32, nRF52, RP2040), register-level programming details (I2C CR1/CR2, DMA config, interrupt bits) are in a separate Reference Manual, not the datasheet. The summary's available_sections will show what's actually present. The part_number must be a specific manufacturer part number (e.g. 'TPS54302', 'STM32F446RCT6') or LCSC number (e.g. 'C2837938'). Do NOT pass bare component values ('100nF', '10K'), descriptions, or reference designators. DATASHEET STATUS VALUES: - 'ready' — extracted and indexed; call read_datasheet, search_datasheets, or analyze_image. - 'extracting' / 'in_progress' / 'queued' / 'pending' — extraction running or scheduled. Poll check_extraction_status every 5-10s until 'ready' or 'failed'. Typical time: 30s-2min. - 'not_extracted' — known part but datasheet hasn't been fetched yet. Trigger it via prefetch_datasheets (cheapest) or by calling read_datasheet (auto-triggers on first read). - 'no_source' — we couldn't find a public datasheet URL for this MPN. First, retry prefetch_datasheets in 10-30s (the URL resolver re-runs and often finds a source on the second pass). If still 'no_source', the agent can upload the PDF manually via request_datasheet_upload + confirm_datasheet_upload (see those tools). Org-uploaded datasheets are private to the org. - 'unsupported' — PDF exists but can't be extracted (scanned image-only, encrypted, or corrupted). Upload a clean text-based PDF via request_datasheet_upload to override. - 'failed' / 'error' — extraction errored. The response includes the error reason. Retry via prefetch_datasheets or escalate to support. - 'rejected' — input wasn't a real MPN (bare value like '100nF', description, or reference designator). Fix the input and re-call. - 'deduplicated' — another part in the family already has this datasheet; same content is returned under the primary MPN.

  Connector

• asset_lookup

  RedM Mcp

  Resolve a RedM game-data asset (ped model, weapon, object, door, vehicle) by exact name, 32-bit hash, or partial-name search. O(1) structured lookup against pre-parsed discoveries tables — replaces the common workflow of grepping `a_c_bear_01` in peds_list.lua, then cross-referencing RELATIONSHIP/README.md for its relationship group. Returns: type, name, normalized hash (`0x` + 8 uppercase hex), source file + line, plus type-specific metadata (peds get `variants` + `relationship`, weapons get `group`, doors get `coords` + `model_hash`, objects get `category`/`subcategory`). Catalog ~22,500 entries (mostly objects). Typical latency p50 ~15ms, p95 ~65ms. NOT for: - **Script natives** like `SET_ENTITY_COORDS`, `GetPedHealth`, or hashes from `Citizen.InvokeNative(0x...)` — use `lookup_native`. Native hashes are 64-bit (`0x06843DA7060A026B`); asset hashes are 32-bit (`0xBCFD0E7F`). Different namespaces, never collide. - **Flag enums, settings, clipsets, scenario keys** like `CPED_CONFIG_FLAGS`, `MP_Style_Casual`, `mech_loco_m@`, `MAGGIE_SEAT_CHAIR_DESK_WRITING`. Those live as tokens in lua source but not in this catalog. Use `grep_docs`. - **Behavior queries** ("which animal is the bear", "weapons in the lemat family") — use `semantic_search`. Pass exactly ONE of `name` / `hash` / `search`. Optional `type` narrows to a category (useful when a fragment like "horse" hits both peds and vehicles). Note: `type` reflects the SOURCE FILE — the same asset name can exist under multiple `type`s. e.g. `mp006_p_mshine_int_door01x` appears as `type=object` (1 row from object_list.lua) AND `type=door` (2 rows from doorhashes.lua, different door hashes for distinct in-world instances with `coords`). Pick `type=door` when you want lockable in-world doors with positions; `type=object` for the model itself. Examples: - `{name: "a_c_bear_01"}` → exact ped lookup, returns variants=11 + relationship=REL_WILD_ANIMAL_PREDATOR. - `{hash: "0xBCFD0E7F"}` → resolves to ped `a_c_bear_01` (omit `0x` ok). - `{search: "lemat", type: "weapon"}` → substring match → `weapon_revolver_lemat`. - `{search: "moonshine", type: "door"}` → exact substring misses (no door name contains "moonshine"), fuzzy trigram fallback fires → `mp006_p_mshine_int_door01x`. Fuzzy mainly fires when `type` narrows out the exact-substring matches; without `type`, common terms find substring hits first and never reach fuzzy.

  Connector

• asset_lookup

  redm-mcp

  Resolve a RedM game-data asset (ped model, weapon, object, door, vehicle) by exact name, 32-bit hash, or partial-name search. O(1) structured lookup against pre-parsed discoveries tables — replaces the common workflow of grepping `a_c_bear_01` in peds_list.lua, then cross-referencing RELATIONSHIP/README.md for its relationship group. Returns: type, name, normalized hash (`0x` + 8 uppercase hex), source file + line, plus type-specific metadata (peds get `variants` + `relationship`, weapons get `group`, doors get `coords` + `model_hash`, objects get `category`/`subcategory`). Catalog ~22,500 entries (mostly objects). Typical latency p50 ~15ms, p95 ~65ms. NOT for: - **Script natives** like `SET_ENTITY_COORDS`, `GetPedHealth`, or hashes from `Citizen.InvokeNative(0x...)` — use `lookup_native`. Native hashes are 64-bit (`0x06843DA7060A026B`); asset hashes are 32-bit (`0xBCFD0E7F`). Different namespaces, never collide. - **Flag enums, settings, clipsets, scenario keys** like `CPED_CONFIG_FLAGS`, `MP_Style_Casual`, `mech_loco_m@`, `MAGGIE_SEAT_CHAIR_DESK_WRITING`. Those live as tokens in lua source but not in this catalog. Use `grep_docs`. - **Behavior queries** ("which animal is the bear", "weapons in the lemat family") — use `semantic_search`. Pass exactly ONE of `name` / `hash` / `search`. Optional `type` narrows to a category (useful when a fragment like "horse" hits both peds and vehicles). Note: `type` reflects the SOURCE FILE — the same asset name can exist under multiple `type`s. e.g. `mp006_p_mshine_int_door01x` appears as `type=object` (1 row from object_list.lua) AND `type=door` (2 rows from doorhashes.lua, different door hashes for distinct in-world instances with `coords`). Pick `type=door` when you want lockable in-world doors with positions; `type=object` for the model itself. Examples: - `{name: "a_c_bear_01"}` → exact ped lookup, returns variants=11 + relationship=REL_WILD_ANIMAL_PREDATOR. - `{hash: "0xBCFD0E7F"}` → resolves to ped `a_c_bear_01` (omit `0x` ok). - `{search: "lemat", type: "weapon"}` → substring match → `weapon_revolver_lemat`. - `{search: "moonshine", type: "door"}` → exact substring misses (no door name contains "moonshine"), fuzzy trigram fallback fires → `mp006_p_mshine_int_door01x`. Fuzzy mainly fires when `type` narrows out the exact-substring matches; without `type`, common terms find substring hits first and never reach fuzzy.

  Connector

• bet_research

  Tinder Bio

  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.

  Connector

• polymarket_arbitrage

  Bis

  Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `event` (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partition_check (sum of YES prices across mutually-exclusive legs — should ≈1; deviations >3pp emit a BUY/SELL EVERY LEG signal). `topic` (for cross-event scanning): pass a seed question like "Strait of Hormuz traffic returns to normal" or "Fed rate decision"; searches related events across the platform, flattens markets, runs the comparator on the union. Cross-event mode catches "...by May 31" vs "...by Jun 30" patterns that single-event misses. SEMANTIC ANCHOR: cross-event pairs require ≥0.30 Jaccard similarity on question tokens (prevents Powell-Fed-Pause being paired with Powell-DOJ-probe); skipped_low_similarity surfaces the rejected pair count. PARTITION FILTER: drops will-person-X / will-manager-Y / will-someone-else- placeholder slugs; partitions with >20% placeholder fraction return null arb signal. Response: opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context), and in event mode partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}. FILL CHECK: when the partition signal fires, arbitrage.fill_check prices it against live CLOB depth (theoretical_edge_pp_at_book vs realizable_edge_pp at 1000 shares/leg, thin_legs[]) — realizable_edge_pp ≤ 0 means the overround exists only at last-trade, not in the book; do not trade it. For custom sizing use polymarket_fill_risk.

  Connector

• polymarket_arbitrage

  Dati It

  Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `event` (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partition_check (sum of YES prices across mutually-exclusive legs — should ≈1; deviations >3pp emit a BUY/SELL EVERY LEG signal). `topic` (for cross-event scanning): pass a seed question like "Strait of Hormuz traffic returns to normal" or "Fed rate decision"; searches related events across the platform, flattens markets, runs the comparator on the union. Cross-event mode catches "...by May 31" vs "...by Jun 30" patterns that single-event misses. SEMANTIC ANCHOR: cross-event pairs require ≥0.30 Jaccard similarity on question tokens (prevents Powell-Fed-Pause being paired with Powell-DOJ-probe); skipped_low_similarity surfaces the rejected pair count. PARTITION FILTER: drops will-person-X / will-manager-Y / will-someone-else- placeholder slugs; partitions with >20% placeholder fraction return null arb signal. Response: opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context), and in event mode partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}. FILL CHECK: when the partition signal fires, arbitrage.fill_check prices it against live CLOB depth (theoretical_edge_pp_at_book vs realizable_edge_pp at 1000 shares/leg, thin_legs[]) — realizable_edge_pp ≤ 0 means the overround exists only at last-trade, not in the book; do not trade it. For custom sizing use polymarket_fill_risk.

  Connector

• search_within

  Tinder Bio

  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).

  Connector

• deep_research

  Dati It

  ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1320 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 5,016 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx — it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass — so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri (record-level pipeworx:// when the source emits one, else source-level). "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).

  Connector

• deep_research

  Tinder Bio

  ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1320 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 5,016 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx — it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass — so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri (record-level pipeworx:// when the source emits one, else source-level). "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).

  Connector

• deep_research

  Istat It

  ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1320 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call — this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 5,016 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx — it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass — so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri (record-level pipeworx:// when the source emits one, else source-level). "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).

  Connector

• polymarket_fill_risk

  Dati It

  Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, and a verdict (clean|degraded|cannot_fill). BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio, profit_usd at executed size, per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L).

  Connector

• polymarket_fill_risk

  Tinder Bio

  Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, and a verdict (clean|degraded|cannot_fill). BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio, profit_usd at executed size, per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L).

  Connector

• polymarket_fill_risk

  Istat It

  Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, and a verdict (clean|degraded|cannot_fill). BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio, profit_usd at executed size, per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L).

  Connector

• polymarket_fill_risk

  Bis

  Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, and a verdict (clean|degraded|cannot_fill). BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio, profit_usd at executed size, per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L).

  Connector

• deploy_app

  mcp

  Deploys an app to a VM and exposes it at a public https://<name>-<id>.redu.cloud URL (a random 8-char suffix is appended to <name> for uniqueness — a BARE custom `dname` like `myapp.redu.cloud` ALSO gets a suffix, so to PIN a known URL pass a dname that already includes an 8-char suffix like `myapp-7k2m9x4p.redu.cloud` and wire the app's own URL env to it; single-surface apps can instead just read the injected PUBLIC_URL/APP_URL). The container is built ON the VM — no local Docker/podman needed. PREREQS — run check_deploy_prerequisites first: it auto-selects your network_id + keypair_name (and returns a recipe to mint a keypair if you have none). Pass those two ids here. PORT: pass the port the app actually listens on (plan_deploy detects it / Dockerfile EXPOSE) — redu health-probes that exact port, so a wrong/omitted port (defaults to 3000) fails a non-3000 app (e.g. a static nginx app listens on 80 → pass 80). TWO source modes: (1) GIT — pass `repo` (public; private repos also need git_token). (2) UPLOAD — call prepare_upload first to tar + POST your LOCAL working dir, then pass the returned `source_token` (no git, no PAT; use this for uncommitted code, a fixed clone of a repo you don't own, or private code). The source needs a Containerfile/Dockerfile; redu auto-finds one in common subfolders (Docker/, scripts/, packaging/…) and builds with the repo root as context — for a repo with MULTIPLE Dockerfiles pass `dockerfile`+`context` to pick the right one. If it has NONE, pass dockerfile_content (the one plan_deploy generated) or include a Dockerfile in the uploaded tarball. To wire a DB, pass `database` (auto-injects the connection env + DATABASE_URL — zero setup): `database:'single_vm'` puts Postgres ON the app VM (cheapest; data dies if the VM is replaced); `database:'managed'` provisions a SEPARATE managed-DB VM on the same private network and wires it automatically (data PERSISTS across redeploys; reused on a same-name redeploy) — you do NOT call create_database/create_relational_database for this. Choose the engine with `db_engine` ('postgres' default → PG* env; 'mysql'/'mariadb' → MYSQL_* env + mysql:// URL, for WordPress/Matomo/LAMP apps; mysql/mariadb require database:'managed'). redu also injects APP_URL/PUBLIC_URL (= the app's public URL) into its env, so apps that need their own URL get it (map an app-specific var like BASE_URL to PUBLIC_URL if needed). Build+provision takes ~3-6 min (a bit longer for managed, which also brings up the DB VM); poll list_deployments or get_deployment until status='ready'. On 'build_failed'/'error', call get_deployment(id) to read build_log. ALWAYS run plan_deploy first and confirm the plan + cost with the user before deploying.

  Connector

• faa_lookup_registration

  faa-aircraft-registry-mcp-server

  Decode one US civil aircraft N-number to its full registration record — aircraft make/model, engine, year manufactured, airworthiness, registration status, Mode S (ICAO 24-bit) code, and registered owner (when owner-PII redaction is off). One call resolves the relational join and decodes every coded field. Accepts "N12345" or "12345" (the leading N is optional). Returns ownerRedacted: true when owner details were withheld. A number that is known but inactive (deregistered or reserved) is not found here — use faa_get_registration_status for the cross-file status answer.

  Connector

• compute

  Drillable

  A deterministic AGGREGATE over ONE corpus's COMPLETE set — the calculated-query shape ("how many X", "break X down by Y", "which is most common"). Requires `domain`; optional `filter` scopes the set (e.g. {"spirit":"gin"}); optional `by` (a record field) returns the count PER value, sorted, with the largest. Built ON `enumerate`, so it inherits the completeness contract: over an INCOMPLETE set it ABSTAINS rather than undercount. It counts on GROUND and refuses to crown a "best"/worth ranking (that has no oracle — the user's call). For the records/categories themselves use `enumerate`. Mounted corpora: calendar, building-codes, gearing, colorimetry, first-aid, tuning, wire-gauge, preferred-numbers, strength-training, unix-permissions, number-bases, cognitive-psychology, braille, semver, cron, unicode, timezones, metar, glob, ieee754, http-status, uuid, base-encodings, percent-encoding, dms-coordinates, gray-code, hashing, classical-ciphers, hamming-code, geohash, mac-address, poker-hands, capacitor-codes, iso-duration, dice-probability, scrabble-score, mach-number, chords, dtmf, base85, theoretical-ecology, checksums, bloom-filter, search-heuristics, solar-times, blood-alcohol, maidenhead-locator, brewing, celestial-navigation, electrochemistry, structural-mechanics, regex, psychrometrics, photographic-exposure, photometry, rf-link, screen-resolution, color-names, type-sizes, vin, drill-bit-sizing, iso-country-codes, itu-e164, mime-types, finite-automata, ac-circuits, currency-codes, elliptic-curves, queueing-theory, totp-hotp, computational-geometry, crockford-base32, iana-port-numbers, acoustics, magnetism, hydrostatics, gas-laws, blackbody-radiation, antenna-gain, bcp47, dimensionless-numbers, iso-language-codes, dns-record-types, midi-messages, kinematics, digital-logic, clothing-sizes, knitting-needle-gauge, pipe-size, winemaking-math, ansi-escape-codes, radiation-dosimetry, transmission-lines, cribbage-scoring, running-pace, dnd-math, bowling-scoring, tire-size, abn-acn, sedol-cusip, damm-verhoeff, iso-6346, iso-7064, hydrogen-spectrum, material-elasticity, pump-affinity, control-theory, em-plane-waves, ordinary-differential-equations, posix-signals-reference, quaternions-reference, origami-flat-foldability-theorems, trailer-hitch-ball-coupler-classes, bayesian-inference, issn-check, ean-barcode, iana-uri-schemes, aquarium-chemistry, iso-thread, knitting-needle-sizes, bearing-sizes, horology, rocket-propulsion, rolling-element-bearing-life, iec-60320, sae-viscosity, hat-sizes, darts-scoring, complex-numbers, lambda-calculus, combustion-stoichiometry, ham-radio-bands, miniature-scale, fracture-mechanics, torsion, catenary, open-channel-hydraulics, gaussian-beam-optics, nato-phonetic, lei, fen-pgn, nmea-0183, phonetic-algorithms, lumber-grades-dimensions, film-speed-iso, telescope-optics, tabletop-rpg-probability, z-transform, generating-functions, terzaghi-bearing-capacity, icao-doc8643, imei-reference, gs1-ai, ulid, postal-barcodes, photographic-paper-sizes, fishing-line-ratings, sorting-algorithms, candle-making, pool-billiards-geometry, sourdough-ratios, electromagnetic-induction, probability-distributions, isentropic-flow, fatigue-life, ghs-hazard, abrasive-grit-sizes, cycling-power-zones, dynamic-programming-recurrences, smtp-reply-codes, un-locode, chain-pitch, string-gauges, sewing-pattern-grading, aquaculture-stocking-density, polynomial-arithmetic, nhs-number, diode-junction, elastic-collisions, pressure-vessel, reverberation-time, ieee-ethertypes, icao-mrz, http-methods, tls-alerts, bwt-mtf, bicycle-wheel-sizing, silk-thread-nm-denier, soapmaking-lye, iso-3166-2, context-free-grammars, dc-motor-equations, usb-class-codes, film-frame-rates, aperture-f-stop-series, golf-handicap, hydroponics-nutrients, sewing-fabric-math, resin-mixing-ratios, pdf-structure, piping-water-hammer, hertzian-contact-stress, photovoltaic-cell-performance, un-ece-vegetable-fruit-grading-standards, iata-airport-delay-codes, un-transport-hazard-class-un-numbers, faa-nas-airspace-classes, sieve-mesh-sizing, disc-golf-flight-numbers, beekeeping-hive-math, vinyl-record-cutting-specs, houseplant-light-and-watering-calc, cellular-automata-rules, error-correcting-codes-beyond-block, climbing-rope-and-anchor-ratings, knot-invariants, fiber-dispersion, osmotic-pressure-solutions, naics-sic-classification, isni-checksum, shotgun-gauge-and-choke, rope-cordage-strength-and-diameter, screen-mesh-count-and-particle-sizing, battery-cell-form-factor-codes, xor-filter, kite-line-and-wind-window, clothing-glove-size-standards, wasm-module-header, protobuf-wire-format, rankine-cycle-efficiency, aes-fips-block-parameters, voronoi-delaunay, np-completeness-reductions, hidden-markov-viterbi, png-ihdr-fields, mbr-partition-table, fuzzywuzzy-rapidfuzz-string-similarity-api-reference, v-belt-sprocket-sizing, e164-carrier-mnc-mcc, faa-nav-aid-frequency-bands, go-baduk-scoring, zip-central-directory-header, curling-scoring, mahjong-hand-scoring, sudoku-difficulty-rating, dominoes-scoring, base45, pbkdf2, hkdf, hvac-duct-sizing, board-game-elo-scoring, tide-and-moon-phase-almanac, obd2-pids, emission-designators, runway-designators, qr-code, iban-structure, sewing-needle, experiment-design, iana-link-relations, crystallography, png-chunk-type, wind-turbine-aerodynamics, rf-noise-and-link-budget, icd-10-cm, un-sdg-indicator-framework, iso-20022-message-types, world-heritage-list-criteria, german-tax-id-checksum, hydraulic-hose-fitting-sizing, spectacle-frame-and-lens-sizing, beer-lambert-spectrophotometry, induction-motor-slip-torque, corrosion-rate-faraday, seebeck-thermoelectric-generation, viscosity-shear-rheology, imo-ship-number, itu-callsign-allocation, alcohol-proof-abv, code128-code39-barcode-checksum, usp-suture-sizing, precious-metal-fineness, hop-alpha-acid-ibu, guitar-fret-spacing, juggling-siteswap, knots, leathercraft-stitch-and-skiving, data-structure-complexity, ipv4-tcp-header-bitfields, cologne-phonetic-and-match-rating, needleman-wunsch-smith-waterman-alignment, un-vienna-road-signs, billiards-collision-physics, naismith-trail, statistical-mechanics, population-genetics, electrical-transformer-turns-ratio, unicode-script-property-values, sd-card-speed-class, rebar-sizing-astm-a615, pool-spa-water-chemistry, home-canning-process-times, seismic-magnitude, battery-peukert-discharge, ac-skin-effect-transformer-losses, cpf-cnpj-nif-national-id-checksums, grib2-wmo-bitstream-header, aamva-drivers-license-barcode-pdf417, ntp-timestamp-format-and-leap-indicator, o-ring-sizes, npt-pipe-thread, saami-ammunition-caliber, linear-programming-simplex, clausius-clapeyron-vapor-pressure, fips-state-county-codes, usda-plants-taxonomic-registry, orifice-venturi-flow-meter, beer-style-specs, doppler-effect, compton-scattering, ipa-phonetic-alphabet, library-of-congress-classification-outline, nail-size-penny-system, book-format-folio-quarto-octavo, wine-bottle-nomenclature-volumes, garden-hose-thread-ght, wheel-bolt-pattern-pcd, stable-matching-gale-shapley, bezier-de-casteljau-splines, hall-effect, gyroscopic-precession, photoelectric-effect, combinatorial-game-theory-nim-sprague-grundy, un-m49-region-codes, hvac-filter-merv-rating, paper-basis-weight-system, flag-semaphore-encoding, uv-index-calc, watch-movement-ligne-sizing, model-rocket-motor-classification, cornhole-scoring, skin-cancer-epidemiology, chaos-theory-fractal-dimension, thermal-expansion-coefficients, agma-gear-tooth-bending-stress, bolt-preload-torque-tension, magnetic-circuit-reluctance, ashrae-refrigerant-designations, upu-s10-tracking-number, rubiks-cube-notation-and-metrics, food-additive-e-numbers, multihash-cid, axe-throwing-scoring, voting-tally-methods, canine-caloric-requirements, maritime-mid-ship-station, fire-hose-thread-sizing, ski-binding-din-release-setting, zipper-tooth-gauge-sizing, racket-stringing-tension-and-pattern, arrhenius-equation, larmor-radiated-power, npsh-cavitation-margin, centrifugal-fan-laws, magnus-effect, pop-rivet-sizing, michaelis-menten-enzyme-kinetics, larmor-precession, itu-r-recommendation-v431-frequency-band-nomenclature, voltage-drop-conductor-sizing, grounding-electrode-resistance, chimney-stack-effect-draft, concrete-water-cement-ratio-strength, helmholtz-resonator-port-tuning, propeller-pitch-slip-thrust, pencil-lead-diameter-and-hardness-scale, hydraulic-jump-open-channel-flow, epa-air-quality-index-breakpoints, concrete-maturity-method, wet-bulb-globe-temperature-wbgt, capstan-belt-friction-equation, iala-maritime-buoyage, iau-constellation-codes, egg-size-grading, respirator-filter-class-rating, resin-identification-codes, nfpa-fire-extinguisher-classification, iucn-red-list-categories, enhanced-fujita-scale, proquint-encoding, electrical-conduit-trade-size, fishing-hook-size, baume-specific-gravity-converter, kalman-filter-and-state-estimation, coriolis-effect-deflection, coulombs-law-electrostatic-force, stokes-law-terminal-velocity, helical-compression-spring-rate, clothing-pattern-drop-and-suit-size-system, bowling-ball-drilling-layout, tippet-x-diameter-calculator, curie-weiss-magnetic-susceptibility, penman-monteith-reference-evapotranspiration, camera-lens-filter-thread-and-step-ring-sizing, amateur-radio-contest-scoring, optimal-stopping-theory, cherenkov-radiation-angle, zeeman-effect-splitting, josephson-junction-relation, thermal-expansion, malus-law-polarization, hazen-williams-pipe-flow, extended-surface-fin-heat-transfer, fillet-weld-strength, isan-check-character, iswc-check-digit, rifle-scope-moa-mrad-conversion, cvss-scoring, dicom-tag-dictionary, fips-140-security-levels, rutherford-scattering-cross-section, ais-navigation-status-message-types, nema-wiring-device-configurations, rfc5322-email-address-grammar, tor-v3-onion-address, railway-signal-aspects-and-block-rules, uic-wagon-number-check-digit, asl-fingerspelling-manual-alphabet, retrieval-metrics, vehicle-stopping-distance, vcard-property-registry, iana-root-zone-tld-registry, nato-stanag-military-rank-codes, bip39-mnemonic-checksum, nema-mg1-motor-frame-sizes, larson-miller-creep-rupture-parameter, icao-wake-turbulence-separation-calculator, contract-bridge-hand-evaluation, simple-machines-mechanical-advantage, led-photodiode-responsivity-and-quantum-efficiency, icao-notam-q-code-contractions, sysexits-posix-exit-codes, marc21-code-lists, fix-protocol-tag-dictionary, mutcd-traffic-sign-codes, isbn-registration-group-ranges, nordic-personal-id-checksum, table-tennis-scoring, flywheel-kinetic-energy-storage, iec-60529-ip-code-structure, radiation-pressure, gravitational-lensing-deflection, wmo-cloud-atlas, wind-speed-averaging-conversion, FCC-NWS-SAME-event-codes-EAS, transponder-squawk-codes, icd-10-pcs-code-decoder, nema-250-enclosure-type-ratings, richardson-dushman-thermionic-emission, posix-errno-codes, win32-hresult-facility-codes, basel-conv-hazard-codes, sql-sqlstate-codes, badminton-scoring, icao-wake-turbulence-category-assignment, dewey-decimal-classification, mohs-hardness-scale, glasgow-coma-scale, torino-impact-hazard-scale, bortle-dark-sky-scale, textile-care-symbols-iso3758, un-dangerous-goods-placard-design-orange-book, backgammon-pip-count-and-cube, union-find-disjoint-set, quadratic-residues-jacobi-symbol, cigar-ring-gauge, surfboard-volume-calculator, seawater-sound-speed-equations, french-gauge-medical-tubing, duplicate-bridge-matchpoint-scoring, blackjack-basic-strategy-ev, rack-units, eip-55-checksum-address, iccid-sim-card-checksum, iso-15924-scripts, welding-rod-electrode-classification-aws, pinewood-derby-physics, golay-code-23-12, vexillology-flag-construction-proportions, pagerank-power-iteration, raft-consensus-safety-properties, rohs-weee-marking-symbols, ssh-key-fingerprint, woodturning-lathe-speed, table-of-consanguinity-relationship-calculator, apgar-score, mil-std-810-environmental-test-methods, turntable-tonearm-alignment-geometry, roller-derby-jam-scoring, gemstone-carat-weight-from-dimensions, coin-melt-value, computability-turing-machines, public-key-crypto-arithmetic, real-time-scheduling-theory, order-theory-lattices, ipv6-header-bitfields, baking-pan-volume-substitution, bicycle-spoke-length-calculation, freediving-depth-pressure-tables, croquet-and-bocce-scoring-and-legality, skip-list-probabilistic-height, merkle-tree-proof-verification, pickleball-scoring-and-rules, sound-transmission-mass-law, home-roasting-coffee-first-crack-development, elf-header-fields, pcap-global-header-fields, dns-header-bitfields, falconry-jess-and-weight-management, pottery-throwing-and-clay-shrinkage, wine-appellation-classification-systems, un-spsc-product-classification, rubber-plastic-shore-durometer-hardness, tea-brewing-parameters, rowing-ergometer-pace-power, fabric-gsm-areal-density-conversion, kombucha-fermentation-math, fdi-dental-tooth-numbering, precious-metal-hallmark-purity-marks, eu-vat-number-checksum, z-base-32-codec, solar-panel-tilt-poa-irradiance, specific-heat-sensible-latent-load, rxnorm-normalized-drug-names, lockpicking-pin-tumbler-tolerance, loinc-observation-codes, fpv-drone-motor-prop-math, aci-318-reinforced-concrete-flexural-capacity, consensus-quorum-arithmetic, tcg-deck-draw-probability, iso6709, usps-pub28-abbreviations, adts-aac-frame-header, fermi-dirac-statistics, pickleball-equipment-specs, butterworth-chebyshev-filter-design, hash-table-load-factor-and-collision-math, munsell-color-notation, geologic-time-scale-ics, douglas-sea-scale, palermo-impact-hazard-scale, eyring-transition-state-theory, debye-huckel-activity-coefficient, sausage-casing-diameter-standards, economic-inequality-indices, tournament-tiebreak-systems, acupuncture, cocktail, camera, law, copyright, trademark, music-theory, supplements, writing-style, minecraft-dungeons, spanish, medical-denials, languages, behavioral-econ, baseball, agent-practices, pokemon, mcp, readability, citations, relay, models, self-oracle, recall-traps, units, tax, physics, logic, astronomy, biology, geography, medicine, chemistry, math, eurorack, cooking, personal-finance, stardew, coffee, electronics, physiology, diving, decibels, subnetting, textile-gauge, statistics, chess-endgames, woodworking, rating-systems, check-digits, paper-sizes, swe-claim-denial, psychology, roman-numerals, minecraft-mods, encodings, hardiness-zones, terraria, aspect-ratio, resistor-color-code, incoterms, soundex, zigbee, wind-chill, saffir-simpson, dataviz, patents, shoe-size, crc, base58, bech32, reed-solomon, string-similarity, compression, prng, computus, hyperloglog, peppers, tomatoes, fluid-mechanics, information-theory, combinatorics, graph-algorithms, linear-algebra, algorithm-complexity, coding-theory, fourier-analysis, numerical-methods, heat-transfer, markov-chains, orbital-mechanics, html-named-character-references, thermodynamics, geometric-optics, convex-optimization, nuclear-decay, fresnel-equations, myrcene, itu-q-code, 3d-printing, arrow-spine, camera-film-formats, mechanical-vibrations, fiber-optics, beaufort-scale, iana-protocol-numbers, boolean-algebra, game-theory, bolts-screws, standard-atmosphere, capillary-action, tcr-therapy, software-licenses, gauge-systems-industrial, ring-sizes, three-phase-power, http-headers, group-theory, molecular-diffusion, tabletop-wargaming-probability, matrix-decompositions, count-min-sketch, punycode, photovoltaic-cell-model, faa-n-number, orcid-checksum, swift-bic-format, projectile-ballistics-drag-corrected, faa-airport-codes, iso15459-license-plate, typography, tides, ndc, epsg, hts, elevator-rope-crane-wire-rope-classification, ecfr, regular-expression-derivatives, scientific-method, mtg-rules, cas-registry-checksum, international-code-of-signals, garden-perennials, usb-device-descriptor, compost, flag-semaphore, shipping-container-iso-6346-sizing, beer-styles, ceramics-glaze-chemistry, compost-cn-ratio, archimedes-buoyancy-and-flotation, iso-7010-safety-signs, sun-safety, market-identifier-codes, horseshoe-pitching-scoring, voting-theory-social-choice, merchant-category-codes, isrc, iso-3166-3, isil, cfi, perfume-concentration-and-dilution, cheesemaking-recipe-math, wcag-success-criteria, iec-60529-ip-rating-codes, pencil-graphite-hardness-grading, iarc-carcinogen-classification-registry, hornbostel-sachs-instrument-classification, ethernet-cable-category-ratings, chemical-compound-physical-properties, tippet-x-rating, weir-flow-discharge, who-atc-drug-classification, schwarzschild-radius, iata-icao-airline-designators, hl7v2-message-type-registry, nfpa-704-fire-diamond, dea-controlled-substance-schedules, icao-wake-turbulence-category, usda-beef-quality-grades, koppen-climate-classification, modified-mercalli-intensity, ansi-a13-1-pipe-marking, volcanic-explosivity-index, digit-lottery, rayleigh-scattering-intensity, grounded-retrieval, asme-y14-5-gdt-symbols, automotive-blade-fuse-sizing, figure-skating-scoring, ioc-noc-codes, icd-10-pcs, aiga-dot-symbol-signs, universal-dependencies-relations, lsh-minhash, string-matching-algorithms, gymnastics-code-of-points, archery-target-scoring, wind-load-structures, seawater-sound-speed, messier-catalog, grpc-status-codes, cwe-weakness-taxonomy, cites-appendices, climbing-grade-conversion-scales, fire-sprinkler-k-factor-sizing, colregs-navigation-rules, osha-permissible-exposure-limits, ada-2010-accessible-design-standards, cdc-acip-immunization-schedule, un-human-rights-instruments, ipcc-climate-findings, rfc2119-bcp14-requirement-keywords, montreal-protocol-controlled-substance-annexes, hl7-fhir-r4-resource-type-registry, roller-chain-sizing, sec-edgar-filing-rules, systemd, esrb-pegi-content-rating-systems, consumer-product-recalls-policy, antitrust-merger-guidelines, epidemiology-surveillance, usda-egg-poultry-inspection-grade-marks, un-dangerous-goods-packing-instructions, scientometrics, kayak-canoe-hull-speed, radar-range-equation, food-recalls, supreme-court-holdings, wmo-present-weather-code, who-pheic-declarations, us-place-gazetteer, fmcsa-hours-of-service-limits, gdpr-administrative-fine-tiers, fmla-employee-eligibility-thresholds, uspstf-screening-grades, ada-diabetes-diagnostic-criteria, flsa-overtime-exemption-thresholds, cpsc-childrens-product-lead-limits.

  Connector

• create_invoice

  Norway Invoices (Peppol BIS 3.0 / EHF via Storecove)

  Send a Norway B2B electronic invoice over the Peppol network in Peppol BIS 3.0 / EHF (EN 16931) format via Storecove (a certified Peppol Access Point). Norway is moving to mandatory structured e-invoicing for domestic B2B: the parliament (Stortinget) has adopted the reform and the sending obligation applies from 2027-01-01. Builds the structured invoice JSON from seller + buyer (name, Norwegian VAT NO<9 digits>MVA and/or organisasjonsnummer 9 digits, address) and line items (description, quantity, net unit price, VAT rate 25/15/12/0), computes the Norwegian VAT (MVA) breakdown, and submits it under YOUR OWN Storecove credentials. Bring your own credential as header x-storecove-key. You must also pass seller_legal_entity_id — the legalEntityId of the sender you created in your Storecove account. Norwegian VAT (MVA) rates: 25 (standard), 15 (food/groceries), 12 (transport/accommodation and other low-rate services), 0 (zero-rated/exempt/reverse charge). Amounts in NOK. Delivery over Peppol is asynchronous: this returns a submission guid — use get_delivery_evidence with it to fetch the delivery proof/status. Tip: call check_recipient first to confirm the buyer is reachable on Peppol. There is no cancel over Peppol: to reverse an invoice you issue a credit note (a new invoice).

  Connector

• check_recipient

  Norway Invoices (Peppol BIS 3.0 / EHF via Storecove)

  Check whether a business can receive electronic invoices on the Peppol network before you send (Storecove POST /discovery/receives). This is the safe pre-flight for Norwegian B2B: pass the recipient identifier and scheme and learn if they are a registered Peppol participant. For Norway use scheme 0192 with the 9-digit organisasjonsnummer. Returns can_receive=true when the party is reachable (Storecove code OK). If can_receive is false, the recipient is not on Peppol — fall back to recipient_email in create_invoice or ask them to register.

  Connector