Patents

Added value: +{
+  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
+  "type": "string"
+}

Added value: +{
+  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
+  "type": "string"
+}

Previous value: -"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)."New value: +"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. Unknown keys in form_d/news_keyword/job_post/tool_diff/new_entity params are rejected at subscribe time."

Previous value: -[
-  "sec_8k",
-  "polymarket_edge",
-  "fred_series",
-  "patent_grant",
-  "clinical_trial"
-]New value: +[
+  "sec_8k",
+  "polymarket_edge",
+  "fred_series",
+  "patent_grant",
+  "clinical_trial",
+  "form_d",
+  "news_keyword",
+  "job_post",
+  "tool_diff",
+  "new_entity"
+]

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Previous value: -"Your question or request in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Previous value: -"Your question in natural language. Accepts query, q, prompt, text, input as aliases."New value: +"Your question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases."

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Previous value: -"The research question, in natural language. Broad/multi-part is fine — decomposition is the point."New value: +"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."

Added value: +{
+  "description": "Alias for question.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Previous value: -"Memory key to delete"New value: +"Memory key to delete. Accepts name, k, label as aliases."

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Previous value: -"Memory key to retrieve (omit to list all keys)"New value: +"Memory key to retrieve (omit to list all keys). Accepts name, k, label as aliases."

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Previous value: -"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\")"New value: +"Memory key (e.g., \"subject_property\", \"target_ticker\", \"user_preference\"). Accepts name, k, label as aliases."

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for key.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

Added value: +{
+  "description": "Alias for value.",
+  "type": "string"
+}

Previous value: -"Value to store (any text — findings, addresses, preferences, notes)"New value: +"Value to store (any text — findings, addresses, preferences, notes). Accepts content, text, data, v as aliases; a non-string value is stored as JSON."

Previous value: -[
-  {
-    "query": "machine learning neural networks"
-  },
-  {
-    "query": "blockchain cryptocurrency"
-  },
-  {
-    "applicant": "APPLE INC."
-  },
-  {
-    "inventor": "Hinton",
-    "query": "neural"
-  }
-]New value: +[
+  {
+    "filed_after": "2023-09-25",
+    "filed_before": "2026-09-25",
+    "query": "\"cell-free RNA\""
+  },
+  {
+    "query": "machine learning neural networks"
+  },
+  {
+    "query": "blockchain cryptocurrency"
+  },
+  {
+    "applicant": "APPLE INC."
+  },
+  {
+    "inventor": "Hinton",
+    "query": "neural"
+  }
+]

Previous value: -"Optional. Filter to patents filed on/after this date (ISO YYYY-MM-DD)."New value: +"Optional. Filter to patents FILED on/after this date (ISO YYYY-MM-DD). Use this for \"who has filed / applied for patents on X (recently / in the last N years)\" — it covers both pending applications and already-granted patents, so it is the right bound even when the question also says \"recent\". Do NOT substitute `granted_after` for a filing-activity question: grant lags filing by 2+ years, so a recent filing window under `granted_after` typically returns zero even when filing activity is real."

Previous value: -"Optional. Filter to patents filed on/before this date (ISO YYYY-MM-DD)."New value: +"Optional. Filter to patents FILED on/before this date (ISO YYYY-MM-DD)."

Previous value: -"Optional. Filter to patents GRANTED (issued) on/after this date (ISO YYYY-MM-DD). This is the argument that answers \"recent/latest patents\" — without it, results are unexamined applications, not issued patents. Accepted synonym: `issued_after`."New value: +"Optional. Filter to patents GRANTED (issued) on/after this date (ISO YYYY-MM-DD) — use ONLY when the question explicitly says GRANTED / ISSUED / APPROVED, not for a plain \"recent patents\" or \"who has filed\" question (use `filed_after` for those — see its description). Accepted synonym: `issued_after`."

Previous value: -"Free-text keywords. Every term must appear (they are AND-ed), so add words to narrow and remove words to widen. Wrap words in double quotes to require them adjacent: `\"machine learning\" model` needs the exact phrase plus the word model. Examples: \"lithium battery\", \"crispr\", \"neural network\". Pass \"*\" if you only want to filter by applicant/date with no keyword constraint."New value: +"Free-text keywords. Every term must appear (they are AND-ed), so add words to narrow and remove words to widen. Wrap words in double quotes to require them adjacent: `\"machine learning\" model` needs the exact phrase plus the word model. Examples: \"lithium battery\", \"crispr\", \"neural network\". Pass \"*\" if you only want to filter by applicant/date with no keyword constraint. A curated set of known synonyms/abbreviations (e.g. cfRNA / cell-free RNA / circulating RNA, or MRD / minimal residual disease / residual cancer) is automatically expanded to an OR group within the query — quoted or bare, either form is recognized — so you do not need to guess which exact wording a given patent uses (see `synonyms_expanded` in the response). If several quoted phrases — or two recognized synonym-group concepts, quoted or not — ANDed together still match nothing, the tool retries once with them OR'd instead (see `broadened` in the response) rather than returning a bare zero."

Added value: +[
+  {
+    "entity": "Tesla"
+  }
+]

Added value: +[
+  {
+    "question": "What is the current US unemployment rate?"
+  }
+]

Added value: +[
+  {
+    "question": "What was Apple's fiscal 2023 revenue?"
+  }
+]

Added value: +[
+  {
+    "type": "company",
+    "values": [
+      "AAPL",
+      "MSFT"
+    ]
+  }
+]

Added value: +[
+  {
+    "depth": "quick",
+    "question": "What is the current US unemployment rate and how has it changed over the past year?"
+  }
+]

Added value: +[
+  {
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Added value: +[
+  {
+    "url": "https://pipeworx.io"
+  }
+]

Added value: +[
+  {
+    "message": "Fleet #2184 smoke test: verifying pipeworx_feedback example call returns non-empty.",
+    "type": "other"
+  }
+]

Added value: +[
+  {
+    "window": "7d"
+  }
+]

Added value: +[
+  {
+    "topic": "Fed rate decision"
+  }
+]

Added value: +[
+  {
+    "days": 14,
+    "window": "1wk"
+  }
+]

Added value: +[
+  {
+    "limit": 5,
+    "window": "1wk"
+  }
+]

Previous value: -"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage."New value: +"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage and Polymarket's own taker fee."

Previous value: -"Assumed execution slippage in percentage points per leg (default 0.3). Subtracted from raw |edge| before ranking and Kelly sizing. Polymarket has zero trading fees as of 2024 but bid/ask + thin depth typically eats 20-50bp per trade. Bump for very thin partitions; drop to 0 if you have a smarter fill model."New value: +"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."

Added value: +[
+  {
+    "market": "will-the-fed-increase-interest-rates-by-25-bps-after-the-december-2026-meeting-20260729232808636",
+    "side": "buy_yes",
+    "size_usd": 1000
+  }
+]

Added value: +[
+  {
+    "since": "30d",
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Added value: +[
+  {
+    "key": "target_ticker",
+    "value": "AAPL"
+  }
+]

Added value: +[
+  {
+    "type": "company",
+    "value": "AAPL"
+  }
+]

Added value: +[
+  {
+    "entities": [
+      "Pipeworx",
+      "Zapier"
+    ]
+  }
+]

Added value: +[
+  {
+    "package": "left-pad"
+  }
+]

Added value: +[
+  {
+    "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."
+  }
+]

Added value: +[
+  {
+    "topic": "finance"
+  }
+]

Added value: +[
+  {
+    "claim": "Apple's fiscal 2023 revenue was $383 billion"
+  }
+]

Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]

Previous value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"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 stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."

Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]

Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."

Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]

Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — 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."

Previous value: -"Optional. Filter to patents granted on/after this date (ISO YYYY-MM-DD)."New value: +"Optional. Filter to patents GRANTED (issued) on/after this date (ISO YYYY-MM-DD). This is the argument that answers \"recent/latest patents\" — without it, results are unexamined applications, not issued patents. Accepted synonym: `issued_after`."

Previous value: -"Optional. Filter to patents granted on/before this date (ISO YYYY-MM-DD)."New value: +"Optional. Filter to patents GRANTED (issued) on/before this date (ISO YYYY-MM-DD). Accepted synonym: `issued_before`."

Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."

Previous value: -[
-  "company"
-]New value: +[
+  "company",
+  "ticker"
+]

Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."