Usaspending

What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass `topic` (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).

{"topic":"finance"}

Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.

How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair: windows both venues settled, divergent count, the rate with its 95% Wilson interval (withheld under 30 paired windows), which direction they split, and what was excluded (unsettled on a side, 50-50). A HEADLINE RATE IS A CONCENTRATION QUESTION, so every pair also carries `concentration` (UTC days and hours the divergent windows fell in, the busiest day, the top-3-day share, and a plain reading) and `by_how_decided` (the rate by how far the reference venue's mid was from 50 at its last priced minute: the rate is a fraction of a percent for windows that were decided by the end and tens of percent for the ones that were not). `divergent_path` gives the mean Up mid by minute on both venues over the divergent windows only, split by who said Up, so the "early spike that fades" story can be checked rather than assumed. Measured on the archive 2026-10-27 over 30 days of btc: polymarket.com vs Kalshi diverged on 48 of 2,847 windows (1.69%, interval 1.27-2.23), spread over 27 of 31 UTC days, 0.19% of windows decided by the end and 17-29% of the ones still undecided; Polymarket US vs Kalshi on 0 of 1,838. asset btc | eth | sol | xrp | bnb (bnb has no pair: Kalshi only); days 1-90 (default 30), capped by what the archive holds (it starts 2026-09-22 for polymarket.com and Kalshi, 2026-10-07 for Polymarket US). Read-only; cheap enough to call, it reads several thousand archive rows.

{"asset":"btc","days":30}

{"asset":"eth","days":14}

The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as ISO such as 2026-10-27T14:15:00Z, on a 15-minute boundary). Per venue: question, Up bid / ask / mid / last, spread_pp, quote_state, volume WITH ITS UNIT, open interest, liquidity, settlement source, comparison basis, when it settles. THE VENUES ARE NOT ONE CONTRACT. Kalshi and Polymarket US settle on CF Benchmarks' BRTI (60-second average at the end against the same at the start): the same bet, so a gap between them is a real disagreement. polymarket.com settles on a Chainlink 60-second TWAP, end against start: same comparison shape, different feed, so a gap against either is partly the contract. `pairs[]` gives equivalent ("true"|"false"|"unclear"|"not_comparable") from resolution_diff for every pair, material_differences, mid_diff_pp (a minus b, in percentage points) and read_as in words. Measured over 30 days of settled windows the Chainlink and BRTI feeds settle a window differently about 1.2-1.8% of the time, almost entirely windows that ended near the threshold (see updown_divergence_rate). `net_spread` is computed only for the pair that is equivalent: the gap in mid terms and at top of book (buy Up where cheaper at the ask, Down where Up is dearer at 1 minus the bid) after BOTH venues' taker fees, each fee carrying its verified-as-of date. Top-of-book size is shown where the venue publishes it (Polymarket US); the Kalshi figure is not in its market payload, so read its order book before sizing. A venue with no market for the window is {status:"not_listed", reason}; one that could not be read is {status:"unavailable", refusal} -- never an empty object, and never the same thing. A one-sided book (typical Polymarket US just before a window is decided) has quote_state "bid_only", a null…

{"asset":"btc","horizon":"15m","window":"current"}

{"asset":"eth","window":"previous"}

{"asset":"btc","window":"2026-10-27T14:30:00Z"}

Search US federal PROCUREMENT CONTRACTS / government contract awards for goods and services. Use recipient_name for "contracts won by Lockheed Martin"; keywords searches award descriptions/topics, not contractor identity. Dates are optional and default to the last 12 months for "recent" questions. Dates select awards ACTIVE in the window (not signed in it) and award_amount is the award's LIFETIME obligation, so do not sum it as spending for the period. Results are paged: 100 per page max — pass `page` (and read `page_metadata.has_next`) to reach the rest. Returns recipient, award amount, outlays (with an outlays_reported flag, since DoD awards usually report none), dates, and contract type. Umbrella contracts (IDVs — CRS-2, NASA Launch Services II, CCtCap) are a SEPARATE result set in `idvs`, not in `awards`: read both, and `idv_status` says which you got. IDV and child-order amounts are disjoint, so `totals.combined_amount` is the correct total.

{"limit":10,"recipient_name":"Lockheed Martin"}

