CULT+MATH Decision Briefs
REMOTE · CULTMATH.COM
Odds and forecasts on the numbers executives plan against, plus free studies and Decision Briefs.
Available components
Last scanned (17 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 22906 tokens (~322/item across 71 items; 71 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (83% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 71 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 72 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_standards” rewrote its description, which is the text the model reads security
- New tool “get_framework” functional
- New tool “list_frameworks” functional
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “run_college_athletics” functional
- New tool “run_sports_business_benchmark” functional
- “run_concentration_benchmark” reworded the description of “peers” cosmetic
- “run_disclosure_check” reworded the description of “peers” cosmetic
- “run_peer_benchmark” reworded the description of “metric” cosmetic
- 18 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_standards” rewrote its description, which is the text the model reads security
- Tool “run_ai_visibility” rewrote its description, which is the text the model reads security
- Tool “run_ai_visibility_quick” rewrote its description, which is the text the model reads security
- Tool “run_angle_demand” rewrote its description, which is the text the model reads security
- Tool “run_answer_share” rewrote its description, which is the text the model reads security
- Tool “run_answer_share_quick” rewrote its description, which is the text the model reads security
- Tool “run_channel_mix” rewrote its description, which is the text the model reads security
- Tool “run_city_profile” rewrote its description, which is the text the model reads security
- Tool “run_claim_check” rewrote its description, which is the text the model reads security
- Tool “run_comment_themes” rewrote its description, which is the text the model reads security
- Tool “run_concentration_benchmark” rewrote its description, which is the text the model reads security
- Tool “run_contractor_revenue” rewrote its description, which is the text the model reads security
- Tool “run_cost_squeeze” rewrote its description, which is the text the model reads security
- Tool “run_customer_concentration” rewrote its description, which is the text the model reads security
- Tool “run_deal_activity” rewrote its description, which is the text the model reads security
- Tool “run_deal_comps” rewrote its description, which is the text the model reads security
- Tool “run_demand_check” rewrote its description, which is the text the model reads security
- Tool “run_demand_durability” rewrote its description, which is the text the model reads security
- Tool “run_disclosure_check” rewrote its description, which is the text the model reads security
- Tool “run_effective_duty” rewrote its description, which is the text the model reads security
- Tool “run_fad_check” rewrote its description, which is the text the model reads security
- Tool “run_filing_trend” rewrote its description, which is the text the model reads security
- Tool “run_launch_lift” rewrote its description, which is the text the model reads security
- Tool “run_merger_review” rewrote its description, which is the text the model reads security
- Tool “run_peer_benchmark” rewrote its description, which is the text the model reads security
- Tool “run_premium_check” rewrote its description, which is the text the model reads security
- Tool “run_private_raises” rewrote its description, which is the text the model reads security
- Tool “run_regulatory_clock” rewrote its description, which is the text the model reads security
- Tool “run_regulatory_trend” rewrote its description, which is the text the model reads security
- Tool “run_revenue_mix” rewrote its description, which is the text the model reads security
- Tool “run_series_forecast” rewrote its description, which is the text the model reads security
- Tool “run_share_of_search” rewrote its description, which is the text the model reads security
- Tool “run_spend_trend” rewrote its description, which is the text the model reads security
- Tool “run_tariff_clock” rewrote its description, which is the text the model reads security
- Tool “run_threshold_odds” rewrote its description, which is the text the model reads security
- Tool “run_trade_concentration” rewrote its description, which is the text the model reads security
- Tool “run_triangulation” rewrote its description, which is the text the model reads security
- Tool “run_write_downs” rewrote its description, which is the text the model reads security
- Schema quality: 285 → 324 ▼ functional
- Tool coverage: 79% → 85% ▲ functional
- New tool “run_ai_brand_check” functional
- New tool “run_ai_readiness” functional
- New tool “run_audience_map” functional
- New tool “run_audience_size” functional
- New tool “run_business_universe” functional
- New tool “run_buyer_roles” functional
- New tool “run_channel_benchmark” functional
- New tool “run_device_clearances” functional
- New tool “run_incentive_tracts” functional
- New tool “run_news_pulse” functional
- New tool “run_news_share_of_voice” functional
- New tool “run_parcel_mix” functional
- New tool “run_recall_watch” functional
- New tool “run_search_vs_ai” functional
- New tool “run_social_pulse” functional
- New tool “run_social_share_of_voice” functional
- New tool “run_topic_views” functional
- New tool “run_trade_area” functional
- New tool “run_trial_pipeline” functional
- New tool “run_wallet_size” functional
- 17 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “run_tariff_clock” rewrote its description, which is the text the model reads security
- Schema quality: 10623 → 13405 ▼ functional
- New tool “get_standard” functional
- New tool “list_standards” functional
- New tool “run_city_profile” functional
- New tool “run_concentration_benchmark” functional
- New tool “run_contractor_revenue” functional
- New tool “run_deal_comps” functional
- New tool “run_demand_durability” functional
- New tool “run_merger_review” functional
- New tool “run_private_raises” functional
- New tool “tell_cultmath” functional
- 16 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_decision_brief” rewrote its description, which is the text the model reads security
- Tool “list_decisions” rewrote its description, which is the text the model reads security
- Tool “run_trade_concentration” rewrote its description, which is the text the model reads security
- New tool “run_effective_duty” functional
- New tool “run_tariff_clock” functional
- 15 Nov 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_decision_brief” rewrote its description, which is the text the model reads security
- Tool “get_document” rewrote its description, which is the text the model reads security
- Tool “list_decision_briefs” rewrote its description, which is the text the model reads security
- Tool “list_decisions” rewrote its description, which is the text the model reads security
- Tool “run_ai_visibility” rewrote its description, which is the text the model reads security
- Tool “run_ai_visibility_quick” rewrote its description, which is the text the model reads security
- Tool “run_angle_demand” rewrote its description, which is the text the model reads security
- Tool “run_answer_share” rewrote its description, which is the text the model reads security
- Tool “run_answer_share_quick” rewrote its description, which is the text the model reads security
- Tool “run_channel_mix” rewrote its description, which is the text the model reads security
- Tool “run_claim_check” rewrote its description, which is the text the model reads security
- Tool “run_comment_themes” rewrote its description, which is the text the model reads security
- Tool “run_cost_squeeze” rewrote its description, which is the text the model reads security
- Tool “run_customer_concentration” rewrote its description, which is the text the model reads security
- Tool “run_deal_activity” rewrote its description, which is the text the model reads security
- Tool “run_demand_check” rewrote its description, which is the text the model reads security
- Tool “run_disclosure_check” rewrote its description, which is the text the model reads security
- Tool “run_fad_check” rewrote its description, which is the text the model reads security
- Tool “run_filing_trend” rewrote its description, which is the text the model reads security
- Tool “run_launch_lift” rewrote its description, which is the text the model reads security
- Tool “run_peer_benchmark” rewrote its description, which is the text the model reads security
- Tool “run_premium_check” rewrote its description, which is the text the model reads security
- Tool “run_regulatory_clock” rewrote its description, which is the text the model reads security
- Tool “run_regulatory_trend” rewrote its description, which is the text the model reads security
- Tool “run_revenue_mix” rewrote its description, which is the text the model reads security
- Tool “run_series_forecast” rewrote its description, which is the text the model reads security
- Tool “run_share_of_search” rewrote its description, which is the text the model reads security
- Tool “run_spend_trend” rewrote its description, which is the text the model reads security
- Tool “run_threshold_odds” rewrote its description, which is the text the model reads security
- Tool “run_trade_concentration” rewrote its description, which is the text the model reads security
- Tool “run_triangulation” rewrote its description, which is the text the model reads security
- Tool “run_write_downs” rewrote its description, which is the text the model reads security
- Tool “search_cultmath” rewrote its description, which is the text the model reads security
- Schema quality: 325 → 281 ▲ functional
- Tool “run_ai_visibility” now declares an output schema ▲ functional
- Tool “run_ai_visibility_quick” now declares an output schema ▲ functional
- Tool “run_angle_demand” now declares an output schema ▲ functional
- Tool “run_answer_share” now declares an output schema ▲ functional
- Tool “run_answer_share_quick” now declares an output schema ▲ functional
- Tool “run_channel_mix” now declares an output schema ▲ functional
- Tool “run_claim_check” now declares an output schema ▲ functional
- Tool “run_comment_themes” now declares an output schema ▲ functional
- Tool “run_cost_squeeze” now declares an output schema ▲ functional
- Tool “run_customer_concentration” now declares an output schema ▲ functional
- Tool “run_deal_activity” now declares an output schema ▲ functional
- Tool “run_demand_check” now declares an output schema ▲ functional
- Tool “run_disclosure_check” now declares an output schema ▲ functional
- Tool “run_fad_check” now declares an output schema ▲ functional
- Tool “run_filing_trend” now declares an output schema ▲ functional
- Tool “run_launch_lift” now declares an output schema ▲ functional
- Tool “run_peer_benchmark” now declares an output schema ▲ functional
- Tool “run_premium_check” now declares an output schema ▲ functional
- Tool “run_regulatory_clock” now declares an output schema ▲ functional
- Tool “run_regulatory_trend” now declares an output schema ▲ functional
- Tool “run_revenue_mix” now declares an output schema ▲ functional
- Tool “run_series_forecast” now declares an output schema ▲ functional
- Tool “run_share_of_search” now declares an output schema ▲ functional
- Tool “run_spend_trend” now declares an output schema ▲ functional
- Tool “run_threshold_odds” now declares an output schema ▲ functional
- Tool “run_trade_concentration” now declares an output schema ▲ functional
- Tool “run_triangulation” now declares an output schema ▲ functional
- Tool “run_write_downs” now declares an output schema ▲ functional
- First check of Tool coverage: 80 functional
- “get_decision_evidence” reworded the description of “decision_id” cosmetic
- “run_premium_check” reworded the description of “brand” cosmetic
- 14 Nov 26 0
- Server version: 1.2.0 → 1.3.0 functional
- New tool “run_series_forecast” functional
- New tool “run_threshold_odds” functional
- 13 Nov 26 +1
- Tool “run_ai_visibility” rewrote its description, which is the text the model reads security
- Tool “run_ai_visibility_quick” rewrote its description, which is the text the model reads security
- Tool “run_angle_demand” rewrote its description, which is the text the model reads security
- Tool “run_answer_share” rewrote its description, which is the text the model reads security
- Tool “run_answer_share_quick” rewrote its description, which is the text the model reads security
- Tool “run_channel_mix” rewrote its description, which is the text the model reads security
- Tool “run_claim_check” rewrote its description, which is the text the model reads security
- Tool “run_deal_activity” rewrote its description, which is the text the model reads security
- Tool “run_demand_check” rewrote its description, which is the text the model reads security
- Tool “run_disclosure_check” rewrote its description, which is the text the model reads security
- Tool “run_fad_check” rewrote its description, which is the text the model reads security
- Tool “run_filing_trend” rewrote its description, which is the text the model reads security
- Tool “run_peer_benchmark” rewrote its description, which is the text the model reads security
- Tool “run_premium_check” rewrote its description, which is the text the model reads security
- Tool “run_regulatory_clock” rewrote its description, which is the text the model reads security
- Tool “run_regulatory_trend” rewrote its description, which is the text the model reads security
- Tool “run_share_of_search” rewrote its description, which is the text the model reads security
- Tool “run_spend_trend” rewrote its description, which is the text the model reads security
- Tool “run_triangulation” rewrote its description, which is the text the model reads security
- Schema quality: 8000 → 10525 ▼ functional
- New tool “run_comment_themes” functional
- New tool “run_cost_squeeze” functional
- New tool “run_customer_concentration” functional
- New tool “run_launch_lift” functional
- New tool “run_revenue_mix” functional
- New tool “run_trade_concentration” functional
- New tool “run_write_downs” functional
- “run_peer_benchmark” reworded the description of “metric” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://cultmath.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cultmath.com | CN=YR1,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | RSA 2048 | SHA256-RSA | 64b6c7c8768c332cb6dfd69acad993cff7e |
| SANs: cultmath.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of cultmath.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| cultmath.com. | DS published | 2371 | 13 | Verified |
| cultmath.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src https://fonts.gstatic.com; img-src 'self' data: https://www.googletagmanager.com https://*.google.com https://*.googleadservices.com https://*.doubleclick.net https://px.ads.linkedin.com https://i.ytimg.com; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://www.googleadservices.com https://www.google.com https://snap.licdn.com; frame-src 'self' https://shaman.cultmath.com https://td.doubleclick.net https://www.googletagmanager.com https://www.youtube-nocookie.com; connect-src 'self' https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com https://*.google.com https://*.googleadservices.com https://*.doubleclick.net https://px.ads.linkedin.com |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cultmath.com/mcp | Verified | 200 | |
| http (plaintext) | http://cultmath.com/mcp | HTTPS enforced | 308 | https://cultmath.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
run_disclosure_check Has anyone started reporting this number? ~538
Use when the user asks whether any company, or which of a named set of competitors, now reports a figure (a franchise share, ARPU, a retention rate, a concentration, a multiple), or whether a public comparable discloses the metric a deal model depends on. Returns, from SEC EDGAR full-text search, which filers use the phrase in their filings over the years given, with the first and latest filing linked; for named peers, who does, who does not, and who could not be measured because they filed nothing. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: filers by year (start-end); compare: peers; segment: form (10-K, 10-Q, 8-K). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For the share of all 10-K filers over time, use run_filing_trend. A real sample of this run, free: https://cultmath.com/agent/samples/disclosure-check.json
| Name | Type | Req | Description |
|---|---|---|---|
| end | integer | – | Last year. At most 10 years per run. |
| form | string | – | Filing type. Default 10-K. |
| peers | string | – | Optional: 2-10 tickers, comma-separated, from: PEP, KO, K, POST, KDP, CELH, UTZ, HRL, GIS, KHC, CAG, CPB, HSY, MDLZ, SJM, CLX, CL, CHD, PG, SMPL, BRBR, MSFT, EA, TTWO, RBLX, OMC, STGW, CRM, HUBS, TDO… |
| phrase | string | yes | The phrase to measure, without quote marks. |
| start | integer | – | First year. Default: two years ago. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_effective_duty What duty did importers actually pay on this product? ~458
Use when the user is pricing, sourcing or sizing a refund claim and needs the tariff actually paid on a product, not the headline rate: "what duty are we really paying on chips from Malaysia?", "how much did the tariff on this product rise this year?". Returns duty as a share of value for all countries, the five largest sources and any countries you name, in two months, with the highest-paying source over $1M, with the change in points, from US Census Bureau calculated duty. An estimate at entry: it ran about 10% below Treasury collections. Months from January 2025 to July 2026. Refuses before you are charged if the months have under $1 million of imports or the partner rows do not add up. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: two months (from, to); compare: countries; place: countries. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For where US imports of the product come from, and who gained share, use run_trade_concentration. For the tariff actions behind a rate, use run_tariff_clock.
| Name | Type | Req | Description |
|---|---|---|---|
| countries | string | – | Optional: up to 5 source countries to show by name, comma-separated, e.g. "China, Malaysia". The five largest sources are always shown. |
| from | string | yes | The earlier month, YYYY-MM, January 2025 to July 2026. |
| hs | string | yes | A 4-, 6- or 10-digit HS code, e.g. "8542" for integrated circuits. |
| to | string | yes | The later month, YYYY-MM, after from, up to July 2026. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_fad_check Is this moment lasting, or past its peak? ~328
Use when the user is writing a creative or campaign brief, or weighing a trend, and asks whether a moment, ingredient, format or cultural theme is a lasting shift or a fad that has peaked. Returns, for US Google Trends and English Wikipedia interest since 2016, how much of its best 12 months the subject keeps today, with controls, with months since the peak and a verdict: lasting, fading, past its peak, still rising, or signals disagree. Ratios and dates only. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: monthly since January 2016. Price: $0.07 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For category growth against the market, use run_demand_check. A real sample of this run, free: https://cultmath.com/agent/samples/fad-check.json
| Name | Type | Req | Description |
|---|---|---|---|
| article | string | yes | The English Wikipedia article on the same subject, e.g. "Cottage cheese". |
| term | string | yes | The moment as people search for it, e.g. "cottage cheese". |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_filing_trend Is this becoming material to companies? ~356
Use when the user asks whether a risk, technology or theme is spreading through public companies, or whether companies now treat it as material. Returns, year by year, the share of U.S. 10-K filers that mention the phrase, from SEC EDGAR full-text search, with a denominator control ("competition") and a null control ("shrinkflation") that must read 0. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: share by year (start-end). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For named companies rather than all filers, use run_disclosure_check; for filings, rules and spending together, use run_triangulation. A real sample of this run, free: https://cultmath.com/agent/samples/filing-trend.json
| Name | Type | Req | Description |
|---|---|---|---|
| end | integer | – | Last year, not in the future. Default: this year. At most 10 years per run. |
| phrase | string | yes | The phrase to count, without quote marks, e.g. "tariff" or "GLP-1". |
| start | integer | – | First year (2001 onward). Default: four years ago. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_incentive_tracts Is this site in an Opportunity Zone or an NMTC-eligible tract? ~361
Use when the user is structuring a real estate or business investment and asks about tax-advantaged capital for a specific site: "is this address in an Opportunity Zone?", "will it still be one in 2027?", "can this project use New Markets Tax Credits?". Geocodes each address with the Census Geocoder and checks its tract against the CDFI Fund’s lists: Opportunity Zones 1.0 (through 2028), Opportunity Zones 2.0 (from January 1, 2027) and NMTC low-income-community eligibility. An unmatched address is reported as unmatched, never as "not in a zone". Refuses before you are charged if the lists fail their integrity check or no address matches. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: current designations, plus OZ 2.0 from January 1, 2027; compare: addresses (up to 10); place: address. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For who lives around the site, use run_trade_area.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | One US street address. |
| addresses | array | – | Up to 10 US street addresses, for a portfolio. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_launch_lift Has this launch lifted the brand it came from? ~338
Use when the user asks whether a line extension, spin-off, sequel, collaboration or new product lifted interest in the parent brand or show, or is weighing a launch on the promise of a halo. Returns, for the launch month, the parent's US search change against the three months before, the best same-window change in every other year since 2019 as a seasonal control, and a verdict against a +20% bar set before the pull: lifted, seasonal, or no lift; optionally English Wikipedia as a second signal. Ratios only. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: the launch month against the same window in other years. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound.
| Name | Type | Req | Description |
|---|---|---|---|
| article | string | – | Optional: the English Wikipedia article on the parent, e.g. "Power (TV series)". |
| launch | string | yes | The launch or premiere month, YYYY-MM, 2020-04 or later and finished. |
| parent | string | yes | The parent brand or show as people search for it, e.g. "power" or "oreo". |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_merger_review Do antitrust agencies require remedies for mergers in this sector, and how often? ~336
Use when the user is setting regulatory-risk terms for a deal (outside date, reverse break fee, divestiture commitments) or asks whether regulators have blocked or conditioned deals in a sector: "have the FTC or DOJ forced divestitures in hospital mergers?". Returns FTC consent orders and Justice Department consent decrees from the Federal Register that mention an acquisition and the phrase, counted by year, each with its title, date, document number and link. Settlements only: litigated and abandoned deals are not counted. Refuses before you are charged if its controls show the search or the agency filter is not working. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: by year since since_year; segment: phrase (sector or product). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For federal rules with comment deadlines in the sector, use run_regulatory_clock.
| Name | Type | Req | Description |
|---|---|---|---|
| phrase | string | yes | A sector or product, e.g. "hospital", "grocery", "veterinary". |
| since_year | integer | – | First year to count. Default 8 years back. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_news_pulse Is this in the news, is it spiking, and how is the tone moving? ~278
Currently switched off: it answers "not available" and charges nothing. Use when the user is monitoring a brand, competitor, executive, product or issue in the media: "how much press is Kraft Heinz getting?", "did coverage of this recall spike?", "is the tone turning negative?". Returns articles by week from GDELT's global news monitoring, spike weeks, share of all coverage, average tone and whether it is warming or cooling, the most frequent outlets, and the top headlines with links (never article text). Refuses before you are charged if nothing matches or the counts fail their checks. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: by week over days. To compare coverage with competitors, use run_news_share_of_voice; for online discussion, use run_social_pulse.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days back from today. Default 90. |
| query | string | yes | A phrase, matched exactly, e.g. "Kraft Heinz". |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_news_share_of_voice Who is getting the most news coverage, and in what tone? ~241
Currently switched off: it answers "not available" and charges nothing. Use when the user is comparing media presence with competitors: "who gets more press, Coca-Cola or PepsiCo?", "is our share of coverage growing against theirs?". Returns each name's articles, share of the combined coverage, average tone and busiest week, from GDELT's global news monitoring. Refuses before you are charged if none has coverage. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: busiest week over days; compare: names (2-3). For one name in depth (spikes, outlets, headlines), use run_news_pulse.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days back from today. Default 30. |
| names | array | yes | 2-3 names to compare. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_parcel_mix What is the land around this Houston-area site used for? ~370
Use when the user is screening a site in Harris County, Texas (Houston) for development, investment or lending and asks what surrounds it: "what is around this lot?", "how much vacant land is nearby?", "is this block mostly commercial or residential?". Returns the parcels within the radius by land-use category from the Harris County Appraisal District, with counts, appraised value, the vacant share and the site parcel’s class. Houston has no zoning code, so this is land use, not zoning; owner names are never returned. Refuses before you are charged outside Harris County or if the totals do not reconcile. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: one release (current appraisal year); place: address or lat/lon, radius_miles (Harris County); segment: land-use category (in the result). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For who lives around the site, use run_trade_area.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | A US street address. Give this or lat and lon. |
| lat | number | – | Latitude in decimal degrees, with lon. |
| lon | number | – | Longitude in decimal degrees, with lat. |
| radius_miles | number | – | Radius in miles. Default 0.5. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_peer_benchmark Are we ahead of or behind our peers on this metric? ~406
Use when the user names a public company and asks how its growth, margin, R&D or marketing spend compares with competitors. Returns the company's revenue growth, gross margin, or R&D or sales-and-marketing as a share of revenue for its latest fiscal year, each peer's, the peer median, the gap and the rank, from SEC EDGAR XBRL as filed; every excluded peer is named with the reason. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: latest fiscal year only; compare: peers (the comparison set); segment: metric (growth, margin, R&D, S&M, ad intensity). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For where the revenue comes from, use run_revenue_mix. A real sample of this run, free: https://cultmath.com/agent/samples/peer-benchmark.json
| Name | Type | Req | Description |
|---|---|---|---|
| metric | string | yes | What to compare, from each company's latest 10-K: revenue_growth (revenue growth), gross_margin (gross margin), rd_intensity (R&D as a share of revenue), sm_intensity (sales and marketing as a share… |
| peers | string | yes | 2-6 peer tickers from the same list, comma-separated, e.g. "CAG,CPB,KHC". |
| ticker | string | yes | The company. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_premium_check Is our premium holding, or are buyers hunting for a cheaper way in? ~322
Use when the user asks whether their price premium is holding, whether customers are trading down, or whether a price rise is hurting demand. Returns the share of the brand's US Google searches that look for a cheaper way in (price, cheap, discount, coupon, dupe, alternative, sale), against the year before, with a verdict (eroding, holding, strengthening) and each modifier's trend. Shares and bands only. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: latest 12 months against the 12 before. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For brands' shares of all searches, use run_share_of_search; for which reasons to buy people search for, use run_angle_demand. A real sample of this run, free: https://cultmath.com/agent/samples/premium-check.json
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | One brand, spelled as people type it into Google, e.g. "Oatly". The run adds the price-seeking words itself. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_private_raises Is private money flowing into this industry or away from it? ~301
Use when the user asks where private capital is going, how crowded an industry is with funded competitors, or whether fund-raising is picking up: "are biotech private raises up this year?", "who raised money in restaurants lately?". Returns, quarter by quarter, Form D notices naming the industry group as a share of all Form D notices, whether that share is rising or falling, and the latest issuers with their stated offering amounts and amounts sold, each linked. Notices, not completed raises. Refuses before you are charged if its controls fail. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: share by quarter (quarters); segment: industry. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For public-company merger activity in a sector, use run_deal_activity.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | yes | A Form D industry group. |
| quarters | integer | – | Quarters to count. Default 8. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_recall_watch Is this product category being recalled more? ~321
Use when the user is weighing quality or supplier risk in a food, drug or device category, diligencing a manufacturer, or asks about recall history: "are ice cream recalls rising?", "who recalls the most peanut butter?". Returns FDA recall records per year from openFDA enforcement reports, the direction, the split by class (Class I is the most serious) and the firms with the most recalls. No recall in the window is a sound result. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: by year (years); segment: category (food, drug, device), class and firm (in the result). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For who is getting devices cleared in the category, use run_device_clearances.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Which FDA enforcement report to read. |
| phrase | string | yes | Matched against product descriptions, e.g. "peanut butter". |
| years | integer | – | Complete calendar years to cover, ending last year. Default 6. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_regulatory_clock Is there still time to respond to a rule on this? ~292
Use when the user asks whether a U.S. federal rule on a topic is open for comment, when the deadline is, or when a final rule takes effect. Returns, as of today, the Federal Register documents mentioning the phrase whose comment period is still open (with days left) and the final rules still waiting to take effect, optionally for one agency, each linked. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: as of today: open comment periods and dates ahead; segment: agency. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For the long-run trend in rule-making, use run_regulatory_trend. A real sample of this run, free: https://cultmath.com/agent/samples/regulatory-clock.json
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Optional: one agency only. |
| phrase | string | yes | The phrase to measure, without quote marks. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_regulatory_trend Are regulators moving on this? ~351
Use when the user asks whether rules are coming on a topic, or how much federal rule-making mentions it, optionally for one agency. Returns, year by year, the share of U.S. federal final and proposed rules that mention the phrase, from the Federal Register, against every final and proposed rule that year, with a null control that must read 0. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. For deadlines and comment windows, use run_regulatory_clock. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: share by year; segment: agency narrows to one regulator. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. A real sample of this run, free: https://cultmath.com/agent/samples/regulatory-trend.json
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Optional: count only this agency's rules. |
| end | integer | – | Last year, not in the future. Default: this year. At most 10 years per run. |
| phrase | string | yes | The phrase to count, without quote marks, e.g. "front-of-package" or "PFAS". |
| start | integer | – | First year (1994 onward). Default: four years ago. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_revenue_mix Where does this company's revenue come from, and how is the mix moving? ~300
Use when the user names a public company and asks how its revenue splits (by platform, revenue type, channel, product or region) or whether its mix is shifting, for example toward mobile, live services or digital. Returns every revenue split the company files that adds up to reported revenue across its three latest 10-Ks, with each fiscal year's shares and dollar values and each filing's citation, from SEC EDGAR XBRL as filed. If the company files no split this run can verify, it refuses before you are charged. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: three latest 10-Ks; segment: every split the company files (product, channel, region). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For dependence on one customer, use run_customer_concentration; for margins against peers, use run_peer_benchmark.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | The company. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_search_vs_ai Do this question’s Google winners also win the AI answer? ~323
Use when the user is deciding between SEO and AI-visibility (GEO) work, or asks whether ranking in Google gets them cited by ChatGPT, Claude, Gemini or Perplexity: "we rank #2 on Google, why don’t AI answers cite us?". Returns Google’s top 10 organic domains for one question, how many of them four AI assistants cite across eight answers, the domains only the AI cites (the sources to earn coverage in), and, if a domain is given, its Google rank and AI citation count. Refuses before you are charged if either side cannot be measured. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: one moment; re-run to build a series; segment: question. Price: $0.74 per run over x402 (USDC on Base, no account needed), or $1.06 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For who owns the answers across a whole category, use run_answer_share.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional: your domain, to see where it stands in both. |
| question | string | yes | The question as a buyer would type or ask it. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_series_forecast What will this US series do over the next 12 months? ~307
Use when the user is setting a plan, budget or inventory for the next year and needs where US retail sales, prices (CPI), employment and wages, industrial production, housing or vehicle sales are heading. Returns a 12-month forecast with an 80% band, next to "same month last year", from a model backtested on the series' own last three years. Refuses before you are charged when last year's same month forecast it better, and says by how much. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: 12-month forecast with three years of backtest; segment: series. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For the probability of crossing one line, use run_threshold_odds.
| Name | Type | Req | Description |
|---|---|---|---|
| series | string | yes | The FRED series ID, e.g. RSXFSN (retail sales) or CPIAUCNS (CPI, all items). Not seasonally adjusted. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_share_of_search Who is gaining share of search in this category? ~311
Use when the user asks who they really compete with, whether a competitor is gaining on them, or how their brand interest compares with rivals. Returns each brand's share of US Google searches among the brands named, the change in points against the year before, search growth and a volume band, ranked. Shares and bands only, never monthly volumes. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: latest 12 months against the 12 before; compare: rivals. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For where searchers end up (retailers, reviews, brand sites), use run_channel_mix; for price-seeking searches on one brand, use run_premium_check. A real sample of this run, free: https://cultmath.com/agent/samples/share-of-search.json
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Your brand as people search for it. |
| rivals | string | yes | 2-6 competing brands, comma-separated. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_social_pulse Are people talking about this online, and is it spiking? ~294
Use when the user is listening for discussion of a brand, product, launch or category among technical and early-adopter audiences: "is anyone talking about our launch?", "did this topic spike this month?". Returns weekly mentions on Hacker News and Bluesky, spike weeks, and the Hacker News stories that drew the most points and comments. Not Reddit or X. Bluesky is counted only, never quoted. Refuses before you are charged if nothing matches. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: by week over days; segment: platform (Hacker News, Bluesky). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For news coverage, use run_news_pulse; to compare names, use run_social_share_of_voice.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days back from today. Default 30. |
| query | string | yes | A phrase, matched exactly. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_social_share_of_voice Which of these names do people discuss most online? ~274
Use when the user is comparing community attention across competitors or products: "do developers talk about us or them more?", "which tool gets more discussion?". Returns each name's Hacker News mentions and Bluesky posts, with its share on each. Not Reddit or X. Counts only. Refuses before you are charged if none has a mention. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: over days; compare: names (2-4); segment: platform (Hacker News, Bluesky). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For one name in depth (weekly spikes, top threads), use run_social_pulse.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days back from today. Default 30. |
| names | array | yes | 2-4 names to compare. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_spend_trend Is the government actually spending on this? ~295
Use when the user asks whether federal money backs a market, technology or policy, or wants evidence beyond announcements. Returns the share of U.S. federal prime contract obligations matching the phrase, by fiscal year, from USAspending.gov, against all contract obligations. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: share by fiscal year (start-end). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. To check 10-K filings and federal rules as well, use run_triangulation. A real sample of this run, free: https://cultmath.com/agent/samples/spend-trend.json
| Name | Type | Req | Description |
|---|---|---|---|
| end | integer | – | Last fiscal year, not after the current one. At most 10. |
| phrase | string | yes | The phrase to measure, without quote marks. |
| start | integer | – | First federal fiscal year. Default: four years ago. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_sports_business_benchmark Which listed sports businesses are growing, making money and spending to acquire customers? ~447
Use when the user is an investor, deal team or league business office comparing sports companies: "is DraftKings growing faster than Flutter?", "which sportsbook spends most on marketing?", "who has the best margins among team owners?". Returns, for each company's latest fiscal year from its 10-K as filed: revenue, revenue growth, operating margin, sales and marketing and advertising as a share of revenue, the group medians and the filing behind each row. Covers DKNG, FLUT, CHDN, PENN, RSI, MSGK, BATRA, TKO, LYV, SPHR, MSGE. Refuses before you are charged if a filer's name does not match the company. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: latest fiscal year, with growth on the year before; compare: group or tickers (2-8); segment: metric (in the result). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For one company against hand-picked peers on a single metric, use run_peer_benchmark; for college programs, use run_college_athletics.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | A preset group: betting (DKNG, FLUT, CHDN, PENN, RSI), teams (MSGK, BATRA, TKO) or live (LYV, SPHR, MSGE). Give a group or tickers. |
| tickers | string | – | Or 2-8 tickers, comma-separated, from: DKNG, FLUT, CHDN, PENN, RSI, MSGK, BATRA, TKO, LYV, SPHR, MSGE. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_tariff_clock Which tariff actions touch this product, and what dates are coming? ~369
Use when the user is timing a sourcing, pricing or comment decision around US tariffs: "is anything new on Section 301 for Vietnam?", "when do the chip tariffs take effect?", "can we still comment on the excess-capacity investigation?". Returns recent tariff actions from USTR, Commerce (ITA and BIS), CBP and presidential proclamations that mention the phrase, what is open for comment and for how long, and what takes effect next, each with its Federal Register document number. Refuses before you are charged if its controls show the search or the agency filter is not working. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: recent actions over since_days, and dates ahead; segment: agency. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For the duty actually paid on a product since those actions, use run_effective_duty.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Optional: one agency only (ustr, ita, bis, cbp, president). |
| phrase | string | yes | A product, an HTS heading (e.g. "8542"), a country, or an action such as "Section 301". |
| since_days | integer | – | How far back to list recent actions, in days. Default 180. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_threshold_odds What are the odds this US series crosses a line in the next three months? ~491
Use when the user's plan turns on whether rent, food prices, household energy, wages or retail sales will be above or below a level soon: "what are the chances rent inflation is above 3% in December?", "will grocery store sales grow more than 2%?". The operating numbers a plan is built on, not headline CPI. Returns a probability in percent and in words, the central forecast and its 80% range, and the same question answered by "same month last year" and by the historical base rate, so you can see what the model adds. Up to 3 months past the latest published figure only: further out, the method missed by up to 21 points in testing. Refuses before you are charged when the series fails its benchmark today or the month is out of range. Each sold call is scored when the month is published. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: one month up to three ahead (month); segment: series, line (yoy_pct) and direction. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For the full 12-month path, use run_series_forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Whether you want the odds of being above or below the line. Default above. |
| month | string | yes | The target month, YYYY-MM, 1 to 3 months after the latest published figure. |
| series | string | yes | The FRED series ID, e.g. CUUR0000SEHA (rent), CUUR0000SAF11 (food at home), CEU0500000003 (hourly earnings), MRTSSM4451USN (grocery store sales), RSXFSN (retail sales). |
| yoy_pct | number | yes | The line: year-on-year change in percent, e.g. 3 for 3.0%. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_topic_views Which topics on this subject are getting views on YouTube? ~385
Use when the user is a creator, creator manager or brand team planning content on a subject and asks which angle gets watched: "which GTA 6 topics are pulling views right now?", "do trailer videos beat leak videos?", "who owns the views on this?". Returns YouTube's most-viewed videos on the subject from the window, split by the title topics you name: videos, median views and median views per day for each, Shorts against long-form, the top channels' share of views and the top 10 videos. Public counts only; results cannot be published. Refuses before you are charged if the search drifts off the subject. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: one window of days; re-run for a later window; segment: topics; Shorts against long-form. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. To compare named channels rather than topics, use run_channel_benchmark; for what viewers say under one video, use run_comment_themes.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days back from today. Default 30. |
| query | string | yes | The subject, as people search it, e.g. "GTA 6". |
| topics | array | yes | 2-4 title words or short phrases to split the videos by, e.g. ["trailer","leak"]. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_trade_area Who lives within a few miles of this site? ~373
Use when the user is choosing or underwriting a site for a store, restaurant, clinic, school or property and asks about the catchment: "how many people live within 3 miles?", "what is household income around this address?", "how many schools are nearby?". Returns population, households, mean household income, the renter share and density within the radius, from Census ACS 5-year block groups, plus the number of public schools from NCES. A straight-line circle, not drive time. Refuses before you are charged if the area is empty or the totals fail their checks. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: one release (ACS 5-year); place: address or lat/lon, radius_miles. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For whether the site is in an Opportunity Zone or NMTC tract, use run_incentive_tracts; for a whole city’s housing supply against rent, use run_city_profile.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | A US street address. Give this or lat and lon. |
| lat | number | – | Latitude in decimal degrees, with lon. |
| lon | number | – | Longitude in decimal degrees, with lat. |
| radius_miles | number | – | Radius in miles. Default 3. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_trade_concentration Where do US imports of this product come from now? ~332
Use when the user asks whether supply of a product has really diversified, how exposed US imports are to one country, or who gained share after tariffs or reshoring. Returns, for two years, the top-three partners' share of US imports of the HS code, the largest single source, a concentration index, and the partners that gained and lost the most share, from US Census Bureau trade data. Refuses before you are charged if the partner rows do not add up to the world total. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: two years (start, end); place: partner countries (in the result). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For the duty actually paid on that product, by country, use run_effective_duty.
| Name | Type | Req | Description |
|---|---|---|---|
| end | integer | yes | The later year (the latest full year is usually the one before last). |
| hs | string | yes | A 4- or 6-digit HS code, e.g. "8542" for integrated circuits. |
| start | integer | yes | The earlier year. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_trial_pipeline Is the clinical pipeline for this condition crowding? ~332
Use when the user is sizing a therapeutic area, diligencing a biotech or medtech target, or asks how many companies are running trials for a condition: "how crowded is the obesity pipeline?", "who sponsors the most trials in this disease?". Returns interventional trials started per year from ClinicalTrials.gov (all, industry-sponsored, Phase 3), whether industry starts are rising or falling, and the top industry sponsors with the top-5 share. Refuses before you are charged if the condition matches nothing or the counts do not reconcile. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: by start year (years); segment: industry, Phase 3, sponsor (in the result). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For FDA clearances in a device category, use run_device_clearances; for recalls in a product category, use run_recall_watch.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | yes | A disease or condition, e.g. "obesity". |
| years | integer | – | Complete calendar years to cover, ending last year. Default 6. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
run_triangulation Is this real? Companies, regulators and money checked together ~327
Use when the user needs to know whether a trend is substantive or hype before acting on it. Returns, year by year, the share of 10-K filers mentioning it (SEC EDGAR), of federal final and proposed rules (Federal Register) and of federal contract obligations (USAspending), each line's direction, and whether the three agree. If any source fails its controls the whole run refuses. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: three shares by year (start-end). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For one source over a custom window, use run_filing_trend, run_regulatory_trend or run_spend_trend. A real sample of this run, free: https://cultmath.com/agent/samples/triangulation.json
| Name | Type | Req | Description |
|---|---|---|---|
| end | integer | – | Last year. At most 5 years per run. |
| phrase | string | yes | The phrase to measure, without quote marks. |
| start | integer | – | First year. Default: four years ago. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | false when the run is switched off; then nothing can be charged. |
| error | string | – | Why the inputs were refused, with the expected usage. Nothing is charged. |
| instructions | object | – | How to pay over MPP and x402, and how to ask for publication. |
| limits | – | – | What the run cannot tell you, stated before you pay. |
| next_step | string | – | What to tell the user before paying. |
| note | string | – | Why the run is unavailable, when it is. |
| payment_url | string | – | POST here to run and pay. Not a checkout page. |
| price_usd | number | – | Price over MPP (Stripe shared payment token). |
| recipe | string | – | The run, e.g. "filing-trend". |
| what_you_get | string | – | What the paid result will contain for these inputs. |
| x402_price_usd | number | – | Price over x402 (USDC on Base), when offered. |
No examples provided.
How do I install the CULT+MATH Decision Briefs MCP server?
CULT+MATH Decision Briefs is a hosted endpoint at https://cultmath.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · cultmath.com
claude mcp add --transport http com-cultmath-decision-briefs 'https://cultmath.com/mcp'
What is the CULT+MATH Decision Briefs MCP server?
CULT+MATH Decision Briefs is an MCP server listed in the public MCP registry as com.cultmath/decision-briefs. Odds and forecasts on the numbers executives plan against, plus free studies and Decision Briefs. This page covers its hosted endpoint (https://cultmath.com/mcp).
Is the CULT+MATH Decision Briefs MCP server safe to use?
CULT+MATH Decision Briefs scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CULT+MATH Decision Briefs MCP server expose?
CULT+MATH Decision Briefs exposes 71 tools: list_decision_briefs, get_decision_brief, search_cultmath, list_decisions, buy_decision_evidence, and 66 more. Their descriptions and schemas cost roughly 22,358 tokens of context every time the server is loaded.
Does the CULT+MATH Decision Briefs MCP server require authentication?
No. We connected to CULT+MATH Decision Briefs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CULT+MATH Decision Briefs MCP server still maintained?
CULT+MATH Decision Briefs is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the CULT+MATH Decision Briefs MCP server?
VerifyMCP ran 13 checks on CULT+MATH Decision Briefs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.