← The evidence ledger
Evidence row 988016
Observed , by probe.mcp/1.
- Kind
- mcp.tools
- About
- endpoint 9629003a-1089-4fbf-a255-d5b8682640df
- Recorded
- Previous row
- #774134
- Body SHA-256
- 5e487011910c24bd61e37fbfc5439055e9e5858a743bad4e468a02ac30f6e1f9
- Leaf
- 0x933b688d589a408e1192278017f1907e6fd34236073c249798f9f6134b7b9bd9
What was observed
{
"count": 61,
"tools": [
{
"description": "Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns per-model {score, confidence, signals, raw_response} + a combined view. Useful for AI-marketing audits, pre-launch brand checks, competitive monitoring.",
"inputSchema": {
"examples": [
{
"entity": "Tesla"
}
],
"properties": {
"_apiKey": {
"description": "Optional Anthropic API key (sk-ant-...) — only needed if \"anthropic\" is in models. Passed straight through to api.anthropic.com.",
"type": "string"
},
"context": {
"description": "Optional: a phrase locating the entity (e.g. \"Boston restaurant\", \"B2B SaaS\"). Helps disambiguate common names.",
"type": "string"
},
"entity": {
"description": "The thing to ask about. Brand/business name, product name, person, or topic. E.g. \"Pipeworx\", \"OpenInvoice\", \"Acme Corp pricing\".",
"type": "string"
},
"models": {
"description": "Which models to probe. Supported: \"workers-ai\" (free default), \"anthropic\" (requires _apiKey). Omit for just workers-ai.",
"items": {
"type": "string"
},
"type": "array"
}
},
"required": [
"entity"
],
"type": "object"
},
"name": "ai_visibility_check"
},
{
"description": "What changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and both capture timestamps with their gaps from the requested dates. It diffs readable text, not markup, so a restyled page with the same words reads changed:false. Identical captures answer changed:false with the reason (same capture, identical content digest, or identical text), never an empty diff. A date with no capture within max_gap_days (default 30) answers status \"no_capture\", naming which side is missing and the nearest captures to it. Typical uses: how a privacy policy, terms of service, pricing or product page changed; whether a statement was on a page at a given time.",
"inputSchema": {
"examples": [
{
"date_a": "2022-06-02",
"date_b": "2024-06-15",
"url": "https://www.ftc.gov/policy-notices/privacy-policy"
}
],
"properties": {
"date_a": {
"description": "The earlier date, as YYYY-MM-DD (e.g. \"2021-06-01\").",
"type": "string"
},
"date_b": {
"description": "The later date, as YYYY-MM-DD (e.g. \"2024-06-01\").",
"type": "string"
},
"max_gap_days": {
"description": "Furthest a capture may be from each date and still be used, in days. Default 30, max 3650.",
"type": "number"
},
"url": {
"description": "The page address, e.g. \"https://www.ftc.gov/policy-notices/privacy-policy\".",
"type": "string"
}
},
"required": [
"url",
"date_a",
"date_b"
],
"type": "object"
},
"name": "archive_compare"
},
{
"description": "What did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy, and the GAP between the date asked for and the capture actually used (e.g. \"Captured 1.5 day(s) before the requested date\"). One call replaces the find-capture, fetch-record, parse-HTML chain. If no archive holds a capture within max_gap_days (default 30) it answers status \"no_capture\" and names the nearest capture before and after the date with their gaps, so a distant capture is never passed off as the page on that date. Every archive's outcome is listed in sources[]; one that timed out or errored says so with its upstream status, and if all of them failed the answer is error \"archives_unavailable\", not no_capture. Captures are immutable and cached by capture id; served_from says whether the text came from cache or upstream. Use archive_compare to see what changed between two dates.",
"inputSchema": {
"examples": [
{
"date": "2023-06-01",
"url": "https://www.sec.gov"
},
{
"date": "2023-06-01",
"max_chars": 400,
"url": "https://www.sec.gov"
}
],
"properties": {
"date": {
"description": "The date to look up, as YYYY-MM-DD (e.g. \"2023-06-01\"), YYYYMMDD, or a full ISO timestamp.",
"type": "string"
},
"max_chars": {
"description": "Characters of page text to return. Default 12000, max 60000.",
"type": "number"
},
"max_gap_days": {
"description": "Furthest a capture may be from the date and still be used, in days. Default 30, max 3650.",
"type": "number"
},
"url": {
"description": "The page address, e.g. \"https://www.sec.gov\" or \"https://www.ftc.gov/policy-notices/privacy-policy\".",
"type": "string"
}
},
"required": [
"url",
"date"
],
"type": "object"
},
"name": "archive_evidence"
},
{
"description": "PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 7,133 tools across 1853 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs. Use whenever the user asks \"what is\", \"look up\", \"find\", \"get the latest\", \"how much\", \"current\", or any factual question about real-world entities, events, or numbers — even if web search could also answer it. Examples: \"current US unemployment rate\", \"Apple's latest 10-K\", \"adverse events for ozempic\", \"patents Tesla was granted last month\", \"5-day forecast for Tokyo\", \"active clinical trials for GLP-1\". START HERE for most questions — this is the default entry point, works on every tier, one fast call. Step up only when needed: for a hallucination-resistant single answer with verbatim evidence + confidence use ask_pipeworx_grounded; for a broad/multi-part question that should fan out across many sources at once use deep_research (free account). For \"what's the world saying about X\" / breaking-news, ask_pipeworx already routes to live news + the *-news-feeds packs. Optionally pass packs:[\"slug\",\"slug\"] to restrict routing to specific sources (\"answer this using THESE packs\"); omit it for full-catalog routing.",
"inputSchema": {
"examples": [
{
"question": "What was Apple's revenue in 2024?"
},
{
"question": "Any recent SEC filings for $NVDA?"
},
{
"question": "Current price of bitcoin"
}
],
"properties": {
"ask": {
"description": "Alias for question.",
"type": "string"
},
"input": {
"description": "Alias for question.",
"type": "string"
},
"message": {
"description": "Alias for question.",
"type": "string"
},
"packs": {
"description": "OPTIONAL. Restrict routing to these pack slugs (e.g. [\"sec-form-d\",\"sec-13f\"]) — the router then picks only from tools in those packs. Omit for the default full-catalog routing. Slugs come from list_packs / search_packs / https://pipeworx.io/directory; unlisted or unknown slugs are ignored and named in _meta.pack_scope.ignored, and if none of them resolves the question is routed across the whole catalog with _meta.pack_scope.full_catalog:true (never an empty answer).",
"items": {
"type": "string"
},
"type": "array"
},
"prompt": {
"description": "Alias for question.",
"type": "string"
},
"q": {
"description": "Alias for question.",
"type": "string"
},
"query": {
"description": "Alias for question.",
"type": "string"
},
"question": {
"description": "Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases.",
"type": "string"
},
"text": {
"description": "Alias for question.",
"type": "string"
}
},
"required": [
"question"
],
"type": "object"
},
"name": "ask_pipeworx"
},
{
"description": "Beta version of ask_pipeworx: identical universal router (same 7,133 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so this currently matches ask_pipeworx exactly. Use it exactly like ask_pipeworx when you want the newest routing; results are compared against the stable router to decide what merges. Falls back to nothing — this IS a full working router, just the experimental edge.",
"inputSchema": {
"examples": [
{
"question": "What is the current US unemployment rate?"
}
],
"properties": {
"ask": {
"description": "Alias for question.",
"type": "string"
},
"input": {
"description": "Alias for question.",
"type": "string"
},
"message": {
"description": "Alias for question.",
"type": "string"
},
"packs": {
"description": "OPTIONAL. Restrict routing to these pack slugs (e.g. [\"sec-form-d\",\"sec-13f\"]) — the router then picks only from tools in those packs. Omit for the default full-catalog routing. Slugs come from list_packs / search_packs / https://pipeworx.io/directory; unlisted or unknown slugs are ignored and named in _meta.pack_scope.ignored, and if none of them resolves the question is routed across the whole catalog with _meta.pack_scope.full_catalog:true (never an empty answer).",
"items": {
"type": "string"
},
"type": "array"
},
"prompt": {
"description": "Alias for question.",
"type": "string"
},
"q": {
"description": "Alias for question.",
"type": "string"
},
"query": {
"description": "Alias for question.",
"type": "string"
},
"question": {
"description": "Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases.",
"type": "string"
},
"text": {
"description": "Alias for question.",
"type": "string"
}
},
"required": [
"question"
],
"type": "object"
},
"name": "ask_pipeworx_beta"
},
{
"description": "Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,133 across 1853 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbatim quote), confidence, source, fetched_at, refusal_reason:null} on success, OR an explicit refusal {answer:null, refusal_reason:\"not_in_source\"|\"no_tool_match\"|\"tool_error\"|\"data_truncated\"|\"llm_error\"} when the data doesn't directly answer. An \"llm_error\" also carries refusal_cause (\"wall\" = our time budget ended before any model call was made; \"route\"|\"threw\"|\"unparseable\"|\"wall_after_failure\" = a model call failed); refusal_reason itself is unchanged. Use whenever an answer will be quoted, cited, or acted on, and the agent must not invent facts (financial verdicts, legal claims, medical lookups, public statements). Costs one extra LLM call vs ask_pipeworx — prefer ask_pipeworx for casual lookups.",
"inputSchema": {
"examples": [
{
"question": "What was Apple's fiscal 2023 revenue?"
}
],
"properties": {
"ask": {
"description": "Alias for question.",
"type": "string"
},
"input": {
"description": "Alias for question.",
"type": "string"
},
"message": {
"description": "Alias for question.",
"type": "string"
},
"prefer_tool": {
"description": "Run this exact tool instead of letting the router choose — use a name from a previous answer's alternatives[]. Arguments are still filled from your question. Unknown names are refused, never guessed.",
"type": "string"
},
"prompt": {
"description": "Alias for question.",
"type": "string"
},
"q": {
"description": "Alias for question.",
"type": "string"
},
"query": {
"description": "Alias for question.",
"type": "string"
},
"question": {
"description": "Your question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases.",
"type": "string"
},
"text": {
"description": "Alias for question.",
"type": "string"
}
},
"required": [
"question"
],
"type": "object"
},
"name": "ask_pipeworx_grounded"
},
{
"description": "Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), a polymarket.com URL, or a question text. A dated slug (\"...-by-june-30-2026\") still resolves after it settles — the resolver retries a closed-market lookup rather than giving up on the bare one — so either dated or undated works; prefer whichever slug you actually have. 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. A market whose own deadline has already passed returns status:\"market_expired_or_resolved\" + expired_deadline (the date), which is deliberately NOT the same answer as low_confidence_match: your slug was right and is merely settled, so the useful retry is the successor market for the same question, not a corrected spelling. 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.",
"inputSchema": {
"examples": [
{
"market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
},
{
"market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
}
],
"properties": {
"depth": {
"description": "quick = 2-3 evidence sources, thorough = full fan-out. Default thorough.",
"enum": [
"quick",
"thorough"
],
"type": "string"
},
"include_raw": {
"description": "Default false. When false (recommended), FRED/FDA/GDELT/Federal-Register evidence is summarized to the few fields agents actually use — keeps responses under ~20KB. Pass true to get full upstream payloads (50KB-500KB) when you need to recompute deltas, cite specific observations, or post-process.",
"type": "boolean"
},
"market": {
"description": "Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs still resolve after they settle — the resolver retries a closed-market lookup — so either a dated or undated slug works.",
"type": "string"
}
},
"required": [
"market"
],
"type": "object"
},
"name": "bet_research"
},
{
"description": "Cheap categorization: given a company and a list of candidate labels, decide which labels apply — the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, evidence_url, quote, status: found|inferred|not_established} — \"found\" only when the model's quote is independently verified as a verbatim substring of the text used. Pass text directly (cheapest — no fetch) or entity.domain to fetch the homepage once as a fallback. No text and no domain means every label is not_established with no model call made.",
"inputSchema": {
"examples": [
{
"entity": {
"domain": "stripe.com",
"name": "Stripe"
},
"labels": [
"healthcare",
"fintech",
"logistics"
]
}
],
"properties": {
"entity": {
"description": "The row/company to classify. At least one of name/domain required.",
"properties": {
"domain": {
"description": "Company website domain — used to fetch the homepage ONLY when text is not provided.",
"type": "string"
},
"name": {
"description": "Company name, e.g. \"Acme Robotics\".",
"type": "string"
}
},
"type": "object"
},
"labels": {
"description": "Candidate labels to test, 2-30 strings, e.g. [\"healthcare\",\"fintech\",\"logistics\"].",
"items": {
"type": "string"
},
"type": "array"
},
"text": {
"description": "Text to classify directly (a description, a page you already fetched, etc.) — cheapest path, skips any fetch.",
"type": "string"
}
},
"required": [
"entity",
"labels"
],
"type": "object"
},
"name": "classify_row"
},
{
"description": "TYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period — \"Apple revenue for fiscal 2023\", \"Walmart net income FY2026 Q3\", \"Microsoft cash at the end of fiscal 2024\". PREFER OVER entity_profile / get_company_financials whenever the period matters: those answer \"the most recent figures\" and will happily hand back FY2025 when you asked about FY2019, and neither separates a discrete quarter from a year-to-date figure. This one refuses instead — it NEVER substitutes the latest period for the period requested, NEVER returns 0 for missing data, NEVER lets a 9-month YTD number answer a quarterly question, and NEVER converts a currency. Every answer carries the exact us-gaap concept it came from, what that concept MEASURES (NetIncomeLoss excludes non-controlling interests, ProfitLoss includes them — not synonyms), the accession number and a link to the filing on sec.gov, the restatement trail of any superseded figures, and a contract + derivation version to pin against. Fiscal periods are the FILER'S OWN, anchored on their fiscal-year end, so Walmart's year ending 2026-01-31 is FY2026 and Apple's ending 2025-09-27 is FY2025. Attributes: revenue, net_income, cash, gross_profit, operating_income, eps_diluted, capex, operating_cash_flow, long_term_debt, shares_outstanding (the dei COVER-PAGE share count, so its period end is the cover date, after the quarter closed — that is the most current count the filing carries). Units are not all USD: shares_outstanding is in `shares` with currency null, eps_diluted in `USD/shares`. A discrete quarter the filer never filed — every Q4, and Q2/Q3 of cash-flow lines, which are filed year-to-date — is DERIVED as YTD(q) minus YTD(q-1) and comes back with `reported: false`, the subtraction named in `derivation` (fy_minus_9m / ytd_9m_minus_6m / ytd_6m_minus_3m) and both legs with their filings in `derived_from`; test `reported` if you will only accept a figure lifted from a filing. Per-share and balance-sheet figures are NEVER derived. Every non-answer is a named status — `unavailable` (the filer did not report it for that period; the periods that DO exist are listed, without values), `unsupported` (outside what v1 covers — a non-us-gaap filer, an unknown attribute, a non-USD unit), `ambiguous` (the company name matched two filers equally well; both are named), `conflicting` (two filings the same day disagree; both are returned and neither is picked), `partial` (a value with no accession behind it). Source: SEC EDGAR, XBRL financial facts, one publisher read once — see `corroboration`. Same response is served at POST https://gateway.pipeworx.io/v1/facts for non-MCP callers.",
"inputSchema": {
"examples": [
{
"attribute": "revenue",
"company": "AAPL",
"period": {
"fiscal_year": 2023,
"type": "annual"
}
},
{
"attribute": "shares_outstanding",
"company": "TSLA",
"period": {
"fiscal_quarter": 2,
"fiscal_year": 2026,
"type": "quarterly"
}
},
{
"attribute": "capex",
"company": "TSLA",
"period": {
"fiscal_quarter": 2,
"fiscal_year": 2026,
"type": "quarterly"
}
},
{
"attribute": "net_income",
"company": "TSLA",
"period": {
"fiscal_quarter": 4,
"fiscal_year": 2025,
"type": "quarterly"
}
}
],
"properties": {
"as_of": {
"description": "Past ISO timestamp with timezone. Replay the latest answer actually recorded by that instant; no invented history or live fallback.",
"type": "string"
},
"attribute": {
"description": "Which figure. \"revenue\" = total consolidated revenue; \"net_income\" = net income (loss); \"cash\" = cash and cash equivalents at the period end; \"gross_profit\"; \"operating_income\"; \"eps_diluted\" (diluted EPS, unit USD/shares, never derived or summed); \"capex\" (cash paid for PP&E); \"operating_cash_flow\" (net cash from operating activities); \"long_term_debt\" (the noncurrent balance-sheet line where the filer tags it, else total long-term debt — `fact.measure` says which); \"shares_outstanding\" (dei cover-page common shares, unit \"shares\", as of the COVER DATE rather than the period end).",
"enum": [
"revenue",
"net_income",
"cash",
"gross_profit",
"operating_income",
"eps_diluted",
"capex",
"operating_cash_flow",
"long_term_debt",
"shares_outstanding"
],
"type": "string"
},
"basis": {
"description": "Only \"consolidated\" in v1. Segment and product-level figures are XBRL-dimensioned and are not reachable through this contract at any concept.",
"enum": [
"consolidated"
],
"type": "string"
},
"company": {
"description": "Ticker (\"AAPL\"), 10-digit CIK (\"0000320193\"), or company name. A name that matches two filers equally well returns status \"ambiguous\" with both named rather than guessing — pass a ticker or CIK to be certain.",
"type": "string"
},
"exclude_publishers": {
"description": "Publisher ids forbidden for fact retrieval: sec, fmp, alphavantage. Case and surrounding whitespace are normalized; unknown ids are refused. Excluding sec currently leaves no eligible fact source and returns unavailable/sources_excluded with the selection reasons. Identity and fiscal-calendar lookups may still use SEC; no excluded financial concept is fetched.",
"items": {
"type": "string"
},
"type": "array"
},
"freshness": {
"description": "cached (default) permits an eligible stored answer; fresh requires an upstream refresh and never silently falls back to stale data.",
"enum": [
"cached",
"fresh"
],
"type": "string"
},
"max_age": {
"description": "Maximum age in seconds of the upstream publication, not our fetch. Older or undated facts are withheld.",
"maximum": 3155760000,
"minimum": 0,
"type": "number"
},
"period": {
"description": "The reporting period, stated explicitly. There is no default and no \"latest\" — that is the point of this tool.",
"properties": {
"fiscal_quarter": {
"description": "1-4. Required when type is \"quarterly\"; rejected when type is \"annual\".",
"type": "number"
},
"fiscal_year": {
"description": "The FILER'S fiscal year — the year the period ends in by their own calendar. Walmart's year ending 2026-01-31 is 2026.",
"type": "number"
},
"type": {
"description": "\"annual\" = the full fiscal year. \"quarterly\" = ONE discrete quarter, never a year-to-date figure.",
"enum": [
"annual",
"quarterly"
],
"type": "string"
}
},
"required": [
"type",
"fiscal_year"
],
"type": "object"
},
"restatement": {
"description": "Default \"as_amended\" — the latest filed figure for the period, with everything it superseded listed. \"as_originally_reported\" takes the first filing instead.",
"enum": [
"as_amended",
"as_originally_reported"
],
"type": "string"
}
},
"required": [
"company",
"attribute",
"period"
],
"type": "object"
},
"name": "company_facts"
},
{
"description": "Search the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back — a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CNPJ, or an LEI. Use this when you want the OFFICIAL REGISTERED ENTITY and the country is not the US, or when you do not know which country it is. Registers searched: Companies House (GB), Enhetsregisteret (NO), PRH/YTJ (FI), Sirene (FR), 法人番号公表サイト (JP), RIK e-Business Register (EE), and the GLEIF LEI crosswalk, which reaches jurisdictions we have no register pack for (DE, SE, AU, SG...). THIS TOOL REFUSES TO GUESS, and that is its point: when two different companies match a name equally well it answers `match_status: \"ambiguous\"` with BOTH, rather than naming one. A one-word trading name usually IS ambiguous — \"Bolt\", \"Apple\", \"Next\", \"Sea\", \"DNB\" each match a well-known group AND unrelated micro-entities whose registered name is exactly that word — so pass `country` when you know it. Every response names EVERY register it asked under `searched[]`, with that register's own as-of date and row count, and a register that could not be reached carries an `error` there rather than reading as zero rows: \"we could not ask Companies House\" is never the same answer as \"this company is not in Britain\". `related[]` holds entities that collapsed INTO the match — the same company seen through another register, or another country's arm sharing its LEI — so a multinational returns one answer rather than tying with itself. NOT A PEOPLE SEARCH: sole traders and other natural persons are excluded on the publisher's own legal-form field, never guessed from the shape of a name. For US public companies prefer resolve_entity (CIK + ticker + FIGI); the two share this same matcher, and resolve_entity returns these register fields too.",
"inputSchema": {
"examples": [
{
"country": "NO",
"name": "Equinor ASA"
},
{
"country": "JP",
"name": "株式会社花王"
},
{
"country": "EE",
"name": "Bolt"
}
],
"properties": {
"country": {
"description": "OPTIONAL ISO 3166-1 alpha-2 of the register you mean (\"GB\", \"NO\", \"FI\", \"FR\", \"JP\", \"EE\", \"BR\"). Narrows the fan-out, and is frequently the difference between an answer and `ambiguous` on a short name. The GLEIF crosswalk is asked whatever you pass, because for several jurisdictions it is the only register we can name at all.",
"type": "string"
},
"limit": {
"description": "Maximum candidates to return, 1-50 (default 10). Does not change which registers are asked, only how many rivals come back.",
"maximum": 50,
"minimum": 1,
"type": "number"
},
"name": {
"description": "The company name as you have it, in its own script. Pass it VERBATIM — do not strip the legal form (\"Oyj\", \"AS\", \"株式会社\", \"Ltd\"): in Japanese the form is a PREFIX as often as a suffix and 株式会社花王 and 花王株式会社 are DIFFERENT companies, so the form is often the only evidence that separates two candidates. Diacritics, full-width characters and kana are all handled.",
"type": "string"
}
},
"required": [
"name"
],
"type": "object"
},
"name": "company_register_search"
},
{
"description": "\"Compare X and Y\" / \"X vs Y\" / \"X versus Y\" / \"which is bigger / better / larger / more profitable\" / \"rank these companies\" / \"head to head\" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type=\"company\" pulls LATEST 10-K revenue + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly — AAPL Sep, NVDA Jan, etc.). type=\"drug\" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so \"largest\" / \"most\" / \"biggest\" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8–15 sequential lookups.",
"inputSchema": {
"examples": [
{
"type": "company",
"values": [
"AAPL",
"MSFT"
]
}
],
"properties": {
"type": {
"description": "Entity type: \"company\" or \"drug\".",
"enum": [
"company",
"drug"
],
"type": "string"
},
"values": {
"description": "For company: 2–5 tickers/CIKs (e.g., [\"AAPL\",\"MSFT\"]). For drug: 2–5 names (e.g., [\"ozempic\",\"mounjaro\"]).",
"items": {
"type": "string"
},
"maxItems": 5,
"minItems": 2,
"type": "array"
}
},
"required": [
"type",
"values"
],
"type": "object"
},
"name": "compare_entities"
},
{
"description": "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 1853 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 7,133 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 — a resolvable pipeworx:// record URI, present only when the source emits one that resources/read can actually serve, so a citation you get back is always fetchable. \"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).",
"inputSchema": {
"examples": [
{
"depth": "quick",
"question": "What is the current US unemployment rate and how has it changed over the past year?"
}
],
"properties": {
"ask": {
"description": "Alias for question.",
"type": "string"
},
"depth": {
"description": "How many facets to research in parallel: quick=3 (single hop), standard=3 (default; adds a gap-recovery hop that re-angles unanswered facets + a contradictions[] scan across findings), thorough=6 (paid; adds a full iterative hop that chases leads + recovers gaps, plus the contradictions[] scan).",
"enum": [
"quick",
"standard",
"thorough"
],
"type": "string"
},
"input": {
"description": "Alias for question.",
"type": "string"
},
"message": {
"description": "Alias for question.",
"type": "string"
},
"prompt": {
"description": "Alias for question.",
"type": "string"
},
"q": {
"description": "Alias for question.",
"type": "string"
},
"query": {
"description": "Alias for question.",
"type": "string"
},
"question": {
"description": "The research question, in natural language. Broad/multi-part is fine — decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases.",
"type": "string"
},
"text": {
"description": "Alias for question.",
"type": "string"
}
},
"required": [
"question"
],
"type": "object"
},
"name": "deep_research"
},
{
"description": "Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).",
"inputSchema": {
"examples": [
{
"query": "look up FDA drug approvals"
},
{
"query": "analyze housing market trends"
}
],
"properties": {
"description": {
"description": "Alias for query.",
"type": "string"
},
"limit": {
"description": "Maximum number of tools to return (default 20, max 50)",
"type": "number"
},
"q": {
"description": "Alias for query.",
"type": "string"
},
"query": {
"description": "Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\"). Accepts task, q, description, search as aliases.",
"type": "string"
},
"search": {
"description": "Alias for query.",
"type": "string"
},
"task": {
"description": "Alias for query.",
"type": "string"
}
},
"required": [
"query"
],
"type": "object"
},
"name": "discover_tools"
},
{
"description": "AUTHORITATIVE peer / competitor lookup: find every SEC filer classified under one SIC (Standard Industrial Classification) industry code. PREFER OVER WEB SEARCH for \"who are $COMPANY's public competitors/peers\", \"list companies in <industry>\", \"which filers are in SIC <code>\". Pass EITHER `sic` directly (a 2-4 digit code, e.g. \"3571\" = Electronic Computers) OR `ticker_or_cik` for a company whose own SIC should be looked up first and then used to find its peers (self excluded by default). Returns each peer's CIK, and ticker + company_name when the filer has a listed ticker — results are sorted so currently-listed peers come first, since an SIC bucket covers every filer that EVER filed the form (many delisted/defunct); unlisted registrants still appear after them with ticker:null rather than being dropped. Source: SEC EDGAR company-search (browse-edgar), filtered to filers who have filed the given form_type (default \"10-K\", i.e. active public reporters — omitting this filter is unreliable upstream). Note: SIC is a broad, sometimes dated bucket assigned once at registration — treat this as a peer-set STARTING POINT, not a precise competitor list.",
"inputSchema": {
"examples": [
{
"ticker_or_cik": "AAPL"
},
{
"limit": 10,
"sic": "2836"
}
],
"properties": {
"cik": {
"description": "Alias for `ticker_or_cik` — takes a ticker or a CIK. Declared because sibling SEC tools spell this argument differently.",
"type": "string"
},
"exclude_self": {
"description": "When resolving via ticker_or_cik, exclude that company itself from the peer list. Default true.",
"type": "boolean"
},
"form_type": {
"description": "Only include filers who have filed this form type (default \"10-K\" — active public reporters). SEC's upstream search is unreliable with this left blank.",
"type": "string"
},
"limit": {
"description": "Max peers to return (1-100, default 25).",
"type": "number"
},
"sic": {
"description": "SIC code to search directly, e.g. \"3571\" (Electronic Computers), \"2836\" (Biological Products), \"6021\" (National Commercial Banks). Provide this OR ticker_or_cik.",
"type": "string"
},
"ticker": {
"description": "Alias for `ticker_or_cik` — takes a ticker or a CIK. Declared because sibling SEC tools spell this argument differently.",
"type": "string"
},
"ticker_or_cik": {
"description": "Ticker (e.g. \"AAPL\") or CIK of a company whose SIC should be resolved first, then used to find its peers. Provide this OR sic. Aliases: `cik`, `ticker`.",
"type": "string"
}
},
"type": "object"
},
"name": "edgar_companies_by_sic"
},
{
"description": "AUTHORITATIVE historical financials for any US public company. Source: SEC XBRL filings (the official numbers companies file, not third-party scrapes). Send the company as `cik` — that argument takes a TICKER (\"AAPL\") or a CIK (\"320193\"), and `ticker` / `ticker_or_cik` are accepted as aliases for it — plus the metric as `concept` (alias `metric`), which takes a friendly name: Revenue, NetIncomeLoss, Cash, LongTermDebt, EarningsPerShareDiluted. The tool resolves the right XBRL tag for that filer (post-ASC-606 companies use RevenueFromContractWithCustomerExcludingAssessedTax instead of \"Revenues\", etc.). Returns both ANNUAL (10-K) and QUARTERLY (10-Q) values by default, each labeled with fiscal_period and form, newest first, PLUS a `latest` field holding the single freshest data point. Every row also carries `period_start`/`period_end`/`duration_days` so the window a value covers is never ambiguous. Q4 rows are DERIVED (FY minus Q1-Q3, marked derived:true) because SEC filers never report a standalone Q4 fact — so \"revenue Q4 2024\" questions are answerable directly from `values`. CASH-FLOW-STATEMENT concepts (OperatingCashFlow, Capex and siblings) are filed CUMULATIVELY by most filers — a 10-Q's six-month figure is reported under the SAME period label the discrete quarter would use. Those rows are labeled `fiscal_period` \"H1\" (six months) or \"9M\" (nine months) with `ytd:true`, never \"Q2\"/\"Q3\" bare, and a discrete-quarter sibling (`derived:true`, e.g. Q2 = H1 minus Q1) is added alongside so \"capex Q2\" is still answerable without presenting the six-month total as a quarter. Income-statement lines (Revenue, NetIncomeLoss) are usually filed quarter-only already and are unaffected. For one specific period, pass `fiscal_year` and/or `fiscal_period` as ARGUMENTS and the values array comes back filtered to it (they are also the names of the fields on each returned row, which is what to match on if you ask for every period instead); do not default to `latest` for a period question. Use `latest` for point-in-time metrics like cash, runway, and debt — it is the newest 10-Q when one is more recent than the last 10-K, so a stale annual figure never masks a newer quarter; for a YTD-shaped concept, `latest` prefers the discrete derived quarter over the as-filed cumulative figure, so it is never silently a 2-3x-too-large number. Use for \"what was AAPL's revenue in 2024\", \"NVDA's latest cash position\", \"show me long-term debt trend\", anything where you need the SEC-filed number rather than an estimate.",
"inputSchema": {
"examples": [
{
"cik": "320193",
"concept": "Revenue"
},
{
"cik": "1652044",
"concept": "NetIncomeLoss"
},
{
"cik": "DOV",
"concept": "NetIncomeLoss",
"fiscal_period": "FY",
"fiscal_year": "2024",
"period": "annual"
},
{
"cik": "CAPR",
"concept": "Cash"
}
],
"properties": {
"cik": {
"description": "REQUIRED (or one of its aliases `ticker` / `ticker_or_cik`). Ticker (e.g., \"AAPL\") or CIK number (e.g., \"320193\"). Tickers are auto-resolved.",
"type": "string"
},
"concept": {
"description": "REQUIRED (alias `metric`). Metric name. Common: \"Revenue\" / \"Revenues\", \"NetIncomeLoss\", \"Cash\", \"Assets\", \"Liabilities\", \"StockholdersEquity\", \"EarningsPerShareDiluted\", \"LongTermDebt\", \"SharesOutstanding\" (newest cover-page count, dei), \"Capex\", \"OperatingCashFlow\", \"ResearchAndDevelopment\", \"SGA\", \"CostOfRevenue\", \"DilutedShares\", \"PublicFloat\". Exact us-gaap or dei tag names also work.",
"type": "string"
},
"fiscal_period": {
"description": "Optional filter: return only rows for this period within the fiscal year — \"FY\" (annual), \"Q1\", \"Q2\", \"Q3\", \"Q4\" (derived: FY minus Q1-Q3), \"H1\" (six-month year-to-date, cash-flow-statement concepts only), or \"9M\" (nine-month year-to-date). Combine with fiscal_year for a single figure. Asking for \"Q2\"/\"Q3\" on a concept this filer reports cumulatively returns the DERIVED discrete quarter, not the H1/9M total.",
"enum": [
"FY",
"Q1",
"Q2",
"Q3",
"Q4",
"H1",
"9M"
],
"type": "string"
},
"fiscal_year": {
"description": "Optional filter: return only rows for this fiscal year, e.g. \"2024\". This is the filer's OWN fiscal year label (NVDA's FY2024 ended Jan 2024), not a calendar year. Unmatched years are reported with the years that ARE available rather than as an empty result.",
"type": "string"
},
"metric": {
"description": "Alias for `concept` — the word this tool's own description uses for the thing you are asking about.",
"type": "string"
},
"period": {
"description": "Which reporting periods to return: \"all\" (default — annual 10-K + quarterly 10-Q), \"annual\" (10-K/20-F/40-F only), or \"quarterly\" (10-Q only). Point-in-time metrics (cash/runway/debt) usually want the default so the freshest quarter is included; use \"annual\" for clean year-over-year trends.",
"enum": [
"all",
"annual",
"quarterly"
],
"type": "string"
},
"ticker": {
"description": "Alias for `cik` — same thing, a ticker or a CIK. Declared because sibling SEC tools name this argument differently (edgar_fund_holdings uses `ticker`, edgar_company_filings uses `ticker_or_cik`) and a caller filling arguments from prose reaches for whichever it read; all three spellings work here.",
"type": "string"
},
"ticker_or_cik": {
"description": "Alias for `cik` — the spelling used by edgar_company_filings, edgar_insider_transactions and edgar_product_revenue.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_company_concept"
},
{
"description": "AUTHORITATIVE full XBRL fundamentals dump for a US public company. Send the company as `cik` — that argument takes a TICKER (\"NVDA\") or a CIK (\"320193\"), and `ticker` / `ticker_or_cik` are accepted as aliases for it. Returns every reported financial metric (hundreds of concepts: revenue, net income, assets, liabilities, EPS, cash flow lines, segment breakdowns) with annual and historical values pulled straight from the company's SEC filings — the official numbers, not estimates. Use when you need the complete fundamental picture vs. one metric (for one metric use edgar_company_concept). Leads with latest_annual — revenue, net income, assets, cash, EPS for the most recent fiscal year, resolved to whichever XBRL concept the filer currently reports under — and flags retired concepts (e.g. a pre-ASC-606 Revenues tag) as stale so a 2010 figure is never mistaken for current. Large payload; agents typically use this once to discover available concepts then narrow to edgar_company_concept for follow-up queries. For just the headline figures plus the recent filings list, edgar_company_snapshot is the smaller one-call answer.",
"inputSchema": {
"examples": [
{
"cik": "320193"
}
],
"properties": {
"cik": {
"description": "REQUIRED (or one of its aliases `ticker` / `ticker_or_cik`). Ticker (\"NVDA\") or CIK number (\"320193\"). Tickers are auto-resolved to CIKs internally.",
"type": "string"
},
"ticker": {
"description": "Alias for `cik` — same thing, a ticker or a CIK. The spelling edgar_fund_holdings and edgar_ticker_to_cik use.",
"type": "string"
},
"ticker_or_cik": {
"description": "Alias for `cik` — the spelling edgar_company_filings, edgar_insider_transactions and edgar_product_revenue use.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_company_facts"
},
{
"description": "AUTHORITATIVE list of recent SEC filings for a specific US public company. Send the company as `ticker_or_cik` — that argument takes a ticker (\"AAPL\") or a CIK (\"320193\"), and `cik` / `ticker` are accepted as aliases for it. **When the question is about ONE filing rather than the list, say which one**: pass `accession` to narrow to it, or `filed` (\"2026-09-29\", \"2026-09\") when you know only the date, and add `include_primary_text:true` to get that filing's text back here instead of chaining a second call. Filter by form type — \"10-K\" (annual report), \"10-Q\" (quarterly), \"8-K\" (material event — but for severity-classified 8-Ks specifically, prefer sec_8k_recent), \"DEF 14A\" (proxy), \"S-1\" (IPO registration), etc. Returns filing dates, form types, accession numbers, document links. Needs a ticker or CIK: a company that has only just filed its S-1 has no ticker, so for \"find <company> S-1\" or \"S-1 filings filed today\" use edgar_search_filings (form_type \"S-1\", company name as the query). Use for \"what did $TICKER recently file\" or \"show me the last N proxy statements for $TICKER\". For specific financial metrics over time use edgar_company_concept; for the full XBRL dump use edgar_company_facts. If you also need the headline financials alongside the filings, edgar_company_snapshot returns both in one call.",
"inputSchema": {
"examples": [
{
"form_type": "10-Q",
"limit": 15,
"ticker_or_cik": "AAPL"
},
{
"limit": 20,
"ticker_or_cik": "320193"
},
{
"form_type": "8-K",
"ticker_or_cik": "Amyris"
}
],
"properties": {
"accession": {
"description": "Narrow the list to ONE filing you already know the accession of, dashed or not (e.g. \"0001628280-26-063820\") — use this when the question is about a specific filing rather than \"what has this company filed\". Pair it with `include_primary_text:true` to get that filing's text back in the same call. A named accession that does not belong to this filer is an explicit error, never a silently unfiltered list.",
"type": "string"
},
"cik": {
"description": "Alias for `ticker_or_cik` — the spelling edgar_company_concept and edgar_company_facts use for the same thing. Takes a ticker or a CIK.",
"type": "string"
},
"filed": {
"description": "Only filings filed on this date, in this month, or in this year — \"2026-09-29\", \"2026-09\", \"2026\" (US spellings \"09/29/2026\" and \"September 29, 2026\" are accepted too). Use it when the question names WHEN (\"Tesla's September 29 2026 8-K\") and you do not have the accession: without it the newest filing of that form is returned, which for an 8-K is routinely a different filing from the one asked about.",
"type": "string"
},
"form_type": {
"description": "Filter by SEC form type (e.g., \"10-K\", \"10-Q\", \"8-K\"). Omit for all types.",
"type": "string"
},
"include_primary_text": {
"description": "When true, also return the primary document's text (HTML stripped to plaintext, capped at ~40,000 chars) under `primary_text`, for the SINGLE filing `accession` names. Ignored — with a note saying so — when no accession narrows the list, since the text of twenty filings is not a thing this tool returns; use edgar_filing_text for that.",
"type": "boolean"
},
"limit": {
"description": "Max filings to return (1-40, default 20)",
"type": "number"
},
"ticker": {
"description": "Alias for `ticker_or_cik` — the spelling edgar_fund_holdings and edgar_ticker_to_cik use for the same thing. Takes a ticker or a CIK.",
"type": "string"
},
"ticker_or_cik": {
"description": "REQUIRED (or one of its aliases `cik` / `ticker`). Ticker symbol (e.g., \"AAPL\") or CIK number (e.g., \"320193\")",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_company_filings"
},
{
"description": "ONE CALL for \"give me the SEC picture on $TICKER\" / \"what has $COMPANY filed recently and what are its numbers\" / \"pull the filings and financials for X\". Resolves a ticker, company name or CIK and returns, from SEC EDGAR, the three things callers otherwise chain by hand across edgar_ticker_to_cik -> edgar_company_filings -> edgar_company_concept: the identity (cik, company_name, tickers, SIC code, fiscal year end), the recent filings list (accession numbers, form types, filing dates, document links — by default the substantive forms 10-K/10-Q/8-K/20-F/40-F/6-K/DEF 14A, so insider Form 4 noise is excluded; pass `form_type` for one form or \"all\"), and the headline XBRL figures from the latest annual report (revenue, net income, operating income, gross profit, assets, liabilities, equity, cash, EPS, shares, R&D — each resolved to the concept the filer CURRENTLY reports under, with retired concepts listed separately as stale). Send the company as `ticker_or_cik`; `cik` / `ticker` are accepted aliases. A filer with no XBRL facts (a fund, a trust, a foreign private issuer on paper forms) still returns its filings, with `financials_status: \"unavailable\"` and a reason, not an error. Drill down from here: edgar_filing_text for a filing's text, edgar_company_concept for one metric's multi-year history, edgar_company_facts for every concept. For a cross-source view (patents, contracts, hiring, news) use entity_profile instead.",
"inputSchema": {
"examples": [
{
"ticker_or_cik": "AAPL"
},
{
"filings_limit": 5,
"form_type": "10-K",
"ticker_or_cik": "NVDA"
}
],
"properties": {
"cik": {
"description": "Alias for `ticker_or_cik` — same thing. The spelling edgar_company_facts and edgar_company_concept use.",
"type": "string"
},
"filings_limit": {
"description": "How many filings to return after the form filter (1-40, default 10).",
"type": "number"
},
"form_type": {
"description": "Which filings to list. Omit for the substantive default set (10-K, 10-K/A, 10-Q, 10-Q/A, 8-K, 20-F, 40-F, 6-K, DEF 14A). Pass one form (\"10-K\") to list only that form, or \"all\" for every form including Form 4 insider filings.",
"type": "string"
},
"ticker": {
"description": "Alias for `ticker_or_cik` — same thing. The spelling edgar_ticker_to_cik uses.",
"type": "string"
},
"ticker_or_cik": {
"description": "REQUIRED (or one of its aliases `cik` / `ticker`). Ticker (\"AAPL\"), company name (\"Apple Inc\") or CIK (\"320193\"). Tickers and names are resolved to a CIK internally.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_company_snapshot"
},
{
"description": "AUTHORITATIVE list of the SEC filing documents inside ONE specific filing, by accession number. Retrieve a filing / its contents / attachments: pass the accession (e.g. \"0000320193-25-000079\", with or without dashes) plus the filer's ticker (\"AAPL\") or CIK (\"320193\"). Returns every document in the filing folder — the primary document (10-K / 10-Q / 8-K body), all exhibits, and XBRL files — each with name, type, size, and a direct https URL, plus the filing's form type, filing date, and human -index.html page. Set include_primary_text:true to also pull the primary document's text (HTML stripped to plaintext, ~40k chars). Use to list a 10-K / 10-Q / 8-K's exhibits, retrieve filing contents/attachments, or fetch the text of a filing. You can pass an exact accession, OR just a ticker + form_type to auto-resolve the latest matching filing (no accession lookup needed). Examples: edgar_filing_documents({ticker: \"NVDA\", form_type: \"10-K\"}) for the documents in NVIDIA's latest annual report; edgar_filing_documents({accession: \"0000320193-25-000079\", ticker: \"AAPL\", include_primary_text: true}) for a specific filing's text.",
"inputSchema": {
"examples": [
{
"form_type": "10-K",
"include_primary_text": true,
"ticker": "AAPL"
},
{
"accession": "0000320193-25-000079",
"ticker": "AAPL"
}
],
"properties": {
"accession": {
"description": "Optional SEC accession number of a specific filing, with or without dashes (e.g. \"0000320193-25-000079\"). Omit it to auto-resolve the latest filing — pass form_type instead, and the response will say `accession_source:\"auto_selected\"` and list under `auto_selected.candidates` the other filings you might have meant. If the question names WHICH filing (a date, \"the September 29 8-K\"), pass `filed` or the accession rather than relying on that choice.",
"type": "string"
},
"cik": {
"description": "The filer's CIK number (e.g. \"320193\"). Provide this OR ticker.",
"type": "string"
},
"filed": {
"description": "Only consider filings filed on this date, in this month, or in this year — \"2026-09-29\", \"2026-09\", \"2026\" (US spellings \"09/29/2026\" and \"September 29, 2026\" accepted). **Pass this whenever the question names a date** (\"Tesla's September 29 2026 8-K\"): without it the NEWEST filing of that form is used, and for an 8-K that is routinely a different filing.",
"type": "string"
},
"filing_date": {
"description": "Alias for `filed`.",
"type": "string"
},
"form_type": {
"description": "When accession is omitted, the form type of the latest filing to fetch, e.g. \"10-K\", \"10-Q\", \"8-K\", \"DEF 14A\" — or a `|`-separated SET (\"10-K|10-Q\") for \"the most recent of either, whichever is newer\". Omit both accession and form_type to get the single most recent filing of ANY type at all (routine 8-Ks/Form 4s/Form 144s included, not just annual/quarterly reports) — use the `|` set instead when you specifically want the newest 10-K or 10-Q.",
"type": "string"
},
"include_primary_text": {
"description": "When true, also fetch the primary document and return its text (HTML stripped to plaintext, truncated to ~40,000 chars). Default false. For the FULL, pageable document text — or just one section like going-concern/liquidity — use edgar_filing_text instead.",
"type": "boolean"
},
"ticker": {
"description": "The filer's ticker (e.g. \"AAPL\", \"NVDA\") or company name. Provide this OR cik. Tickers are auto-resolved to CIKs.",
"type": "string"
},
"ticker_or_cik": {
"description": "Alias for `ticker` / `cik` — the single-argument spelling edgar_company_filings and edgar_insider_transactions use. Takes either a ticker or a CIK.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_filing_documents"
},
{
"description": "Full text of an EXHIBIT attached to a filing — not the filing's own primary document (use edgar_filing_text for that). This is the only way to read an 8-K's Exhibit 99.1/99.2 press release — a quarterly production-and-delivery report, an earnings release, a KPI update — because the 8-K body itself routinely just says \"see the attached exhibit\" and carries none of the numbers; the figures live in the exhibit document. Pass the filer's `ticker` or `cik` plus either an `accession` (from edgar_company_filings) or a `form_type` to auto-resolve the latest matching filing (defaults to \"8-K\" when both accession and form_type are omitted, since that is overwhelmingly when an exhibit holds the operative content). Set `exhibit` to pick a specific attachment by its SEC-assigned type — \"99.1\", \"99\", \"10.1\" — read off the filing's own document index (case-insensitive, the \"EX-\" prefix optional); omit it to default to the first EX-99.* exhibit, which is the convention Item 2.02 (earnings) and Item 7.01 (Reg FD) 8-Ks use for a press release. When the requested exhibit is not found (or none exists), the response lists every exhibit actually in the filing under `available_exhibits` rather than failing silently. **For a specific number inside the exhibit, pass `search`** (a short phrase likely to appear verbatim, e.g. \"vehicle deliveries\", \"Megapack\", \"energy storage\") the same way edgar_filing_text does — it scans the whole exhibit and returns matching passages ranked by a nearby figure, with `|`-separated phrases for more than one fact in one call; a zero-match search is a real answer when `raw_truncated` is absent (try different wording); with `raw_truncated: true` it is `status: \"not_found_within_scanned_portion\"` and inconclusive and falls back to a word-level match when the exact phrase misses. Without `search`, the exhibit text is returned paged (`max_chars`/`offset`, same convention as edgar_filing_text) since a press release can run several thousand words. Use for \"Tesla's Q3 2026 vehicle deliveries and production\", \"what did $TICKER's earnings press release say about [KPI]\", \"read the exhibit attached to $TICKER's latest 8-K\". Source: U.S. Securities and Exchange Commission, EDGAR filing exhibits (the same primary-source filings edgar_filing_text and edgar_filing_documents read).",
"inputSchema": {
"examples": [
{
"accession": "0001628280-26-064366",
"search": "vehicle deliveries|energy storage",
"ticker": "TSLA"
}
],
"properties": {
"accession": {
"description": "Optional SEC accession number of a specific filing, with or without dashes (e.g. \"0001628280-26-064366\"). Omit it to auto-resolve the latest filing matching form_type (and filed, if given) — the response says `accession_source:\"auto_selected\"` when this happens.",
"type": "string"
},
"cik": {
"description": "The filer's CIK number (e.g. \"1318605\"). Provide this OR ticker.",
"type": "string"
},
"contains": {
"description": "Alias for `search`.",
"type": "string"
},
"exhibit": {
"description": "Which exhibit to read, by its SEC-assigned type — \"99.1\", \"EX-99.1\", \"99\", \"10.1\" (case-insensitive, \"EX-\" prefix optional). Omit to default to the first EX-99.* exhibit (the press-release convention). If nothing matches, the response lists every exhibit the filing actually has under `available_exhibits` instead of failing with no leads.",
"type": "string"
},
"filed": {
"description": "Only consider filings filed on this date, in this month, or in this year — \"2026-10-02\", \"2026-10\", \"2026\" (US spellings accepted). Pass this whenever the question names a date or quarter (\"Tesla's Q3 2026 deliveries report\") — Tesla and most large filers submit TWO 8-Ks a quarter (a day-2 production-and-delivery release, then a day-~22 full earnings release), so without a date the newest one is used and it may not be the one the question means.",
"type": "string"
},
"filing_date": {
"description": "Alias for `filed`.",
"type": "string"
},
"find": {
"description": "Alias for `search`.",
"type": "string"
},
"form_type": {
"description": "When accession is omitted, the form type of the filing to resolve — \"8-K\", \"10-K\", \"10-Q\", etc., or a `|`-separated set. Defaults to \"8-K\" when both accession and form_type are omitted, since an exhibit holding the operative content (a press release) is overwhelmingly an 8-K attachment.",
"type": "string"
},
"max_chars": {
"description": "Max characters to return in this page when `search` is not used (1000–100000, default 50000). Text past this is available via next_offset.",
"type": "number"
},
"offset": {
"description": "Character offset to start from when `search` is not used (default 0). Pass the prior result's next_offset to page forward.",
"type": "number"
},
"phrase": {
"description": "Alias for `search`.",
"type": "string"
},
"search": {
"description": "Find a specific fact instead of paging blind — same convention as edgar_filing_text's `search`. A short 2-4 word phrase likely to appear VERBATIM (e.g. \"vehicle deliveries\", \"energy storage deployments\"), case-insensitive, scanned over the WHOLE exhibit text before any paging. Falls back to a word-level match (reported as such) when the exact phrase has no match. Separate multiple facts with `|` (e.g. \"vehicle deliveries|energy storage deployments\") to get both from this one exhibit in one call, each reported independently under `searches[]`.",
"type": "string"
},
"ticker": {
"description": "The filer's ticker (e.g. \"TSLA\") or company name. Provide this OR cik. Tickers are auto-resolved to CIKs.",
"type": "string"
},
"ticker_or_cik": {
"description": "Alias for `ticker` / `cik` — the single-argument spelling edgar_filing_documents and edgar_filing_text use. Takes either a ticker or a CIK.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_filing_exhibit_text"
},
{
"description": "AUTHORITATIVE full text of a SEC filing's primary document (10-K / 10-Q / 8-K body), HTML stripped to clean plaintext — the source for disclosures that live in prose, not XBRL: going-concern language, ATM / at-the-market equity facilities, committed-equity share caps, public-float figures, subsequent events, the liquidity footnote, and MD&A KPIs XBRL never tags (test volume, units shipped, subscriber counts, same-store sales). Pass an accession (from edgar_search_filings / edgar_company_filings) plus the filer's ticker or CIK; OR omit accession and pass ticker + form_type to auto-resolve the latest matching filing. **For a specific fact inside a long filing, pass `search`** (a word or exact phrase, e.g. \"tests processed\" or \"processed approximately\") instead of paging blind — it scans the WHOLE document (before any offset/max_chars windowing) and returns every matching passage with surrounding context and its own `offset` in the document, so a KPI ~100k characters in is found in one call instead of paging through `max_chars` windows by hand. A zero-match `search` on a fully-read document (`status: \"not_found\"`) is a real answer (the filing does not use that exact wording) — retry with a shorter or different phrase rather than assuming the tool failed. On a `raw_truncated` document a zero is `status: \"not_found_within_scanned_portion\"`: the phrase was not found in the first `scanned_chars` characters, which is NOT evidence the filing lacks it. A `search` response carries ONLY the matched passages, so it reports `returned_chars` against `total_chars` and sets `truncated:true` whenever those differ — read a figure's absence from it as \"the phrase did not match there\", never as \"the filing does not say it\", and re-read without `search` (or at a passage `offset`) to confirm. (Do not read `search.truncated` as a completeness signal: it is about the SEARCH — false means every distinct match location was returned — and is routinely false on a response holding a third of the document.) **For a question asking two facts from the same filing** (\"revenue and test volume in the latest 10-Q\"), pass `search` as `|`-separated phrases (e.g. \"revenue|tests processed\") to get both in this one call under `searches[]` — and when a phrase names a financial total (revenue, net income, EPS, ...), the matching XBRL figure for this exact accession comes back under `xbrl` even if that total never appears as an absolute number in the prose (common: filings often state only the growth delta/percentage in text). Optionally set `section` to return just one part (going_concern | liquidity | capital_resources | subsequent_events | risk_factors — 10-K Item 1A, bounded from its heading to the next Item heading, table-of-contents hits and cross-references skipped; the response carries `section_diagnostics` with its length and where it ended); `search` runs within that slice when both are given. Large docs (a 10-Q is ~100k+ chars of text) are PAGED, not spilled, when `search` is not used: the result caps at `max_chars` (default 50000) from `offset`, and returns `truncated` + `next_offset` — pass next_offset back as `offset` to read the next window. An especially large filing (e.g. an S-1 with heavy inline-XBRL tagging can exceed 10MB of raw HTML) is also capped on the READ side — the response sets `raw_truncated:true` when only the first portion of the document was read at all, which bounds how far `offset` can page (and how far `search` can scan) and can make a late section or search term come back not-found even though it exists further in. Use for \"does $TICKER disclose substantial doubt / going concern\", \"what ATM facility does $TICKER have\", \"read the liquidity section of the latest 10-Q\", \"how many tests did $TICKER process this quarter\". For the list of documents/exhibits in a filing use edgar_filing_documents; for structured financial numbers use edgar_company_concept.",
"inputSchema": {
"examples": [
{
"form_type": "10-Q",
"section": "liquidity",
"ticker": "ACTU"
},
{
"form_type": "10-K",
"section": "risk_factors",
"ticker": "AAPL"
},
{
"accession": "0001683168-26-003909",
"cik": "1652935",
"max_chars": 30000,
"section": "going_concern"
},
{
"accession": "0001628280-26-054525",
"search": "processed approximately",
"ticker": "NTRA"
}
],
"properties": {
"accession": {
"description": "SEC accession number, dashed or not (e.g. \"0001683168-26-003909\"). Omit to auto-resolve the latest filing of form_type for the given ticker/cik — the response then says `accession_source:\"auto_selected\"` and lists under `auto_selected.candidates` the other filings you might have meant. If the question names WHICH filing (a date, \"the September 29 8-K\"), pass `filed` or an accession instead of relying on that choice.",
"type": "string"
},
"cik": {
"description": "Filer CIK number (e.g. \"1652935\"). Provide this OR ticker.",
"type": "string"
},
"contains": {
"description": "Alias for `search`.",
"type": "string"
},
"filed": {
"description": "Only consider filings filed on this date, in this month, or in this year — \"2026-09-29\", \"2026-09\", \"2026\" (US spellings \"09/29/2026\" and \"September 29, 2026\" accepted). **Pass this whenever the question names a date** (\"Tesla's September 29 2026 8-K\"): without it the NEWEST filing of that form is read, and for an 8-K that is routinely a different filing — verified live 2026-10-18, the newest TSLA 8-K was six days later, 3,061 chars, and contained none of the credit-facility figures asked about.",
"type": "string"
},
"filing_date": {
"description": "Alias for `filed`.",
"type": "string"
},
"find": {
"description": "Alias for `search`.",
"type": "string"
},
"form_type": {
"description": "When accession is omitted, the form type of the latest filing to fetch — \"10-K\", \"10-Q\", \"8-K\", \"DEF 14A\", etc. For \"the most recent 10-K OR 10-Q\" (or any \"whichever of these is newer\" question), pass a `|`-separated SET, e.g. \"10-K|10-Q\" — do NOT guess a single type (\"10-K\" by habit skips a newer 10-Q) and do NOT omit this field to get \"any type\", since a company files far more 8-Ks/Form 4s/Form 144s between annual or quarterly reports than it files the reports themselves and an empty form_type returns the single most recent filing of ANY kind (verified live 2026-09-25, fleet #2450: NTRA's single most recent SEC filing was a Form 144 insider-sale notice, filed weeks after its real 10-Q and completely unrelated to the question asked).",
"type": "string"
},
"max_chars": {
"description": "Max characters to return in this page (1000–100000, default 50000). Doc text past this is available via next_offset.",
"type": "number"
},
"offset": {
"description": "Character offset to start from (default 0). Pass the prior result's next_offset to page forward.",
"type": "number"
},
"phrase": {
"description": "Alias for `search`.",
"type": "string"
},
"search": {
"description": "Find a specific fact instead of paging blind. Pass a short 2-4 word phrase likely to appear VERBATIM in the prose (\"processed approximately\", \"tests processed\", \"going concern\") rather than restating the question. Case-insensitive substring match over the WHOLE document text (or the whole `section` slice), run BEFORE max_chars/offset windowing; returns matching passages (context + their own offset) instead of the paged `text`, ranking passages with a nearby figure first. If a multi-word phrase has no verbatim match, it falls back to the phrase's individual words and returns the passages holding the most of them (search.match_mode \"words\") — read those passages for the fact rather than treating them as confirmed. Use a returned offset with a follow-up call (no `search`) to read more surrounding text. **For TWO OR MORE facts from this same filing in one call, separate phrases with `|`** (e.g. \"Signatera revenue|tests processed\") — each is searched independently and reported under `searches[]`, keyed by `phrase`, instead of the singular `search`. This is the way to answer a compound question (\"what was revenue AND test volume in the latest 10-Q\") without a second call. Note: a phrase naming a financial TOTAL (revenue, net income, EPS, assets, cash, gross/operating profit, long-term debt, stockholders equity, shares outstanding) often has NO verbatim match at all, because filers frequently state only the growth delta/percentage in prose and report the actual total exclusively in XBRL — when a phrase names one of these, the response also attaches that concept's value for THIS SAME accession under `xbrl` (sourced like edgar_company_concept, not text-matched), so you don't need a separate edgar_company_concept call just to get the number the text search alone would report as a false \"not found\". Accepted aliases: `contains`, `find`, `phrase`.",
"type": "string"
},
"section": {
"description": "Return only this section (located by heading). Omit for the whole document. Unmatched sections fall back to the whole document (section_found:false). risk_factors applies to 10-K text only and is the filer-written wording, untagged: it is not a classification of the risks.",
"enum": [
"going_concern",
"liquidity",
"capital_resources",
"subsequent_events",
"risk_factors"
],
"type": "string"
},
"ticker": {
"description": "Filer ticker (e.g. \"ACTU\"). Provide this OR cik. ONLY pass a ticker you are CERTAIN of — a wrong remembered ticker silently retrieves a DIFFERENT company's filing as a clean success (a \"SpaceX\" question filled with SPCE returns Virgin Galactic's S-1). For a recent IPO or any uncertain ticker, resolve first: edgar_company_filings accepts the company NAME and returns the cik — pass that cik here.",
"type": "string"
},
"ticker_or_cik": {
"description": "Alias for `ticker` / `cik` — the single-argument spelling edgar_company_filings and edgar_insider_transactions use. Takes either a ticker or a CIK.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_filing_text"
},
{
"description": "AUTHORITATIVE portfolio holdings of a US ETF or mutual fund (SEC Form N-PORT) — what the fund actually owns. Pass the FUND's ticker (e.g. \"ARKK\", \"QQQ\", \"VTI\", \"VOO\", \"IVV\"). Returns the latest monthly portfolio: net assets, holdings count, and top positions by weight — each with name, CUSIP, value (USD), and % of fund. Use for \"what does ARKK hold\", \"top holdings of QQQ\", \"is $STOCK in VTI\". Distinct from edgar_institutional_holdings (13F = what an investment MANAGER like Berkshire owns); this is a registered fund's own N-PORT. Covers US-registered open-end funds + ETFs; data is ~30-60 days delayed. Note: a few legacy ETFs structured as unit investment trusts (e.g. SPY, DIA) don't file N-PORT and won't resolve — use IVV or VOO for S&P 500 exposure.",
"inputSchema": {
"examples": [
{
"limit": 25,
"ticker": "ARKK"
},
{
"limit": 10,
"ticker": "QQQ"
}
],
"properties": {
"limit": {
"description": "Top N holdings by weight to return (1-100, default 25)",
"type": "number"
},
"ticker": {
"description": "REQUIRED (or its alias `ticker_or_cik`). ETF or mutual-fund ticker (e.g. \"ARKK\", \"SPY\", \"QQQ\"). Fund tickers, not company stock tickers.",
"type": "string"
},
"ticker_or_cik": {
"description": "Alias for `ticker` — the spelling sibling SEC tools (edgar_company_filings, edgar_insider_transactions) use. Must still be a FUND ticker: N-PORT funds are keyed by ticker, so a bare CIK will not resolve here.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_fund_holdings"
},
{
"description": "AUTHORITATIVE insider trading activity (SEC Form 3/4/5) for a US public company — who bought or sold, how many shares, at what price, and what they hold now. Send the company as `ticker_or_cik` — a ticker (\"TSLA\") or a CIK — and `cik` / `ticker` are accepted as aliases for it. Returns each recent Form 4 filing parsed into structured transactions: reporting owner + role (director/officer/10% holder), transaction code (P=open-market purchase, S=sale, A=grant/award, M=option exercise, G=gift, F=tax-withholding), shares, price per share, acquired/disposed, and shares owned after. Use for \"insider buying at $TICKER\", \"did executives sell recently\", \"latest Form 4 activity\". Open-market purchases (code P) are the strongest conviction signal; awards (code A) are routine comp. For the raw filing list use edgar_company_filings with form_type:\"4\".",
"inputSchema": {
"examples": [
{
"limit": 10,
"ticker_or_cik": "TSLA"
},
{
"include_derivatives": true,
"ticker_or_cik": "1318605"
}
],
"properties": {
"cik": {
"description": "Alias for `ticker_or_cik` — the spelling edgar_company_concept and edgar_company_facts use for the same thing. Takes a ticker or a CIK.",
"type": "string"
},
"include_derivatives": {
"description": "Also include derivative (options/RSU) transactions. Default false (non-derivative common-stock only).",
"type": "boolean"
},
"limit": {
"description": "Max Form 4/3/5 filings to parse (1-25, default 10)",
"type": "number"
},
"ticker": {
"description": "Alias for `ticker_or_cik` — the spelling edgar_fund_holdings and edgar_ticker_to_cik use for the same thing. Takes a ticker or a CIK.",
"type": "string"
},
"ticker_or_cik": {
"description": "REQUIRED (or one of its aliases `cik` / `ticker`). Ticker symbol (e.g., \"TSLA\") or CIK number (e.g., \"1318605\")",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_insider_transactions"
},
{
"description": "AUTHORITATIVE stock portfolio of a large institutional investor (SEC Form 13F-HR) — what a fund/manager owns, share counts, and position values. Pass the MANAGER's ticker or CIK (e.g. \"BRK-B\" or CIK \"1067983\" for Berkshire Hathaway; \"1350694\" for Bridgewater). Returns the latest quarterly 13F: top holdings aggregated by issuer with value (USD), shares, and % of portfolio, plus the report period. Use for \"what does Berkshire own\", \"Bridgewater's biggest positions\", \"which funds hold $TICKER\" (run per manager). Note: 13F covers US-listed long equity + options held by managers with >$100M AUM, filed ~45 days after quarter-end; it excludes shorts, cash, and non-US holdings. Values are whole USD for filings since 2023; older ones are in thousands. IMPORTANT: rows carry a `put_call` field and a plain-English `direction`. A `put` row is a BEARISH bet AGAINST that issuer — never report it as a holding the manager owns — and for option rows the value is the underlying's notional, not premium or capital at risk. Rank real holdings by `pct_of_long_equity`, and read `position_summary` + `interpretation_note` before summarising.",
"inputSchema": {
"examples": [
{
"limit": 25,
"ticker_or_cik": "BRK-B"
},
{
"limit": 50,
"ticker_or_cik": "1067983"
}
],
"properties": {
"cik": {
"description": "Alias for `ticker_or_cik` — the spelling edgar_company_concept and edgar_company_facts use for the same thing. Takes a ticker or a CIK.",
"type": "string"
},
"limit": {
"description": "Top N holdings by value to return (1-100, default 25)",
"type": "number"
},
"ticker": {
"description": "Alias for `ticker_or_cik` — the spelling edgar_fund_holdings and edgar_ticker_to_cik use for the same thing. Takes a ticker or a CIK.",
"type": "string"
},
"ticker_or_cik": {
"description": "REQUIRED (or one of its aliases `cik` / `ticker`). The institutional manager's ticker (e.g. \"BRK-B\") or CIK (e.g. \"1067983\"). NOT the held stock — the fund/manager doing the filing.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_institutional_holdings"
},
{
"description": "PRODUCT-LEVEL or segment-level revenue as STRUCTURED data — e.g. \"how much revenue did Keytruda generate\", \"AAPL revenue by product line\". Regular XBRL tools (edgar_company_concept, edgar_company_facts) only expose UNDIMENSIONED totals; a filer's product/segment breakdown is tagged with an XBRL dimension (e.g. a \"Keytruda [Member]\"), which those APIs cannot see no matter which concept is requested. This tool reads SEC's own standardized \"Financial Report\" rendering of that dimensional data straight out of the annual or quarterly segment-reporting / revenue-disaggregation note — 10-K and 10-Q for US filers, 20-F for foreign private issuers (Novartis, AstraZeneca, GSK, Sanofi, Novo Nordisk, Takeda) and 40-F for Canadian MJDS filers, resolved automatically and reported back as `resolved_form` — the same note human analysts read, but pre-parsed into rows. Pass `product_filter` (case-insensitive substring, matched against the dimension breadcrumb, e.g. \"Keytruda\") to get just one product/segment instead of the whole table. Every result carries a citation (accession, filing date, exact report + URL it came from). Not every filer discloses product-level revenue in XBRL, and a small fraction use a non-standard table layout this parser can't read — both are reported as an explicit status rather than a silent empty array, with a fallback to edgar_filing_text for the prose note.",
"inputSchema": {
"examples": [
{
"product_filter": "Keytruda",
"ticker_or_cik": "MRK"
},
{
"product_filter": "Entresto",
"ticker_or_cik": "NVS"
}
],
"properties": {
"accession": {
"description": "Optional exact accession number (from edgar_company_filings) to read a specific past filing instead of the latest matching form_type.",
"type": "string"
},
"cik": {
"description": "Alias for `ticker_or_cik` — the spelling edgar_company_concept and edgar_company_facts use for the same thing. Takes a ticker or a CIK.",
"type": "string"
},
"form_type": {
"description": "Filing type to read the note from. Omit it to try 10-K, then 20-F, then 40-F automatically — foreign private issuers (NVS, AZN, GSK, SNY, NVO, TAK) file 20-F and Canadian MJDS filers file 40-F. \"10-Q\" also works for filers that disaggregate revenue quarterly. The form actually used comes back as `resolved_form`.",
"type": "string"
},
"limit": {
"description": "Max rows to return (1-200, default 100).",
"type": "number"
},
"product_filter": {
"description": "Optional case-insensitive substring to match against the product/segment dimension, e.g. \"Keytruda\". Omit to get every disaggregated row in the table.",
"type": "string"
},
"ticker": {
"description": "Alias for `ticker_or_cik` — the spelling edgar_fund_holdings and edgar_ticker_to_cik use for the same thing. Takes a ticker or a CIK.",
"type": "string"
},
"ticker_or_cik": {
"description": "REQUIRED (or one of its aliases `cik` / `ticker`). Ticker (e.g. \"MRK\") or CIK (e.g. \"310158\"). Tickers are auto-resolved.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_product_revenue"
},
{
"description": "PREFER OVER WEB SEARCH for \"what did $COMPANY say about X in their SEC filings\" or \"find filings that mention Y\". AUTHORITATIVE full-text search across every SEC filing — EDGAR's own search index. Filter by form type (\"10-K\" annual, \"10-Q\" quarterly, \"8-K\" current event, \"DEF 14A\" proxy, \"S-1\" / \"S-1/A\" / \"F-1\" IPO registration statement, \"424B4\" final IPO prospectus), date range, and optionally one filer (`entity`). **Also the way to FIND AN IPO FILING BY COMPANY NAME or by day** — \"find Anthropic S-1\", \"S-1 registration statements filed today\", \"IPO filing for <company>\": pass `form_type:\"S-1\"` and the company name as `query` (or `query:\"registration statement\"` with `start_date` for a day's filers). A company that has only just registered has no ticker yet, so edgar_company_filings cannot resolve it by name; this tool can. Returns `total_hits` FIRST — the true match count for your filters, independent of how many rows you asked for — then entity name, CIK, form type, filing/period dates, location, accession number (feed straight into edgar_filing_text / edgar_filing_documents — no second lookup), and — for 8-K results — the `items` array of item codes (e.g. \"3.01\" listing deficiency vs \"1.01\" material agreement vs \"3.02\" unregistered sale), which carry the actual signal. **This tool does not return a text snippet** — EDGAR's search index itself returns none — so for the matching passage, chain the `accession` into edgar_filing_text with `search` set to your query (or a shorter phrase from it); that reads the actual filing and returns the surrounding text in a second call, rather than this one fetching every hit's document on your behalf (SEC rate-limits the whole fleet by IP, so a search call stays a single request). A zero-hit response names every filter you passed rather than an empty array, so you can tell \"nothing matches\" from \"a filter was silently dropped\". Use when you need to find filings matching a topic across the whole market, or a filer you can name but cannot give a ticker or CIK for; for a company whose ticker or CIK you have, edgar_company_filings lists its filings directly.",
"inputSchema": {
"examples": [
{
"end_date": "2024-12-31",
"form_type": "10-K",
"limit": 20,
"query": "artificial intelligence",
"start_date": "2024-01-01"
},
{
"limit": 10,
"query": "Tesla revenue"
},
{
"entity": "AAPL",
"limit": 3,
"query": "artificial intelligence"
}
],
"properties": {
"cik": {
"description": "Alias for `entity`.",
"type": "string"
},
"end_date": {
"description": "End date in YYYY-MM-DD format (e.g., \"2024-12-31\"). If you pass this without `start_date`, `start_date` is defaulted to EDGAR full-text search's coverage floor (2001-01-01) rather than silently ignored.",
"type": "string"
},
"entity": {
"description": "Narrow results to ONE filer, by ticker (\"AAPL\"), company name (\"Apple Inc.\"), or CIK (\"320193\") — omit to search across every filer. Aliases `ticker_or_cik` / `cik` / `ticker` are also accepted, the spellings this pack's other tools use for the same thing.",
"type": "string"
},
"form_type": {
"description": "Filter by SEC form type (e.g., \"10-K\", \"10-Q\", \"8-K\", \"DEF 14A\", \"S-1\" for an IPO registration statement, \"424B4\" for the final IPO prospectus). Omit for all types.",
"type": "string"
},
"limit": {
"description": "Number of results to return (1-40, default 10)",
"type": "number"
},
"query": {
"description": "Search query (e.g., \"artificial intelligence\", \"Tesla revenue\")",
"type": "string"
},
"start_date": {
"description": "Start date in YYYY-MM-DD format (e.g., \"2024-01-01\"). If you pass this without `end_date`, `end_date` is defaulted to today rather than silently ignored.",
"type": "string"
},
"ticker": {
"description": "Alias for `entity`.",
"type": "string"
},
"ticker_or_cik": {
"description": "Alias for `entity`.",
"type": "string"
}
},
"required": [
"query"
],
"type": "object"
},
"name": "edgar_search_filings"
},
{
"description": "Resolve a US stock ticker (e.g. \"TSLA\") OR a company name (e.g. \"Tesla\", \"Apple Inc\") to the SEC's 10-digit CIK identifier — required by every other SEC tool. Call THIS FIRST when you have a ticker/name and need to use edgar_company_concept, edgar_company_filings, edgar_company_facts, sec_8k_recent, or any other SEC-keyed tool. Returns {cik, cik_padded, company_name, ticker, matched_by}; when matched by name it also returns `alternatives` — up to 3 OTHER companies whose names also matched, one per distinct CIK, with the winner's OWN share classes/tickers excluded (never listed as its own alternative). Use `alternatives` to tell a genuinely CONTESTED name match (a real rival company also matched) from a clean one (nothing else did). Cheap, no rate limit concerns. Most other tools also accept tickers/names directly and call this internally — only use it explicitly when you want the CIK as data. The response carries a `next` hint: the usual NEXT step after resolving is edgar_company_snapshot({ticker_or_cik}), which returns the recent filings list AND the headline XBRL financials in one call — do not chain edgar_company_filings then edgar_company_concept by hand to get that.",
"inputSchema": {
"examples": [
{
"ticker": "AAPL"
},
{
"ticker": "TSLA"
}
],
"properties": {
"company": {
"description": "Alias for `ticker` — use it when what you have is a company NAME (\"Apple Inc.\") rather than a symbol. Same argument, same behaviour.",
"type": "string"
},
"ticker": {
"description": "REQUIRED (or one of its aliases `ticker_or_cik` / `company`). Stock ticker symbol (e.g., \"AAPL\", \"MSFT\", \"TSLA\") or company name (e.g., \"Apple\", \"Microsoft\")",
"type": "string"
},
"ticker_or_cik": {
"description": "Alias for `ticker` — the spelling edgar_company_filings and edgar_insider_transactions use. A ticker or company name; this tool RESOLVES to a CIK, so passing a bare CIK has nothing to look up.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "edgar_ticker_to_cik"
},
{
"description": "Compare ONE financial metric across ALL public companies for a single period (SEC XBRL \"frames\"). PREFER OVER WEB SEARCH for \"which companies had the most revenue/net income/assets in <year>\", \"rank companies by <metric>\", cross-company financial comparison. concept is a US-GAAP tag (e.g. \"Revenues\", \"NetIncomeLoss\", \"Assets\", \"ResearchAndDevelopmentExpense\", \"CashAndCashEquivalentsAtCarryingValue\"). period is a calendar frame: \"CY2023\" (annual), \"CY2023Q1\" (quarter), or \"CY2023Q1I\" (instant/balance-sheet, period-end). Returns companies + values, sorted descending by default. Differs from edgar_company_concept (one company over time) — this is one period across every filer.",
"inputSchema": {
"examples": [
{
"concept": "Revenues",
"limit": 25,
"period": "CY2024"
},
{
"concept": "ResearchAndDevelopmentExpense",
"limit": 50,
"period": "CY2024Q1",
"sort": "desc"
}
],
"properties": {
"concept": {
"description": "US-GAAP (or dei) tag, e.g. \"Revenues\", \"NetIncomeLoss\", \"Assets\", \"ResearchAndDevelopmentExpense\".",
"type": "string"
},
"limit": {
"description": "Max companies to return (1-200, default 25).",
"type": "number"
},
"period": {
"description": "Calendar frame: \"CY2023\" (annual duration), \"CY2023Q1\" (quarterly duration), or \"CY2023Q1I\" (instant, balance-sheet items at period end).",
"type": "string"
},
"sort": {
"description": "\"desc\" (default, largest first) or \"asc\".",
"enum": [
"desc",
"asc"
],
"type": "string"
},
"taxonomy": {
"description": "Taxonomy: \"us-gaap\" (default) or \"dei\".",
"type": "string"
},
"unit": {
"description": "Unit of measure (default \"USD\"). Use \"shares\" for share counts, \"USD-per-shares\" for per-share.",
"type": "string"
}
},
"required": [
"concept",
"period"
],
"type": "object"
},
"name": "edgar_xbrl_frames"
},
{
"description": "\"Tell me about X\" / \"research Acme\" / \"brief me on Tesla\" / \"what does Apple do\" / \"company profile for Microsoft\" / \"give me the rundown on NVDA\" / \"everything you know about $TICKER\" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA), news and GLEIF, and returns: cik + company_name (+ resolved_from/resolved_to when `value` was a name); recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (the latest ANNUAL Revenues, NetIncomeLoss, Cash, diluted EPS, capex and operating cash flow, each with its period_end, SEC form and the accession of the filing it came from — plus EntityCommonStockSharesOutstanding, which is the newest COVER-PAGE share count the filer has published rather than an annual one, so its period_end is a cover date after the quarter closed and it is the right per-share denominator; a filer tagging a fallback concept appears under the name of that tag instead, e.g. PaymentsToAcquireProductiveAssets instead of PaymentsToAcquirePropertyPlantAndEquipment); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); federal_contracts (USAspending awards where the company is the recipient); fda_products (FDA-licensed biologics — vaccines, cell/gene therapies — from the Purple Book; a company with only small-molecule/generic drugs will show none here, that is expected, not a failure); hiring (H-1B sponsorship volume + salary range from DOL LCA filings); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. `sources_used` / `sources_failed` say which of these actually returned data for THIS company — an empty section is a real \"no data\", not a bug. `sources_skipped` is the third state: a leg we deliberately did NOT run, each entry carrying a `reason` token and a plain-English `detail` (the Purple Book is skipped for a filer SEC classifies outside the life-science SIC bands, since it lists only 351(a)/(k) biologics licence holders). Pass a ticker (\"AAPL\"), zero-padded CIK (\"0000320193\"), OR a company name (\"Moderna\") — names now resolve via SEC EDGAR's company-name match; a private company (no CIK/ticker) returns resolved:false with an explicit `notes` line, not a bare failure. `type` accepts \"company\" or \"ticker\" interchangeably — both take the same `value` shapes above.",
"inputSchema": {
"examples": [
{
"type": "company",
"value": "AAPL"
}
],
"properties": {
"country": {
"description": "OPTIONAL ISO 3166-1 alpha-2 of the business register you mean (\"NO\", \"FI\", \"GB\", \"JP\", \"FR\", \"EE\", \"BR\"). Only affects a NAME lookup, and is often what separates the company you mean from a US namesake. When a name resolves to a register entity with no CIK, the SEC/CIK-keyed sections are reported under `sources_skipped` with reason `not_queried` — they were never asked, which is not the same as having failed.",
"type": "string"
},
"type": {
"description": "\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.",
"enum": [
"company",
"ticker"
],
"type": "string"
},
"value": {
"description": "Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\"). A NAME now resolves through the national business registers as well as SEC EDGAR, so a non-US company returns its register identity and record rather than `resolved: false`.",
"type": "string"
}
},
"required": [
"type",
"value"
],
"type": "object"
},
"name": "entity_profile"
},
{
"description": "The REVERSE of sponsor_to_filer: given a US-listed public FILER (parent company), list its operating subsidiaries as disclosed in Exhibit 21 of its most recent 10-K (Item 601(b)(21) — \"significant subsidiaries\"). Built for the same trial-sponsor/entity-resolution join, run the other direction: instead of ~10 calls guessing candidate subsidiary names and confirming each via sponsor_to_filer, get the parent's full disclosed subsidiary list (with jurisdiction of incorporation) in one call, straight from SEC — e.g. Merck (MRK/CIK 310158) -> \"Merck Sharp & Dohme LLC\" among hundreds of others. Pass `name_filter` (case-insensitive substring) to check whether a specific candidate name is among the subsidiaries without reading the whole list. Every result carries provenance (accession number, filing date, exhibit URL) so the join is auditable. Smaller filers or ones with no significant subsidiaries can genuinely have no Exhibit 21 — status distinguishes that from a lookup failure. Foreign private issuers (20-F filers) are not yet covered.",
"inputSchema": {
"examples": [
{
"ticker_or_cik": "MRK"
},
{
"name_filter": "Sharp & Dohme",
"ticker_or_cik": "310158"
}
],
"properties": {
"cik": {
"description": "Alias for `ticker_or_cik` — the spelling edgar_company_concept and edgar_company_facts use for the same thing. Takes a ticker or a CIK.",
"type": "string"
},
"limit": {
"description": "Max subsidiaries to return (1-500, default 200). Large parents can disclose 500+.",
"type": "number"
},
"name_filter": {
"description": "Optional case-insensitive substring to filter subsidiary names by, e.g. \"Sharp & Dohme\" to check whether that entity is among the parent's disclosed subsidiaries. Subsidiary names in Exhibit 21 use \"&\", not \"and\".",
"type": "string"
},
"ticker": {
"description": "Alias for `ticker_or_cik` — the spelling edgar_fund_holdings and edgar_ticker_to_cik use for the same thing. Takes a ticker or a CIK.",
"type": "string"
},
"ticker_or_cik": {
"description": "REQUIRED (or one of its aliases `cik` / `ticker`). The PARENT company's ticker (e.g. \"MRK\") or CIK (e.g. \"310158\"). Tickers are auto-resolved to CIKs.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "filer_to_sponsors"
},
{
"description": "Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.",
"inputSchema": {
"examples": [
{
"key": "user_research_topic"
}
],
"properties": {
"k": {
"description": "Alias for key.",
"type": "string"
},
"key": {
"description": "Memory key to delete. Accepts name, k, label as aliases.",
"type": "string"
},
"label": {
"description": "Alias for key.",
"type": "string"
},
"name": {
"description": "Alias for key.",
"type": "string"
}
},
"required": [
"key"
],
"type": "object"
},
"name": "forget"
},
{
"description": "Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor.",
"inputSchema": {
"examples": [
{
"url": "https://pipeworx.io"
}
],
"properties": {
"max_links": {
"description": "Maximum number of link entries to include (default 25, max 50).",
"type": "number"
},
"url": {
"description": "Full URL of the site to summarize, e.g. \"https://example.com\" or a specific landing page.",
"type": "string"
}
},
"required": [
"url"
],
"type": "object"
},
"name": "generate_llms_txt"
},
{
"description": "Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob (mid), forecast_prob, and edge_pp per strike, plus the settlement clause verbatim. BACKTEST (`backtest_days: N`): scores an archived gridded forecast against the market on settled days and returns brier_market vs brier_forecast with a plain-English `verdict`, so the edge is MEASURED rather than asserted. READ THE WARNINGS — they are not boilerplate. (1) These markets DO NOT settle on the NWS. They settle on The Weather Company (weather.com) at a Kalshi station code such as CLINYC, which the response quotes verbatim; so part of every edge_pp is NWS-vs-Weather-Company disagreement about the same day at the same station, which is not mispricing and not tradeable. `settlement_vs_forecast_basis_f` from backtest mode is that part as a number. (2) The station is DERIVED from the settlement clause, never from the city name: Chicago settles at MIDWAY and New York at CENTRAL PARK, so a city-centre forecast would misprice a whole ladder. A station that cannot be resolved yields rows with no forecast and a reason, never a guessed coordinate. (3) forecast_prob assumes a normal distribution around the NWS high whose width is ASSUMED, not fitted (stated in `distribution_assumption`) — run backtest mode to see whether it is calibrated. (4) edge_pp is gross: no Kalshi fees, no bid-ask. MEASURED RESULT, AND IT IS NOT THE FLATTERING ONE: on the first backtest (KXHIGHNY, 13 settled days to 2026-09-11, 58 market observations) the MARKET beat the forecast — Brier 0.1008 for the market against 0.1594 for the archived gridded forecast, lower being better. So on that sample there is NO forecast edge to sell, and a large edge_pp is more likely to be the model disagreeing with a better-informed market than an opportunity. The measured settlement-vs-forecast basis was 1.7F mean absolute over 8 pinnable days, slightly warm-biased, which is a big share of a typical edge_pp on a 2-degree bracket. Re-run backtest_days before believing any edge; if a later sample reverses this, the numbers say so. NWS is US-only, so the ~30 international Kalshi weather series (London, Paris, Tokyo) return market prices with forecast_unavailable rather than a forecast. Precipitation series are listed but not yet priced. Cities: nyc, chicago, los angeles, miami, austin, houston, denver, philadelphia — or pass `series_ticker` for any other (e.g. \"KXHIGHTBOS\").",
"inputSchema": {
"examples": [
{
"city": "nyc"
},
{
"city": "chicago"
},
{
"backtest_days": 14,
"series_ticker": "KXHIGHNY"
}
],
"properties": {
"backtest_days": {
"description": "Run measurement mode over the last N settled days (max 60) instead of pricing today. Returns brier_market vs brier_forecast, the settlement-vs-forecast basis, and per-day detail. Both sides are scored at 12:00Z on each event day — before the daily high and before resolution — because a settled market prices the known outcome at close.",
"type": "number"
},
"city": {
"description": "City to price, e.g. \"nyc\", \"chicago\", \"los angeles\", \"miami\", \"austin\", \"houston\", \"denver\", \"philadelphia\". Defaults to nyc. Unmapped cities return known_cities[] rather than a wrong series.",
"type": "string"
},
"date": {
"description": "Settlement date as YYYY-MM-DD. Defaults to the soonest open event. Daily weather markets open ~1-2 days ahead and close 05:00Z the next day.",
"type": "string"
},
"market_type": {
"description": "\"high_temp\" (default) | \"precip\". Precipitation markets return prices but no forecast_prob yet.",
"type": "string"
},
"series_ticker": {
"description": "Explicit Kalshi series, e.g. \"KXHIGHNY\" or \"KXHIGHTBOS\" (Boston). Overrides `city`; use it for any of the 121 daily weather series not in the city list.",
"type": "string"
}
},
"type": "object"
},
"name": "kalshi_weather_edge"
},
{
"description": "List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.",
"inputSchema": {
"properties": {
"include_inactive": {
"description": "Include cancelled subscriptions in the response (default false).",
"type": "boolean"
}
},
"required": [],
"type": "object"
},
"name": "list_subscriptions"
},
{
"description": "Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:\"pwfb_…\"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.",
"inputSchema": {
"examples": [
{
"message": "Fleet #2184 smoke test: verifying pipeworx_feedback example call returns non-empty.",
"type": "other"
}
],
"properties": {
"claim_token": {
"description": "Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.",
"type": "string"
},
"context": {
"description": "Optional structured context: which tool, pack, or vertical this relates to.",
"properties": {
"pack": {
"description": "Pack slug (e.g., \"fred\")",
"type": "string"
},
"tool": {
"description": "Tool name (e.g., \"fred_get_series\")",
"type": "string"
},
"vertical": {
"description": "Vertical (e.g., \"housing\")",
"type": "string"
}
},
"type": "object"
},
"message": {
"description": "Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.",
"type": "string"
},
"type": {
"description": "bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.",
"enum": [
"bug",
"feature",
"data_gap",
"praise",
"other"
],
"type": "string"
}
},
"type": "object"
},
"name": "pipeworx_feedback"
},
{
"description": "What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.",
"inputSchema": {
"examples": [
{
"window": "7d"
}
],
"properties": {
"window": {
"description": "24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.",
"enum": [
"24h",
"7d",
"30d"
],
"type": "string"
}
},
"type": "object"
},
"name": "pipeworx_trending"
},
{
"description": "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}. FEES: every opportunities[] row and partition_check.arbitrage carry edge_pp_gross (== gap_pp / overround_pp), fees_pp, edge_pp_net, net_positive, plus polymarket_fee_pp, fee_basis and fee_categories[]. BOTH cost components are modeled: Polymarket's own per-category TAKER FEE (fee = shares × rate × p × (1-p), rates crypto 0.07 / sports-economics-culture-weather-other 0.05 / finance-politics-mentions-tech 0.04, geopolitics and world events fee-free; verified against Polymarket's own docs as of 2026-09-13) and Polygon gas (~$0.02/leg). The taker fee dominates: ~$1.75 per 100 shares on a crypto market at 50c versus $0.02 of gas, so rows that looked profitable before fleet #1927 may now show net_positive:false — that is the correction, not a regression. Each leg is priced at ITS OWN market's rate and price (the fee curve peaks at 50c and falls toward both extremes). fee_basis says where the rate came from: 'payload' (read off the market, the normal case), 'category' (mapped from its fee category), 'fee_free', or 'fallback' (rate unknown — charged at the modal 0.05 rather than assumed free, so an unreadable market is never reported as costless). Where fill_check reprices against live depth, this does NOT double-count that spread cost. 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.",
"inputSchema": {
"examples": [
{
"topic": "Fed rate decision"
}
],
"properties": {
"event": {
"description": "Single-event mode (use this if you know the specific Polymarket event): event slug like \"fed-decision-may-2026\" or \"when-will-bitcoin-hit-150k\". Full Polymarket URLs also accepted.",
"type": "string"
},
"topic": {
"description": "Cross-event mode (use this if you want to scan related events across the platform): a topic or seed question like \"Fed rate decision\" or \"Strait of Hormuz traffic returns to normal\". Tool searches Polymarket for related events and checks monotonicity across them.",
"type": "string"
}
},
"type": "object"
},
"name": "polymarket_arbitrage"
},
{
"description": "Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers \"how long has this edge existed and is it shrinking?\" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: days (lookback, default 14, max 30), window (snapshot family, default \"1wk\"). RESPONSE: tracked[] = every opportunity in the LATEST snapshot with its full edge_pp_net time-series across prior snapshots, first_seen, trend (new | widening | stable | decaying) and decay_pp_per_day (both computed on |edge_pp_net| — the value itself is signed by trade direction, negative = SELL YES); expired[] = opportunities that appeared in earlier snapshots but are GONE from the latest (closed, resolved, or arbed away) with their lifespan_days — the median lifespan is your competition clock; snapshot_dates[] = which days actually have data (snapshots are written when polymarket_edges runs on a cache-miss, so gaps mean nobody scanned that day). LIMITS: history depth is bounded by the 60-day snapshot TTL and starts from when snapshotting was enabled; decay numbers come from daily closes of edge_pp_net (net of default slippage AND Polymarket's own taker fee — see polymarket_edges), not intraday.",
"inputSchema": {
"examples": [
{
"days": 14,
"window": "1wk"
}
],
"properties": {
"days": {
"description": "Lookback in days (default 14, clamp 2-30).",
"type": "number"
},
"window": {
"description": "Which polymarket_edges window family to read snapshots for: 24hr | 1wk | 1mo (default 1wk).",
"type": "string"
}
},
"type": "object"
},
"name": "polymarket_edge_tracker"
},
{
"description": "Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for \"what should I bet on today\" — agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segment: (1) MODEL_DRIVEN — crypto_price (lognormal barrier from 90d FRED log-returns) and news_momentum (GDELT 7d/21d article-volume ratio, soft signal w/ halved Kelly). (2) STRUCTURAL_ARBITRAGE — partition_overround on mutually-exclusive events; per-leg favorite-longshot bias correction with per-sport α (tennis 1.02, soccer 1.10, MMA 1.15, default 1.0); placeholder-slug filter drops will-person-X / will-team-Y / will-manager-Z / will-someone-else- backstops; partitions with >20% placeholder fraction skipped entirely. (3) CONCENTRATED_LONGSHOT — basket trade when one leg ≥75% AND ≥2 longshots ≤8% AND portfolio return ≥25:1; rare-by-design (gates relaxed Run 8 from prior 85%/5%/50:1). EVERY OPPORTUNITY carries edge_pp_net (net of slippage AND Polymarket's own taker fee — fees_pp_applied itemises the fee component; see fees.ts for the published per-category schedule), kelly_fraction + kelly_fraction_half (capped at 0.25), market.liquidity, market.spread_pp, market.volume, plus a 24h-move warning (\"Market moved X.Xpp in 24h\") when the recent move alone exceeds the edge — your edge may already be in the price. TRADEABLE-EDGE KNOBS: min_liquidity / max_spread_pp drop opportunities where edge isn't realizable; min_partition_leg_kelly filters partitions by best per-leg Kelly. RESPONSE TOP-LEVEL: by_segment{model_driven,structural_arbitrage,concentrated_longshot}, fed_candidates/fed_note (Fed bets surface here, excluded from ranking — 1m-T vs EFFR signal is unreliable at meeting-month horizons without paid OIS/SOFR-futures data), and _diagnostics{concentrated_longshot:{...funnel counters},category_counts,filter_skips} so callers can see WHY a segment is empty (top-N stale, all candidates failed gates, knob dropped them). Cached 1h at the KV level keyed on all knobs.",
"inputSchema": {
"examples": [
{
"limit": 5,
"window": "1wk"
}
],
"properties": {
"category_filter": {
"description": "Comma-separated list to restrict the output: \"model_driven\" (crypto_price + news_momentum), \"structural_arbitrage\" (partition_overround), \"concentrated_longshot\". Combine like \"model_driven,structural_arbitrage\". Default: all.",
"type": "string"
},
"limit": {
"description": "Top N edges to return after ranking. Default 10, max 25.",
"type": "number"
},
"max_spread_pp": {
"description": "Tradeable-edge filter. Maximum bid/ask spread in percentage points on the representative market. Default null (no filter). Set to 2 to require tight books — anything wider eats most plausible edges.",
"type": "number"
},
"min_edge_pp": {
"description": "Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage and Polymarket's own taker fee.",
"type": "number"
},
"min_kelly": {
"description": "Minimum half-Kelly fraction (as decimal, e.g. 0.005 = 0.5% of bankroll) to include single-leg opportunities. Default 0 (no filter). Skips opportunities that are too small to bet sensibly even if the edge is large.",
"type": "number"
},
"min_liquidity": {
"description": "Tradeable-edge filter. Minimum $ liquidity on the representative market (or for partition_overround, on at least one top_leg). Default 0 (no filter). Set to 5000 to drop thin-book opportunities where executing the edge would walk the book past breakeven.",
"type": "number"
},
"min_partition_leg_kelly": {
"description": "Minimum BEST per-leg half-Kelly fraction across a partition_overround opportunity's top_legs (or longshot_basket legs). Default 0 (no filter). Partition arbs always return kelly_fraction_half=0 at the parent level by design (basket trades don't compose to single-leg Kelly), so min_kelly never filters them — this knob applies to the per-leg Kelly inside top_legs instead. Use to suppress thin partitions whose individual leg edges aren't worth the per-leg slippage cost.",
"type": "number"
},
"slippage_pp": {
"description": "Assumed execution slippage in percentage points per leg (default 0.3), for bid/ask + thin depth cost that a last-trade price does not show. Subtracted from raw |edge| before ranking and Kelly sizing, ON TOP OF Polymarket's own taker fee — which is NOT zero (rate 0.04-0.07 depending on category, read off each market's own published fee schedule; see fees_pp_applied on every row and fees.ts for the full schedule). Bump slippage for very thin partitions; drop to 0 if you have a smarter fill model — the fee still applies regardless.",
"type": "number"
},
"window": {
"description": "Polymarket volume window to filter markets. Default 1wk.",
"enum": [
"24hr",
"1wk",
"1mo"
],
"type": "string"
}
},
"type": "object"
},
"name": "polymarket_edges"
},
{
"description": "Realizable-vs-theoretical edge check against live CLOB order-book depth — AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a \"clean\" fill that quietly omitted it as optimistic in the direction that loses money). 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, verdict (clean|degraded|cannot_fill), fee_schedule ({category, taker_rate, exponent, maker_rebate_rate, fees_enabled, basis} — read off THIS market, never assumed free), fee_usd/fee_pp at the actual VWAP fill, breakeven_win_rate_taker (the win probability your side needs just to cover price + fee — ~51.8% on a 50c crypto taker fill, not 50%), breakeven_win_rate_maker (no fee charged to makers — any rebate is in fee_schedule.maker_rebate_rate), and all_in_cost_pp = slippage_pp + fee_pp. 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 and profit_usd — both NET of every leg's own Polymarket taker fee (capture_ratio_gross/profit_usd_gross keep the pre-fee figures; per_leg[].fee_usd itemizes each leg, summed as fees_usd_total), 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). Adverse selection while working resting orders is still not modeled.",
"inputSchema": {
"examples": [
{
"market": "will-the-fed-increase-interest-rates-by-25-bps-after-the-december-2026-meeting-20260729232808636",
"side": "buy_yes",
"size_usd": 1000
}
],
"properties": {
"event": {
"description": "Basket mode: event slug or full polymarket.com URL — checks every leg of the partition.",
"type": "string"
},
"market": {
"description": "Single-market mode: market slug or full polymarket.com URL.",
"type": "string"
},
"side": {
"description": "Single-market: buy_yes | sell_yes | buy_no | sell_no (default buy_yes). Basket: sell_yes | buy_yes (default auto — sell if partition sum > 1, buy if < 1).",
"type": "string"
},
"size_usd": {
"description": "Single-market: USD to spend (buys) or target proceeds (sells). Basket: settlement notional — shares per leg, each paying $1 at resolution. Default 1000, clamp 10–1,000,000.",
"type": "number"
}
},
"type": "object"
},
"name": "polymarket_fill_risk"
},
{
"description": "Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says so. TWO MODES: (1) `topic` — 11 pre-mapped macro subjects (\"fed\", \"btc\", \"eth\", \"cpi\", \"gdp\", \"sp500\", \"recession\", \"next_pope\", \"next_uk_pm\", \"next_israel_pm\", \"2028_president\") auto-fetch the matching event on each venue. You do NOT have to use those exact keys: the topic is resolved through aliases and keywords, so \"bitcoin\", \"fed rate decision\", \"inflation\", \"s&p 500\" and \"next pope\" all land on the right subject, and `resolution.topic_matched_by` tells you whether it was an exact key, a known alias, a phrase found inside a longer question, or a single-keyword guess — treat \"phrase\" and \"token\" as a GUESS at what you meant. An unresolvable topic returns error:\"mapping_failed\" with mapping_stage:\"topic_unrecognized\" and known_topics[]; it never silently falls back to a default subject. (2) explicit `kalshi_event_ticker` + `polymarket_event_slug` for custom pairings — BOTH modes run the identical token-overlap matcher, so the same disclosures apply to both. `resolution` is returned in BOTH modes and says how each side's identifier was picked (which Kalshi series was queried, how many events came back, whether the chosen one had quoted markets; which Polymarket search query ran and why that event won). Fleet #2064: when two Polymarket candidates tie on resolution time `polymarket_selected_by` now SAYS so, names every tied slug, names the tie-break that actually decided it (the candidate whose metric_type matches the Kalshi series, else lexicographic slug order), and states whether the winner's metric matches the Kalshi series — it used to assert \"picked the soonest-resolving\" byte-identically on calls that returned DIFFERENT events, because the tie was settled by upstream fetch arrival order. RESPONSE: each venue's leg-by-leg prices (raw probability 0-1) plus matched spread[].top_spreads_pp (Kalshi − Polymarket) where the same outcome shows up on both sides. SAFETY FIELDS: compatibility_warning is a sentence and compatibility_codes[] the machine-readable form; BOTH can be non-empty on returned pairs, so read them even when matched_pairs>0. Codes: event_subject_mismatch (the two event titles share no subject words — probably not the same question), temporal_mismatch (the two events are about different SUBJECT months — e.g. Kalshi \"CPI in October\" vs Polymarket \"September Inflation\"), temporal_alignment_unknown (the subject month could not be parsed on one or both sides — NOT the same as confirmed-aligned; check each event yourself), non_equivalent_bet_shapes, no_candidate_pairs, unclassified_legs_excluded, pairing_unverified (set in EITHER mode whenever pairs are returned: the legs were matched by keyword and word overlap, not a shared resolution source). Each entry in top_spreads_pp carries its own flags[] (temporal_mismatch, temporal_alignment_unknown, event_subject_mismatch, low_token_overlap). A leg whose metric_type or match_subtype is \"unknown\" is NEVER paired — those comparisons land in spread.skipped_unclassified and, when the wording lined up, in spread.low_confidence_pairs[] for inspection only. temporal_alignment{polymarket_month,kalshi_month,aligned} tells you whether the two events are about the same SUBJECT calendar period, in EITHER mode — this is the period the question is ABOUT (e.g. \"September\" for a CPI release that settles in October), not necessarily when either side settles; null means it could not be computed (see temporal_alignment_unknown), not that the two sides align. Fleet #2062: this used to compare Polymarket's settlement date against Kalshi's subject month and call a match — fixed to compare subject month to subject month on both sides. FEES: every top_spreads_pp and low_confidence_pairs[] row carries edge_pp_gross (== |spread_pp|), fees_pp, edge_pp_net, net_positive, and BOTH venues' taker fees itemised as kalshi_fee_pp and polymarket_fee_pp (plus polymarket_fee_rate, polymarket_fee_category, polymarket_fee_basis). Kalshi leg: fee = ceil(0.07 * contracts * P * (1-P) * 100) / 100 dollars per order, verified against kalshi.com/docs and corroborating explainers as of 2026-09-12. Polymarket leg: fee = shares × rate × p × (1-p) with rate by category (crypto 0.07, sports/economics/culture/weather/other 0.05, finance/politics/mentions/tech 0.04, geopolitics and world events fee-free), verified against Polymarket's own docs as of 2026-09-13 and read off each market's published fee parameters rather than inferred. Both amortized at a 100-contract reference size. Before fleet #1927 the Polymarket leg carried modeled gas only, which made every edge_pp_net here optimistic by up to ~1.75pp; spreads that no longer clear are the correction. Spread-crossing cost is still NOT modeled on the Polymarket leg (no live order book is fetched by this tool). spread.fees_note carries the same disclosure. RESOLUTION EQUIVALENCE (fleet #1909): every top_spreads_pp and low_confidence_pairs[] row now also carries resolution_equivalent (\"true\"|\"false\"|\"unclear\") and, when not \"true\", resolution_warning naming what differs — computed ONCE per event pair (not per leg) via resolution_audit/resolution_diff off one representative leg from each side, since the settlement mechanism is normally shared across every leg in one event. A non-equivalent or unclear pair is NEVER suppressed, only labelled — read resolution_warning before treating spread_pp as a real cross-venue disagreement rather than a difference in contract. spread.resolution_audit carries the full underlying audit (source/timestamp/timezone/precision/evidence_standard/void_handling for both sides) and spread.resolution_source_note is the standing disclosure explaining the methodology and its \"unclear\" caveat. Call resolution_audit/resolution_diff directly for a specific pair of legs if you need a non-representative-sample breakdown. skipped_cross_type / skipped_cross_subtype counters expose how many leg-pair comparisons were dropped (cross-type = metric_type mismatch like MoM vs YoY; cross-subtype = inequality mismatch like cum_ge vs cum_le). 15-MINUTE CRYPTO WINDOWS (fleet #3449): a topic such as \"btc 15m\" or \"bitcoin 15 minute\" is routed to updown_venue_compare (the same window on polymarket.com, Polymarket US and Kalshi with a per-pair equivalence flag); the response's `resolution` says topic_matched_by exact/alias/phrase and routed_to. Real cross-venue spreads are rarer than the macro-shortcut list suggests — most pre-mapped topics return compatibility_warning today; pre-mapped ≠ tradeable.",
"inputSchema": {
"examples": [
{
"topic": "fed"
},
{
"topic": "btc"
},
{
"topic": "bitcoin"
},
{
"topic": "fed rate decision"
},
{
"topic": "btc 15m"
}
],
"properties": {
"kalshi_event_ticker": {
"description": "Explicit Kalshi event ticker, e.g. \"KXFED-26OCT\". Overrides the topic-mapped Kalshi side.",
"type": "string"
},
"polymarket_event_slug": {
"description": "Explicit Polymarket event slug, e.g. \"fed-decision-in-june-825\". Overrides the topic-mapped Polymarket side.",
"type": "string"
},
"topic": {
"description": "Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — plus the 15-minute crypto up/down windows btc_15m | eth_15m | sol_15m | xrp_15m | bnb_15m (\"btc 15m\", \"bitcoin 15 minute\"), which are answered by updown_venue_compare for the window in progress — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess.",
"type": "string"
}
},
"type": "object"
},
"name": "polymarket_kalshi_spread"
},
{
"description": "REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee — read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: \"a side shown at 82 with five minutes left, how often did it ACTUALLY win?\" Returns a grid of (price bucket x minute elapsed) -> n, realized_win_rate_pp, mean_shown_price_pp, calibration_gap_pp (realized minus shown — zero means the book is calibrated), breakeven_win_rate_pp (the shown price plus the taker fee that was actually in force for that market), and net_edge_pp (realized minus breakeven, which is what a taker would have kept). WHY AN ARCHIVE EXISTS AT ALL: a settled 15-minute window is exactly what these venues stop serving. Measured 2026-10-22, a polymarket.com window drops out of the default market listing within minutes of closing (its trade tape and resolution stay retrievable by a closed-market lookup, which the collector now uses), and the other venues serve settled windows only briefly or thinly. So this tool reads a local archive collected window-by-window as they settle. THE THREE VENUES ARE NEVER POOLED. all three compare an END 60-second average with a START 60-second average, but on different feeds: polymarket.com on a Chainlink TWAP, polymarket-us and Kalshi on a CF Benchmarks BRTI simple average. The feeds disagree near the threshold (measured 2026-10-24 on btc: polymarket.com and Kalshi settled differently on 1.6% of windows both hold, polymarket-us and Kalshi on none), so venue:\"all\" returns one grid PER VENUE and `venues_pooled` is always false. EVERY RATE CARRIES ITS 95% INTERVAL, AND EVERY EDGE SAYS WHETHER IT SURVIVES IT. Each cell gives realized_win_rate_ci95_lo/hi_pp (Wilson, so it never reports an impossible win rate above 100), the same interval carried onto net_edge_ci95_lo/hi_pp, and net_edge_distinguishable_from_zero. READ THAT BOOLEAN BEFORE net_edge_pp: at these sample sizes most cells are false, meaning the interval straddles zero and a net_edge_pp of +4pp is NOT evidence of an edge. For scale, at a 90% win rate even n=300 gives a 95% half-width of ~3.4pp while net edges here run +2 to +4pp — so a comfortable-looking sample still cannot call a small edge real. `verdict` says it per cell in plain words, and the first note says how many cells survived. A THIN CELL WITHHOLDS ITS RATE ENTIRELY. Any bucket holding fewer than 30 settled windows reports status \"thin\" with realized_win_rate_pp and every interval null rather than printing a rate from a sample too small to mean anything — a 2-sample \"100% win rate\" is the most misleading thing this tool could say. ALWAYS READ `coverage` BEFORE THE GRID: it gives the first and last window held, windows_total vs windows_settled, every UTC day inside the span with no windows at all, and the longest run of consecutive missing windows. A grid over a store with a three-day hole looks entirely normal and is measuring a different population. mean_fill_price_pp and fill_vs_shown_pp are populated for polymarket.com only — it is the one venue of the three that publishes a trade tape for these markets, so it is the only place realized FILL can be compared with the shown price instead of assumed equal to it.",
"inputSchema": {
"examples": [
{
"asset": "btc",
"horizon": "15m",
"minute": 5,
"venue": "polymarket"
},
{
"asset": "btc",
"bucket_pp": 10,
"minute": 5,
"venue": "all"
},
{
"asset": "btc",
"side_convention": "favorite",
"venue": "kalshi"
}
],
"properties": {
"asset": {
"description": "btc (default) | eth | sol | xrp | bnb. Coverage differs by venue: polymarket and polymarket-us carry btc/eth/sol/xrp, Kalshi carries btc/eth/bnb.",
"type": "string"
},
"bucket_pp": {
"description": "Price-bucket width in percentage points: 5 | 10 (default) | 20 | 25 | 50. Must divide 100, so the last bucket is never narrower than the rest.",
"type": "number"
},
"horizon": {
"description": "15m (default). 5m | 1h | 1d are accepted but only 15m is collected today, so another value returns coverage.windows_total 0 rather than an error.",
"type": "string"
},
"minute": {
"description": "Minutes elapsed since window open, 0-based. Omit for the full grid; pass 5 for the \"five minutes in\" row only, which is also the cheapest query.",
"type": "number"
},
"side_convention": {
"description": "\"favorite\" (default) folds each window onto whichever side was the favorite — the frame published claims about early favorites use. \"yes\" keeps the venue own YES/Up side.",
"type": "string"
},
"venue": {
"description": "polymarket | polymarket-us | kalshi | all (default polymarket). \"all\" returns one grid per venue, never a merged one.",
"type": "string"
}
},
"type": "object"
},
"name": "prediction_calibration"
},
{
"description": "Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.",
"inputSchema": {
"examples": [
{
"key": "user_research_topic"
},
{}
],
"properties": {
"k": {
"description": "Alias for key.",
"type": "string"
},
"key": {
"description": "Memory key to retrieve (omit to list all keys). Accepts name, k, label as aliases.",
"type": "string"
},
"label": {
"description": "Alias for key.",
"type": "string"
},
"name": {
"description": "Alias for key.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "recall"
},
{
"description": "Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. \"sec_8k\") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.",
"inputSchema": {
"properties": {
"limit": {
"description": "Max events to return (1-200, default 50).",
"type": "number"
},
"mark_read": {
"description": "Flag the returned events read in the same call (default false).",
"type": "boolean"
},
"since": {
"description": "Optional ISO timestamp — return events fired_at >= this time.",
"type": "string"
},
"type": {
"description": "Optional — filter to one subscription type.",
"type": "string"
},
"unread_only": {
"description": "Return only events where read_at is null (default false).",
"type": "boolean"
}
},
"required": [],
"type": "object"
},
"name": "recent_alerts"
},
{
"description": "\"What's new with X\" / \"latest on Y\" / \"what happened to Z this week / month / quarter\" / \"updates on Acme\" / \"news on Tesla recently\" / \"what's happening with Apple\" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since `since`), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). `since` accepts ISO date (\"2026-04-01\") or relative shorthand (\"7d\", \"30d\", \"3m\", \"1y\"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.",
"inputSchema": {
"examples": [
{
"since": "30d",
"type": "company",
"value": "AAPL"
}
],
"properties": {
"since": {
"description": "Window start — ISO date (\"2026-04-01\") or relative (\"7d\", \"30d\", \"3m\", \"1y\"). Use \"30d\" or \"1m\" for typical monitoring.",
"type": "string"
},
"type": {
"description": "Entity type. Only \"company\" supported today.",
"enum": [
"company"
],
"type": "string"
},
"value": {
"description": "Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\").",
"type": "string"
}
},
"required": [
"type",
"value",
"since"
],
"type": "object"
},
"name": "recent_changes"
},
{
"description": "JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets — which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are cached like every other pack (≤ 60s TTL) and there is no push/webhook — do not use this to try to beat a release, use it to see what is coming and what is already priced. CATEGORIES: econ (CPI, Employment Situation/jobs report, GDP, PCE, PPI, retail sales, housing starts, jobless claims — via fred_release_dates per known release_id, since FRED's own cross-release calendar mostly returns recent actuals, not future dates), fed (the next FOMC meeting's rate decision, via fomc_calendar), fda (PDUFA action dates + FDA advisory-committee meetings, via pdufa_catalysts / fda_adcom_calendar), sec (SEC final rules whose own DATES clause names an effective date in the window, via federal-register recent_rules — usually finds nothing in a short window since SEC rules typically take effect 30–60 days out, which is an accurate answer, not a bug), court (ALWAYS EMPTY today — court-listener has no forward-looking scheduled-hearing calendar, only filing/termination dates, so this category returns zero releases with unsupported:true rather than fabricate one). Omit `categories` or pass \"all\" for every category. MATCHING AND ITS HONESTY CONTRACT: every release is returned even when it has ZERO matched markets — a release is never dropped just because nothing on Polymarket or Kalshi resolves on it (most FDA/SEC releases will show markets:[]; that is signal, not a gap). Every matched market carries resolves_on_this_release: \"true\" (the venue's own close/end date sits within ~36h of the release AND the question passed a subject filter — econ and fed only), \"likely\" (same subject filter, but the venue closes days away from the release date), or \"unclear\" (a keyword hit with no date to anchor against — always true for the fda category, which has no ladder structure to check a date against). matched_by names the mechanism (a Kalshi series ticker, a Polymarket search query, or an FDA keyword probe) so a caller can judge the match rather than trust a label. scheduled_at carries both `utc` and `et`; econ releases use the standing BLS/Census 8:30am ET convention (FRED's calendar itself has no clock time), FOMC decisions use the 2:00pm ET convention, and FDA/SEC dates are date_only:true (no reliable clock time exists for either). DO NOT treat a matched market as a real arbitrage or a settled fact on its own — a market question sharing tokens with a release name is not proof it settles on that release's own published number. Call resolution_audit / resolution_diff (fleet #1909) on a specific market before sizing anything here. An empty window (zero releases across every requested category) returns the SAME shape as a populated one — release_count:0, releases:[] — plus empty_reason:\"no_releases_in_window\" and a `hint` telling you to widen, so you never branch on the response shape and never have to guess whether zero means \"nothing is scheduled\" or \"the lookup failed\". Econ releases especially cluster on specific dates each month, so a 48h window often straddles a dead stretch.",
"inputSchema": {
"examples": [
{
"hours": 72
},
{
"categories": "econ,fed",
"hours": 100
}
],
"properties": {
"categories": {
"description": "Comma or space separated subset of econ|fed|fda|sec|court, or \"all\" (default). E.g. \"econ,fed\" or \"fda\".",
"type": "string"
},
"hours": {
"description": "Look-ahead window in hours from now. Default 48. Capped at 720 (30 days) — econ/fed releases are dated weeks apart, so a short window is often empty; widen rather than assume nothing is scheduled.",
"type": "number"
}
},
"type": "object"
},
"name": "release_calendar_markets"
},
{
"description": "Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.",
"inputSchema": {
"examples": [
{
"key": "target_ticker",
"value": "AAPL"
}
],
"properties": {
"content": {
"description": "Alias for value.",
"type": "string"
},
"data": {
"description": "Alias for value.",
"type": "string"
},
"k": {
"description": "Alias for key.",
"type": "string"
},
"key": {
"description": "Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\"). Accepts name, k, label as aliases.",
"type": "string"
},
"label": {
"description": "Alias for key.",
"type": "string"
},
"name": {
"description": "Alias for key.",
"type": "string"
},
"text": {
"description": "Alias for value.",
"type": "string"
},
"v": {
"description": "Alias for value.",
"type": "string"
},
"value": {
"description": "Value to store (any text — findings, addresses, preferences, notes). Accepts content, text, data, v as aliases; a non-string value is stored as JSON.",
"type": "string"
}
},
"required": [
"key",
"value"
],
"type": "object"
},
"name": "remember"
},
{
"description": "Claygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence — {value, evidence_url, quote, status}. status is NEVER self-reported by the model: \"found\" means this code independently verified the model's quote is a VERBATIM substring of text actually fetched; \"inferred\" means a value was given but the quote could not be verified; \"not_established\" means no source answered the field, and its value is always null — never guessed, never a blended score. Sources: \"web\" fetches the company's own site (entity.domain required — homepage, /about, /leadership) via fetch_url; \"catalog\" checks entity_profile (SEC EDGAR; resolved:false for a private company is expected, not a failure); \"both\" (default) tries both. max_cost (USD, default 0.02, max 0.50) scales how many pages are fetched and refuses up front if it is too small to pay for even one extraction call (floor $0.002) — never silently overspends. A row where every source comes back empty costs nothing: every field is mechanically not_established with NO model call made. For a boolean/derived field (e.g. \"does this company sell to healthcare\"), the quote only has to SUPPORT the value — a descriptive sentence about customers/products counts, the source need not state the answer verbatim. leadership_page_status (\"fetched\"|\"not_found\"|\"not_attempted\", plus leadership_note) says plainly whether a leadership/team page was actually read, so a named-person field (head_of_sales) coming back not_established is distinguishable from \"this company just doesn't publish one\" vs. \"we never checked\". model_output_empty:true means the model returned nothing usable (a transport/budget problem) — every field is not_established for THAT reason, never read as 20 individual \"no\" judgments. Use with a fixed question + schema across many rows for \"Claygent over N companies with a hard cost cap\" (composes with batch callers). For picking from a fixed label list instead of extracting open fields, use classify_row (cheaper, one model call).",
"inputSchema": {
"examples": [
{
"entity": {
"domain": "stripe.com",
"name": "Stripe"
},
"max_cost": 0.02,
"output_schema": {
"properties": {
"head_of_sales": {
"type": "string"
},
"sells_to_healthcare": {
"type": "boolean"
}
}
},
"question": "Does this company sell to healthcare, and who is the head of sales?",
"sources": "web"
}
],
"properties": {
"entity": {
"description": "The row/company to research. At least one of name/domain required.",
"properties": {
"domain": {
"description": "Company website domain, e.g. \"acme.com\" (with or without https://). Required to use sources:\"web\".",
"type": "string"
},
"name": {
"description": "Company name, e.g. \"Acme Robotics\".",
"type": "string"
}
},
"type": "object"
},
"max_cost": {
"description": "Cost ceiling in US dollars for this one row. Default 0.02, max 0.50, minimum viable 0.002 (below that the call is refused rather than silently exceeding it).",
"type": "number"
},
"output_schema": {
"description": "JSON Schema object naming the fields to extract, e.g. {\"properties\":{\"sells_to_healthcare\":{\"type\":\"boolean\"},\"head_of_sales\":{\"type\":\"string\"}}}. Up to 20 fields.",
"type": "object"
},
"question": {
"description": "The question to answer about this company, in natural language, e.g. \"Does this company sell to healthcare, and who is the head of sales?\"",
"type": "string"
},
"sources": {
"description": "Where to look: \"web\" (company site only), \"catalog\" (entity_profile only), \"both\" (default).",
"enum": [
"catalog",
"web",
"both"
],
"type": "string"
}
},
"required": [
"entity",
"question",
"output_schema"
],
"type": "object"
},
"name": "research_row"
},
{
"description": "Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says \"the time range specified in the title\" — e.g. Polymarket's 15-minute Chainlink TWAP family), the precision of the computation (e.g. \"1-minute candle close\" vs \"60-second trailing average\" vs \"twap_60s_lookback\"/\"twap_30s_lookback\" vs \"election outcome\"), comparison_basis — what is compared to what (end_average_vs_start_average | close_vs_open; orthogonal to precision, since venues can share this comparison shape while computing each endpoint differently), the evidence standard (official_source | consensus_reporting | any_credible_report | unspecified), and void_handling (cancellation/postponement settlement — reused verbatim from bet_research's cancellation_rule detector, not re-derived). Parses Polymarket's `description` field (fetched via polymarket_market, or via polymarket_us_search for the .us venue) or Kalshi's `rules_primary` + `rules_secondary` fields (fetched via kalshi_market) with regex + a small vocabulary — no LLM pass, so an unusual clause reports confidence:\"low\" rather than a guess. Pass `market` as a Polymarket slug/URL (either venue) or a Kalshi market ticker (e.g. \"KXBTCD-26SEP1317-T66999.99\"); a Kalshi EVENT ticker (e.g. \"KXBTCD-26SEP1317\") also works — it picks one representative market under that event, since the settlement mechanism is normally shared across all strikes/legs in one event. Use this before treating a polymarket_kalshi_spread row as a real arbitrage: two ladders that look alike can settle on different sources (Polymarket.com's Chainlink TWAP stream vs Kalshi/Polymarket US's CF Benchmarks BRTI), at different times, or with a different lookback window — this tool is how you check. Pair with resolution_diff to compare two markets directly. KNOWN GAP: idiosyncratic phrasing that doesn't match the vocabulary returns confidence:\"low\" and evidence_standard:\"unspecified\" rather than an LLM-guessed answer.",
"inputSchema": {
"examples": [
{
"market": "bitcoin-above-70k-on-september-13-2026",
"venue": "polymarket"
},
{
"market": "KXBTCD-26SEP1317",
"venue": "kalshi"
}
],
"properties": {
"market": {
"description": "Polymarket (.com or .us) market slug or URL, OR a Kalshi market ticker (preferred) or event ticker (falls back to a representative market under that event).",
"type": "string"
},
"venue": {
"description": "Which venue to fetch the market from. \"polymarket\" is the offshore venue (polymarket.com); \"polymarket-us\" is the separate, CFTC-regulated polymarket.us venue, matched by slug via its own search (no exact-slug lookup exists upstream).",
"enum": [
"polymarket",
"kalshi",
"polymarket-us"
],
"type": "string"
}
},
"required": [
"venue",
"market"
],
"type": "object"
},
"name": "resolution_audit"
},
{
"description": "Field-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi) — runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns `equivalent`: \"true\" only when both sides parsed with enough confidence to compare AND no field conflicts; \"false\" when a specific conflict was found (differing_fields names which — e.g. [\"source\",\"settle_time\"] for a Polymarket Bitcoin market settling on Binance's 1-minute candle at noon ET versus a Kalshi KXBTCD market settling on CF Benchmarks' BRTI 60-second average at 5pm EDT — SAME asset, DIFFERENT contract; or [\"source\",\"precision\"] for Polymarket.com's Chainlink 15-minute TWAP clause (precision \"twap_60s_lookback\") against Kalshi's 15-minute KXBTC15M clause (precision \"60-second trailing average\" off CF Benchmarks' BRTI) — different source and a different lookback mechanism, even though BOTH compare an end-of-window average to a start-of-window average, so comparison_basis is EQUAL there and correctly NOT in differing_fields — verified live 2026-10-22, fleet #3447); \"unclear\" when one or both sides could not be confidently parsed (an absence of evidence is not evidence of equivalence — read raw_clause yourself in that case). comparison_basis is flagged as differing whenever both sides resolved one and they disagree, independent of whether source/precision also matched. Only flags source/evidence_standard as differing when BOTH sides gave a SPECIFIC comparable answer — a named source (e.g. \"Associated Press, Fox News, NBC\") against a generic one (e.g. Kalshi's \"consensus of media organizations\") is treated as the same evidence standard, not a conflict, since that is standard election-market boilerplate on both venues. Use this before sizing a polymarket_kalshi_spread pair as a real cross-venue arb, or standalone to sanity-check any two markets you suspect settle on different things.",
"inputSchema": {
"examples": [
{
"a": {
"market": "bitcoin-above-70k-on-september-13-2026",
"venue": "polymarket"
},
"b": {
"market": "KXBTCD-26SEP1317",
"venue": "kalshi"
}
}
],
"properties": {
"a": {
"description": "First market to compare.",
"properties": {
"market": {
"type": "string"
},
"venue": {
"enum": [
"polymarket",
"kalshi",
"polymarket-us"
],
"type": "string"
}
},
"required": [
"venue",
"market"
],
"type": "object"
},
"b": {
"description": "Second market to compare.",
"properties": {
"market": {
"type": "string"
},
"venue": {
"enum": [
"polymarket",
"kalshi",
"polymarket-us"
],
"type": "string"
}
},
"required": [
"venue",
"market"
],
"type": "object"
}
},
"required": [
"a",
"b"
],
"type": "object"
},
"name": "resolution_diff"
},
{
"description": "\"What's the ticker for…\" / \"find the CIK for…\" / \"what's the LEI for…\" / \"what's the RxCUI for…\" / \"look up the ID for…\" / \"what is X's official identifier\" / \"who owns X\" / \"is X a subsidiary of Y\" — resolve a user-spoken NAME to the canonical/official identifiers other tools require as input. Use FIRST whenever you have a name but need an ID. SUPPORTED TYPES: \"company\" (cross-source identity spine: 10-digit CIK + ticker + company_name from SEC EDGAR, legal-entity LEI from GLEIF with parent/ultimate-parent/children ownership when the LEI resolves, and security FIGI from OpenFIGI — by exact ticker map when a ticker is implied, and otherwise by name search, so NON-EQUITY instruments that never have a ticker (municipal and corporate bonds, notes, authority debt) DO resolve here; when a name matches more than one instrument it asserts nothing and returns `figi_candidates` to pick from, which is the correct answer to an issuer name that does not identify a single bond; every identifier is labelled with the source that established it, and an identifier that could NOT be resolved is stated explicitly under `unresolved` rather than omitted — accepts ticker, CIK, ISIN, or company name as input; an ISIN like \"CH0038863350\" resolves to the LEGAL ENTITY that issued the security via the GLEIF ISIN-to-LEI mapping, covering non-US issuers EDGAR cannot reach), \"drug\" (returns RxCUI + ingredient + brand from RxNorm + pipeworx://rxnorm/concept/{rxcui} citation; accepts brand or generic name). LEI/FIGI enrichment degrades gracefully — if GLEIF or OpenFIGI is unavailable, the EDGAR identifiers still return. Each call cascades through several lookup endpoints internally — using resolve_entity replaces 2-3 manual lookups.",
"inputSchema": {
"examples": [
{
"type": "company",
"value": "AAPL"
}
],
"properties": {
"country": {
"description": "OPTIONAL ISO 3166-1 alpha-2 of the country whose business register you mean (\"NO\", \"FI\", \"JP\", \"GB\", \"FR\", \"EE\", \"BR\"). Narrows the national-register fan-out and is often the difference between the right company and a US namesake — \"Apple\" with country \"NO\" is a Norwegian company, not Apple Inc. Omitting it searches every register we can name, which is the right default when you do not know. company only; ignored for drug.",
"type": "string"
},
"type": {
"description": "Entity type: \"company\" or \"drug\".",
"enum": [
"company",
"drug"
],
"type": "string"
},
"value": {
"description": "For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing.",
"type": "string"
}
},
"required": [
"type",
"value"
],
"type": "object"
},
"name": "resolve_entity"
},
{
"description": "Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: \"does Claude know about us as well as our competitors?\". Returns ranked list with score, confidence, signal density per entity.",
"inputSchema": {
"examples": [
{
"entities": [
"Pipeworx",
"Zapier"
]
}
],
"properties": {
"_apiKey": {
"description": "Optional Anthropic API key — only if \"anthropic\" is in models. Passed to api.anthropic.com per probe.",
"type": "string"
},
"context": {
"description": "Optional shared context applied to every probe (e.g. \"B2B SaaS\", \"Boston restaurant\"). Disambiguates common names.",
"type": "string"
},
"entities": {
"description": "Array of 2-8 entities to compare (brand/business/product names). First entry treated as the \"subject\" for narrative; rest are competitors.",
"items": {
"type": "string"
},
"type": "array"
},
"models": {
"description": "Which models to probe. Supported: \"workers-ai\" (free default), \"anthropic\" (requires _apiKey). Omit for just workers-ai.",
"items": {
"type": "string"
},
"type": "array"
}
},
"required": [
"entities"
],
"type": "object"
},
"name": "scan_competitor_ai_presence"
},
{
"description": "Composite \"should I add this npm package to my project\" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks \"is X safe / popular / small\" or \"what does adding lodash cost me\". Returns a summary block (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable), per-advisory detail, links, and a list of recent alternative versions. NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly. Partial failures degrade gracefully — bundlephobia's first measurement on a new version can take 5-30s; sources_failed will list it if it times out, the rest still returns.",
"inputSchema": {
"examples": [
{
"package": "left-pad"
}
],
"properties": {
"package": {
"description": "npm package name. Scoped packages (e.g. \"@types/node\") are accepted.",
"type": "string"
},
"version": {
"description": "Specific version to check (e.g., \"18.3.1\"). Defaults to the latest published version when omitted.",
"type": "string"
}
},
"required": [
"package"
],
"type": "object"
},
"name": "scan_dependency"
},
{
"description": "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).",
"inputSchema": {
"examples": [
{
"query": "supply-chain risk",
"text": "Apple Inc. reported fiscal 2023 revenue of $383.285 billion, driven by strong iPhone and Services growth. Net income was $96.995 billion. The company faced supply-chain risk in China during the quarter."
}
],
"properties": {
"limit": {
"description": "Max passages to return (1-20, default 5).",
"type": "number"
},
"query": {
"description": "Natural-language query — what passages do you want? E.g. \"supply-chain risk\", \"fiscal year 2024 revenue\", \"drug interactions with warfarin\".",
"type": "string"
},
"text": {
"description": "The document text to search inside (max ~200K chars).",
"type": "string"
}
},
"required": [
"text",
"query"
],
"type": "object"
},
"name": "search_within"
},
{
"description": "Resolve an organization NAME — especially a clinical-trial sponsor, drug developer, or operating subsidiary — to the US-listed public FILER that reports it (ticker + SEC CIK). Built for the join that plain ticker/name lookup fails: trial registries (ClinicalTrials.gov) name operating subsidiaries (\"Merck Sharp and Dohme\"), while SEC names the listed parent (\"Merck & Co\", MRK). This tool bridges that gap and, crucially, tells you WHY a name does not resolve instead of collapsing every miss to \"not found\". Returns a `status`: \"resolved\" (name is itself a US-listed filer), \"resolved_via_parent\" (name is a subsidiary; resolved to its listed parent, with evidence + confidence), \"us_registrant_unlisted\" (has an SEC CIK but no public listing and no listed parent — typically a private company that filed a Form D or draft registration), or \"no_us_registrant\" (no US SEC presence at all — typically a non-US-listed or foreign private company). Use before joining trial sponsors to public financials, ownership, or filings.",
"inputSchema": {
"examples": [
{
"sponsor": "Merck Sharp and Dohme"
},
{
"sponsor": "Lexeo Therapeutics"
}
],
"properties": {
"sponsor": {
"description": "Organization name to resolve — a trial sponsor, drug developer, or company name, e.g. \"Merck Sharp and Dohme\", \"Lexeo Therapeutics\", \"Dizal Pharmaceuticals\".",
"type": "string"
}
},
"required": [
"sponsor"
],
"type": "object"
},
"name": "sponsor_to_filer"
},
{
"description": "Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: \"sec_8k\" (8-K filings matching ticker + item codes — e.g. items:[\"5.02\"] = officer change), \"polymarket_edge\" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:\"fed\"}), \"fred_series\" (new FRED observations — params:{series_id:\"UNRATE\"}), \"patent_grant\" (new USPTO grants for an applicant), \"clinical_trial\" (new/updated ClinicalTrials.gov studies), \"form_d\" (new SEC Form D fundraise notices — params:{state?, industry?, min_amount?, exemption?}, all optional), \"news_keyword\" (GDELT keyword news alerts, metadata+link only — params:{query, lang?, domains?}), \"job_post\" (new public job-board postings — params:{ats?, board_token?} or {domain?}, plus optional title_query/location_query), \"tool_diff\" (re-runs any read-only tool on a schedule and fires on change — params:{tool, args?, fields[], schedule}), \"new_entity\" (new business registrations from a state business-entity registry — params:{state:\"CO\", name_query?, entity_type?}), \"tech_change\" (a watched domain's website technology stack adds or drops a technology — params:{domains:[\"acme.com\"], technologies?}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:\"you@x.com\"}) or sms (delivery:{sms:\"+15551234567\"} — phone must be verified at /account first; 10/day cap).",
"inputSchema": {
"properties": {
"delivery": {
"description": "Optional delivery channels in addition to the always-on persistent feed. {email:\"you@x.com\"} sends a templated alert per fired event. {sms:\"+15551234567\"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:\"https://...\"} POSTs each event JSON to your endpoint, HMAC-signed — the response includes delivery.webhook_secret (whsec_…) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of \"<X-Pipeworx-Timestamp>.<raw body>\". Auto-disabled after 10 consecutive failing runs.",
"properties": {
"email": {
"description": "Email address to deliver alerts to. Validated against a standard pattern.",
"type": "string"
},
"sms": {
"description": "E.164 phone number, e.g. \"+15551234567\". Must match the account's verified phone.",
"type": "string"
},
"webhook": {
"description": "HTTPS URL to POST fired events to. https only; localhost/private hosts rejected. Signing secret returned once at subscribe time.",
"type": "string"
}
},
"type": "object"
},
"params": {
"description": "Type-specific filter. sec_8k: {ticker:\"AAPL\", items?:[\"5.02\",\"1.01\"]}. polymarket_edge: {topic:\"fed\", min_spread_bps?:500}. fred_series: {series_id:\"UNRATE\"}. patent_grant: {applicant:\"Apple Inc.\"}. clinical_trial: {sponsor?:\"Pfizer\", condition?:\"lung cancer\", phase?:\"PHASE3\"} (sponsor or condition required). form_d: {state?:\"CA\", industry?:\"Biotechnology\", min_amount?:500000, exemption?:\"06B\"} (all optional — omit all to watch every new Form D nationwide). news_keyword: {query:\"\\\"semiconductor sanctions\\\"\", lang?:\"eng\", domains?:[\"reuters.com\"]} (query required). job_post: EITHER {ats:\"greenhouse\", board_token:\"acme\"} (exact board) OR {domain:\"acme.com\"} (auto-detected), plus optional title_query/location_query substrings. tool_diff: {tool:\"form5500\", args?:{...}, fields:[\"headcount\"], schedule:\"daily\"} — re-runs that tool on schedule and fires when the named fields change; tool must be read-only and not need a Pipeworx-held platform key; schedule \"hourly\" needs the paid tier. new_entity: {state:\"CO\", name_query?:\"dental\", entity_type?:\"limited liability\"} — state is required and must be one of FL, NY, CO, OR, CT, TX, PA. tech_change: {domains:[\"acme.com\",\"example.org\"], technologies?:[\"Shopify\",\"Segment\"]} — domains required (1-200), technologies optional (exact names, case-insensitive) to narrow which detected technologies alert. Unknown keys in form_d/news_keyword/job_post/tool_diff/new_entity/tech_change params are rejected at subscribe time.",
"type": "object"
},
"type": {
"description": "Subscription type.",
"enum": [
"sec_8k",
"polymarket_edge",
"fred_series",
"patent_grant",
"clinical_trial",
"form_d",
"news_keyword",
"job_post",
"tool_diff",
"new_entity",
"tech_change"
],
"type": "string"
}
},
"required": [
"type",
"params"
],
"type": "object"
},
"name": "subscribe"
},
{
"description": "What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass `topic` (e.g. \"finance\", \"pharma\", \"betting\") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).",
"inputSchema": {
"examples": [
{
"topic": "finance"
}
],
"properties": {
"topic": {
"description": "Optional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news. Omit for a cross-category spread.",
"type": "string"
}
},
"type": "object"
},
"name": "suggest_questions"
},
{
"description": "Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.",
"inputSchema": {
"properties": {
"id": {
"description": "Subscription id (uuid) returned by subscribe.",
"type": "string"
}
},
"required": [
"id"
],
"type": "object"
},
"name": "unsubscribe"
},
{
"description": "How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair: windows both venues settled, divergent count, the rate with its 95% Wilson interval (withheld under 30 paired windows), which direction they split, and what was excluded (unsettled on a side, 50-50). A HEADLINE RATE IS A CONCENTRATION QUESTION, so every pair also carries `concentration` (UTC days and hours the divergent windows fell in, the busiest day, the top-3-day share, and a plain reading) and `by_how_decided` (the rate by how far the reference venue's mid was from 50 at its last priced minute: the rate is a fraction of a percent for windows that were decided by the end and tens of percent for the ones that were not). `divergent_path` gives the mean Up mid by minute on both venues over the divergent windows only, split by who said Up, so the \"early spike that fades\" story can be checked rather than assumed. Measured on the archive 2026-10-27 over 30 days of btc: polymarket.com vs Kalshi diverged on 48 of 2,847 windows (1.69%, interval 1.27-2.23), spread over 27 of 31 UTC days, 0.19% of windows decided by the end and 17-29% of the ones still undecided; Polymarket US vs Kalshi on 0 of 1,838. asset btc | eth | sol | xrp | bnb (bnb has no pair: Kalshi only); days 1-90 (default 30), capped by what the archive holds (it starts 2026-09-22 for polymarket.com and Kalshi, 2026-10-07 for Polymarket US). Read-only; cheap enough to call, it reads several thousand archive rows.",
"inputSchema": {
"examples": [
{
"asset": "btc",
"days": 30
},
{
"asset": "eth",
"days": 14
}
],
"properties": {
"asset": {
"description": "btc (default) | eth | sol | xrp | bnb. The archive holds btc/eth on all three venues, sol/xrp on polymarket.com and Polymarket US, bnb on Kalshi only (no pair).",
"type": "string"
},
"days": {
"description": "Look-back in days, 1-90 (default 30). The archive starts 2026-09-22 (polymarket.com, Kalshi) and 2026-10-07 (Polymarket US, btc), so a longer span is capped by what is held; coverage is reported per pair.",
"type": "number"
}
},
"required": [],
"type": "object"
},
"name": "updown_divergence_rate"
},
{
"description": "The same 15-minute crypto \"up or down\" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window (\"current\" default, \"next\", \"previous\", or the window START as ISO such as 2026-10-27T14:15:00Z, on a 15-minute boundary). Per venue: question, Up bid / ask / mid / last, spread_pp, quote_state, volume WITH ITS UNIT, open interest, liquidity, settlement source, comparison basis, when it settles. THE VENUES ARE NOT ONE CONTRACT. Kalshi and Polymarket US settle on CF Benchmarks' BRTI (60-second average at the end against the same at the start): the same bet, so a gap between them is a real disagreement. polymarket.com settles on a Chainlink 60-second TWAP, end against start: same comparison shape, different feed, so a gap against either is partly the contract. `pairs[]` gives equivalent (\"true\"|\"false\"|\"unclear\"|\"not_comparable\") from resolution_diff for every pair, material_differences, mid_diff_pp (a minus b, in percentage points) and read_as in words. Measured over 30 days of settled windows the Chainlink and BRTI feeds settle a window differently about 1.2-1.8% of the time, almost entirely windows that ended near the threshold (see updown_divergence_rate). `net_spread` is computed only for the pair that is equivalent: the gap in mid terms and at top of book (buy Up where cheaper at the ask, Down where Up is dearer at 1 minus the bid) after BOTH venues' taker fees, each fee carrying its verified-as-of date. Top-of-book size is shown where the venue publishes it (Polymarket US); the Kalshi figure is not in its market payload, so read its order book before sizing. A venue with no market for the window is {status:\"not_listed\", reason}; one that could not be read is {status:\"unavailable\", refusal} -- never an empty object, and never the same thing. A one-sided book (typical Polymarket US just before a window is decided) has quote_state \"bid_only\", a null mid, and the last trade stands in labelled price_basis \"last\". Quotes are read venue by venue (cached up to 60 seconds), so a gap of a couple of points on a moving window is inside the skew. Only the 15m horizon is offered: it is the one where all three list the same up/down question. For the settled history of how often the venues disagreed, call updown_divergence_rate.",
"inputSchema": {
"examples": [
{
"asset": "btc",
"horizon": "15m",
"window": "current"
},
{
"asset": "eth",
"window": "previous"
},
{
"asset": "btc",
"window": "2026-10-27T14:30:00Z"
}
],
"properties": {
"asset": {
"description": "btc (default) | eth | sol | xrp | bnb. Coverage differs by venue; a venue that does not list the asset answers not_listed.",
"type": "string"
},
"horizon": {
"description": "15m (default and the only value offered).",
"type": "string"
},
"window": {
"description": "\"current\" (default), \"next\", \"previous\", or the window START as an ISO-8601 timestamp on a 15-minute boundary, e.g. 2026-10-27T14:15:00Z. An unaligned timestamp is refused, not rounded.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "updown_venue_compare"
},
{
"description": "\"Is it true that…\" / \"fact check\" / \"verify the claim that…\" / \"did X really…\" / \"was Y actually…\" / \"confirm or refute\" / \"true or false\" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is factually correct. Company-financial claims (revenue, net income, cash for public US companies) verify via the structured SEC EDGAR + XBRL fast path with exact percent-delta math; ANY OTHER factual claim (macro statistics, rates, prices, drug data, records) automatically falls through to the grounded pipeline — routed to the right live source, answered with verbatim evidence, then judged. Returns a verdict (confirmed / approximately_correct / refuted / inconclusive / unsupported / could_not_verify), the grounded or structured actual value with pipeworx:// citation, and reasoning. IMPORTANT for callers: could_not_verify means the check did not happen (our LLM or source failed) and carries verification_error{stage,detail} — it is NOT evidence for or against the claim, and must not be shown as one. unsupported means we looked and cover no source for it. Replaces 4–6 sequential calls (NL parsing → entity resolution → data lookup → comparison).",
"inputSchema": {
"examples": [
{
"claim": "Apple's fiscal 2023 revenue was $383 billion"
}
],
"properties": {
"claim": {
"description": "Natural-language factual claim, e.g., \"Apple's FY2024 revenue was $400 billion\" or \"Microsoft made about $100B in profit last year\".",
"type": "string"
},
"tolerance_pct": {
"description": "Max percent deviation still graded approximately_correct (0.5–50). Overrides the tolerance implied by the claim wording — set 1–2 for hallucination detection where any material error must be refuted. Default: implied by wording, capped at 5.",
"type": "number"
}
},
"required": [
"claim"
],
"type": "object"
},
"name": "validate_claim"
}
]
}What the leaf hashes
{"body":"5e487011910c24bd61e37fbfc5439055e9e5858a743bad4e468a02ac30f6e1f9","id":988016,"kind":"mcp.tools","method":"probe.mcp/1","observed_us":1793242295717727,"prev":774134,"subject":"9629003a-1089-4fbf-a255-d5b8682640df","subject_kind":"endpoint"}Proof
Its day has not closed yet. A day closes ten minutes after midnight UTC; the proof appears here then.