{"end_date":"2024-12-31","keywords":["cybersecurity"],"start_date":"2024-01-01"}

{"agency":"Department of Defense","end_date":"2024-12-31","keywords":["cloud","infrastructure"],"limit":25,"naics":"541512","start_date":"2023-01-01"}

{"agency":"Department of Defense","end_date":"2024-12-31","limit":10,"start_date":"2024-10-01"}

Federal contracts EXPIRING soon -- the recompete calendar. "Which VA IT contracts over $10M expire in the next 12 months?" / "what is up for recompete at DHS next year" / "find follow-on opportunities in NAICS 5415" / "whose contract is ending". Returns the incumbent holding each award, its period of performance, obligated dollars, agency, NAICS/PSC, and a usaspending.gov link. Filter by agency, sub-agency, NAICS or PSC prefix, incumbent name, and minimum obligated dollars. Covers awarded CONTRACTS already held by a vendor; for open solicitations still accepting bids use samgov/govcon tools.

{"agency":"Department of Veterans Affairs","min_amount":10000000,"months_ahead":12,"naics":"5415"}

{"agency":"Defense","limit":25,"months_ahead":12}

{"months_ahead":18,"recipient":"Leidos"}

Federal contract portfolio for one contractor -- "what does Leidos hold and when does it expire", "which of Booz Allen's contracts come up for recompete", incumbent research before a bid. Returns active award count, total obligated, ceiling, expirations at 6/12/18 months, top agencies and NAICS, and the next awards to expire with dates.

{"limit":5,"recipient":"Booz Allen"}

{"recipient":"Leidos"}

Answer "what federal contracts did [company] win recently?" and get a contractor's federal contract awards. Dates are optional and default to the last 12 months; the response always states the window used.

{"limit":10,"recipient_name":"Lockheed Martin"}

{"end_date":"2024-12-31","limit":100,"recipient_name":"Amazon Web Services","start_date":"2022-01-01"}

Break down US federal contract spending by agency for a given fiscal year (default: current year) and optional quarter (1-4). Returns agency names, abbreviations, and dollar amounts from USAspending.gov.

{"fiscal_year":"2024"}

{"fiscal_year":"2023","quarter":2}

Analyze federal spending by industry, product/service, recipient, or agency. Returns spending totals per category. Use for market research and identifying government contracting opportunities.

{"category":"naics","end_date":"2024-12-31","start_date":"2024-01-01"}

{"agency":"General Services Administration","category":"recipient","end_date":"2024-12-31","keywords":["software"],"limit":50,"start_date":"2023-01-01"}

"How has [agency] contract spending trended over the last N fiscal years?" / "is [agency] spending on X growing?" / "federal spending history for [topic]" — US FEDERAL contract/award spending over time from USAspending.gov, grouped by fiscal year, quarter, or month. Filter by keywords or by federal agency (DHS/Homeland Security, DOD/Defense, HHS, VA, DOE, NASA, State, Treasury). Returns the historical dollar amount per period for trend and budget-forecasting questions. Federal only — for state & county award data use gov_contracts_search.

{"end_date":"2024-12-31","group":"fiscal_year","keywords":["artificial intelligence"],"start_date":"2020-01-01"}

{"agency":"Department of Energy","end_date":"2024-12-31","group":"quarter","keywords":["renewable energy"],"start_date":"2023-01-01"}

"Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is factually correct. Company-financial claims (revenue, net income, cash for public US companies) verify via the structured SEC EDGAR + XBRL fast path with exact percent-delta math; ANY OTHER factual claim (macro statistics, rates, prices, drug data, records) automatically falls through to the grounded pipeline — routed to the right live source, answered with verbatim evidence, then judged. Returns a verdict (confirmed / approximately_correct / refuted / inconclusive / unsupported / could_not_verify), the grounded or structured actual value with pipeworx:// citation, and reasoning. IMPORTANT for callers: could_not_verify means the check did not happen (our LLM or source failed) and carries verification_error{stage,detail} — it is NOT evidence for or against the claim, and must not be shown as one. unsupported means we looked and cover no source for it. Replaces 4–6 sequential calls (NL parsing → entity resolution → data lookup → comparison).

{"claim":"Apple's fiscal 2023 revenue was $383 billion"}