Washington Code

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"}

"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"}

List the AMENDMENTS proposed to a Washington State legislative bill — amendment name/drafting number, sponsor (member or committee), type (floor/committee), description, floor action (ADOPTED/FAILED/WITHDRAWN) and date, with links to the amendment text. Returns the most recent amendment first and a count by floor action. Reads directly from the Washington State Legislature's own bill-tracking service. Use for "what amendments have been offered to HB 1002", "was the striker amendment adopted on SB 5016". A bill with no amendments on file returns an empty list, not an error. Keyless. For the bill's overall status use wa_bill_status.

{"biennium":"2023-24","bill":"1002"}

Get the current status of a Washington State LEGISLATIVE BILL — its description, legal title, sponsor(s), introduced date, procedural history line and current status (e.g. "H Rules X", "Passed Legislature"), and companion bills in the other chamber. Reads directly from the Washington State Legislature's own bill-tracking service (not a third-party aggregator). Use for "what is the status of HB 1000", "who sponsored SB 5016", "is HB 1002 still active". Bill numbers reset each biennium (default: the current one) — pass biennium for a past session. Keyless. For an amendment history use wa_bill_amendments; for floor votes use wa_bill_votes; for everything introduced in a session use wa_session_bills.

{"bill":"HB 1002"}

{"biennium":"2025-26","bill":"1000"}

Get the recorded FLOOR ROLL-CALL VOTES on a Washington State legislative bill — chamber, motion ("3rd Reading & Final Passage"), date, and yea/nay/absent/excused counts with the voting legislators named in each category. Most recent vote first. Reads directly from the Washington State Legislature's own bill-tracking service. Use for "how did the House vote on HB 1002", "did SB 5016 pass the Senate". Voice votes and committee-only votes are not recorded here. Keyless.

{"bill":"HB 1002"}

Get the FULL TEXT of a section of the Revised Code of Washington (RCW) — Washington state STATUTES — by citation. "RCW 9A.32.030" is first degree murder. Returns the statutory text and its heading. Keyless. Use for "what does RCW 46.61.502 say", "text of RCW 49.60.180", or to check a Washington statute a case relies on. For agency RULES (Washington Administrative Code, citations like "WAC 296-800-110") use wa_wac_section instead.

{"section":"9A.32.030"}

{"section":"46.61.502"}

List Washington State legislative bills for a BIENNIUM filtered by procedural status: "introduced" (every bill filed, default), "passed_house", "passed_senate", "passed_legislature", "signed" (by the Governor), "vetoed", or "partial_veto" (the last three require agency: "House" or "Senate", the chamber of origin). Returns aggregate counts (by chamber, by type, active count) first, then a page of bare bill records (id, type, chamber, active) — call wa_bill_status on an id for its description. Reads directly from the Washington State Legislature's own bill-tracking service. Use for "how many bills passed the Legislature in 2025-26", "what did the Governor sign from the House in 2025-26". Keyless.

{"biennium":"2025-26","limit":5,"status":"passed_legislature"}

{"agency":"House","biennium":"2025-26","limit":3,"status":"signed"}

Get the text of a Washington Administrative Code (WAC) section AS IT STOOD at the end of a PAST YEAR, from the Legislature's annual WAC archive. Year-end snapshots with full text for 2019 onward (e.g. "WAC 296-800-110 in 2020"); 2004–2018 are PDF-only and the tool returns the chapter PDF link for 2016–2018 and the archive directory for earlier years rather than text. Returns the archived text, caption and the history line as printed that year, so you can diff it against wa_wac_section (current). Keyless. Use for "what did WAC 314-55-010 say in 2021", or to check which version of a rule applied on a date.

{"section":"296-800-110","year":2020}

{"section":"314-55-010","year":2021}

Browse the structure of the Washington Administrative Code (WAC): with no cite, lists every WAC TITLE with the agency it belongs to (Title 296 = Labor and Industries, 458 = Revenue, 388 = Social and Health Services, 173 = Ecology, 246 = Health); with a title ("296") lists its CHAPTERS with captions; with a chapter ("296-800") lists its SECTIONS with captions and subheadings. Use to find which chapter covers a topic before calling wa_wac_section, or to enumerate every rule in a chapter. Keyless.

{"cite":"296-800"}

{"cite":"296"}

List the Washington State Register (WSR) rule-making FILINGS that affected a Washington Administrative Code (WAC) section or chapter — the amendment history as agency actions: WSR number, filing type (Permanent Rule, Proposal Original Notice, Emergency Rule, Expedited Rule Making, Preproposal Statement of Inquiry…), date filed, and a link to the filing text. Newest first. Use for "when was WAC 296-800-110 last amended", "is there a pending proposal to change chapter 458-20 WAC", or to trace a rule's rule-making record. Keyless.

{"cite":"296-800-110"}

{"cite":"458-20"}

Search the FULL TEXT of the Washington Administrative Code (WAC) by topic or keyword — "workplace safety bulletin board", "security deposit", "septic system permit", "cannabis retailer". Calls the Washington State Legislature's own full-text search index of every WAC section (it matches rule TEXT, not just captions), returns matching citations with captions, highlighted snippets and the index-wide match count. Optionally restrict to a title or chapter with cite_prefix ("296" for L&I, "458-20" for Revenue excise-tax rules). Call wa_wac_section with a citation for the full text and history. Keyless.

{"limit":5,"query":"safety bulletin board"}

Get the CURRENT FULL TEXT of a section of the Washington Administrative Code (WAC) — Washington state agency RULES / regulations — by citation. "WAC 296-800-110" is L&I's safe-workplace summary; "458-20-178" is the Department of Revenue use-tax rule. Returns the rule text, its caption, the statutory-authority history (every WSR filing that amended it, with filed/effective dates) and the RCW sections the agency cited as authority. A repealed or nonexistent section is reported as found:false (the site redirects it). Keyless. Use for "what does WAC 296-800-110 say", "text of WAC 388-76-10000", or to check a Washington regulation an agency decision cites. For STATUTES (RCW) use wa_rcw_section; for past years use wa_wac_archived_section; to search by topic use wa_wac_search.

{"section":"296-800-110"}

{"section":"WAC 458-20-178"}