Skip to content
Matterwireby Crawlify

Every regulatory change, traced to its source and verified at 99.5% accuracy.

Matterwire monitors US federal, all 50 states, France, the EU, and the UK. Every record carries its source URL, timestamp, and verifier ID, and joins directly to the watchlists and pipelines you already run.

The Matterwire signals dashboard: a verified amendment to 40 CFR Part 60 opened to its traced record, showing jurisdiction, source URL, capture timestamp, verifier ID VER-0148 and a 0.994 confidence score, joined to a watchlist and a pipeline. Feeds from federal agencies, all 50 states, EU regulations, UK legislation and regulatory portals converge on it.
A real record shape. Every field is delivered, on every plan.
  • 99.5%Verified field accuracy
  • 5Jurisdictions
  • 15+Years in production engineering, Xillentech
The wedge

Four things most regulatory trackers do not give you.

An analyst at a wall display listing five verified source addresses with the exact time each was captured, beside a highlighted Federal Register page and a printed evidence summary

Source traceability on every record.

Each change carries its source URL, the timestamp it was captured, and the ID of the verifier who checked it. Nothing is a black box.

See how
A verifier comparing a Federal Register page against its extracted fields on screen, every field ticked except one flagged for review, above a desk of marked-up printouts

99.5% field-level accuracy.

Verified at the field level, not the document level. Contractual on Enterprise plans.

See how
Three colleagues at a diagram where a register, a docket, a watchlist and a warehouse converge into one verified record

Cross-pipeline correlation.

Join regulatory changes against your watchlists and against the other data pipelines you already run. One composite signal, not a stack of disconnected alerts.

See how
Two people reviewing a pricing page that publishes all three tiers and their figures on the page

Published pricing.

Free, Professional, and Enterprise tiers with figures on the page. No "contact sales" wall to find out if you can afford it.

See how
How it works

Four verbs. One engine.

The same pipeline that runs the Crawlify parent engine, tuned to regulatory sources.

  • Two analysts scoping which sources to watch and how often, against a whiteboard of data sources and delivery schedule

    Monitor

    The engine watches regulatory sources across US federal, 50 states, France, the EU, and the UK. Registers, dockets, official journals, agency portals, and filings, on the cadence you set.

    See how
  • An extraction engine on screen turning source documents into classified fields

    Detect

    AI classifies every change: new rule, amendment, comment period, effective date. Each classification carries a confidence score. Low-confidence records route to human review.

    See how
  • A verifier checking extracted records against their sources, with each row marked verified or flagged

    Correlate

    Detected changes join your watchlists and your other pipelines. Related changes surface as one event instead of scattered alerts.

    See how
  • Delivery formats on screen: API, JSON, CSV and document exports

    Act

    Changes become actions in your systems: alerts, CRM writes, webhook triggers, workflow starts. Source-traceable end to end.

    See how

Stage 1 of 4: Monitor

Verified records

Three fields turn an alert into evidence.

An auditor asks the same three questions every time. Each one is a field on the record rather than a story you assemble afterwards.

Where it came fromsource_url
The address the record was read from, stored in full and resolvable. A checksum of the response is kept alongside it.
When you knewcaptured_at
ISO 8601 with a timezone offset, written at fetch time rather than at publish time.
Who checked itverifier_id
The person who compared the extracted fields against the source text, on every record that went to review.
The log behind one record
The audit trail for record rec_01J8Q4M2X, five events: captured from federalregister.gov with a stored checksum, classified as an amendment at 0.912 confidence, verified against the source text by VER-0148 which raised confidence to 0.994, correlated to the Clean Air watchlist and the EHS-Compliance pipeline, then delivered by webhook and accepted.

Written as the pipeline runs. There is no separate evidence-gathering step to schedule or forget.

Most tools tell you a rule changed. Matterwire shows you the source, the verifier, and the join to your systems.

Coverage

Five jurisdictions. One traced feed.

US federal. All 50 states. France. The European Union. The United Kingdom. Every jurisdiction delivered through the same verified, source-traceable record structure.

  • US-FEDUnited States, federalCongress and the federal agencies, from introduced bill to final rule.
  • US-STUnited States, all 50 statesEvery state legislature and state regulatory body, on one record schema.
  • FRFranceParliamentary texts and the regulators, in French, delivered in English.
  • EUEuropean UnionThe Commission, Parliament and Council, plus the European supervisory authorities.
  • GBUnited KingdomWestminster and the UK regulators, including the devolved bodies.
See every source we monitor
Pick a jurisdiction

Traced record

Proposed amendment to 40 CFR Part 60

Verified
Jurisdiction
US Federal / EPA
Change type
Amendment, comment period open
Source URLThe address this record was read from. Stored in full, with a checksum of the response, so the page cannot be swapped underneath the record.
CapturedWhen the source was fetched, in ISO 8601 with a timezone offset. Written at fetch time, not at publish time.
Verifier IDThe person who checked these fields against the source text. Present on every record that went to human review.
VER-0148
ConfidenceHow certain the classifier was, at the field level. Records below the release threshold route to a human verifier first.
0.994
Effective

Joined signals

  • Watchlist 'Clean Air'
  • Pipeline 'EHS-Compliance'
  • 3 related state bills
Correlation

One change. One signal.

A verified change joins your watchlists and the other pipelines you run. Related items resolve into a single composite event instead of arriving as separate alerts.

How one regulatory change becomes one composite signalA verified regulatory change joins a watchlist match and a pipeline match. The three resolve into a single composite signal delivered to your systems.Verified changeEPA, 40 CFR Part 60VER-0148 · 0.994Watchlist matchClean AirPipeline matchEHS-Compliance1 signalDelivered
Integrations

Delivered into the stack you already run.

Six delivery surfaces. Each one carries the full record, including the source URL, the capture timestamp and the verifier ID.

  • Slack logoSlack
  • Salesforce logoSalesforce
  • HubSpot logoHubSpot
  • Snowflake logoSnowflake
  • Webhooks logoWebhooks
  • REST API logoREST API
Pricing

Published pricing, on the page.

Quorum, FiscalNote and Bloomberg Government all put price behind a demo request. Ours is here.

Free

$0

No card required

Track a limited set of sources with full source traceability. Every record carries the same provenance fields as a paid plan.

Professional

Most teams

$10K to $30K

Per year, billed annually

Multi-jurisdiction monitoring, correlation against your watchlists, and the standard integrations.

Enterprise

$50K to $100K+

Per year, billed annually

Full jurisdiction coverage, the 99.5% field-level accuracy SLA, cross-pipeline correlation, and priority support.

By the numbers
99.5%Verified field-level accuracy
5JurisdictionsUS federal, 50 states, France, EU, UK
50US states covered
15+Years of production engineeringXillentech, the parent studio
315+Projects deliveredXillentech, the parent studio
Questions

Answers before the call.

See a traced record from your own jurisdictions.

Book a demo and we will show you real changes from the sources you care about, each one traced to its origin and verifier. Or start free today.

No obligation. We will use your own jurisdictions in the call.