New Odyssey

Regulatory Agent

Stay ahead of every regulatory change

Expected 2027
pegasus · Regulatory Agent
governed by CIP

Regulatory updates — this week

  1. Connected to Federal Register, SharePoint, Jira
  2. 217 updates monitored
  3. 206 not relevant, no action needed
  4. policyJurisdiction-aware monitoring.
  5. for reviewCFPB · Final rule on overdraft fees: Two products are affected; fee schedules must change.
  6. for reviewTexas · TDPSA amendments: Privacy notice and consent flows need review.

done11 of 217 sent to a person to decide

Illustrative sample

The Pegasus impact

The Pegasus Regulatory Agent is being built to help compliance teams stay ahead of regulatory change across jurisdictions by detecting changes, analyzing their impact and routing actions to the teams that own them.

Keeping up with regulatory changes across jurisdictions requires constant manual monitoring and impact assessment.

Expected availability
2027
Platforms on the same integration layer as the live agents
200+
Capabilities in development
3

Capabilities

AI does the volume. Humans keep the judgment.

In development. These are the capabilities the agent is being built to deliver.

01

Continuous change detection

Monitor the sources you care about, and match every update against your jurisdictions, products and obligations.

Normal rangeRelevant changeUpdates publishedTime

02

Explainable impact analysis

Score each change for relevance and impact, with the reasoning quoted to its source.

Data privacy86Consumer cre…34Reporting62Licensing92Marketing48Threshold

03

Prioritized action routing

Confirm the assessment and assign the action to the team that owns it.

IncomingNo actionPolicy updateEscalate

Systems connected

Connected to the systems you already run.

Custom integrations for regulatory feeds and internal compliance systems.

  • Federal Register
  • SharePoint
  • Jira
  • Microsoft 365
  • Slack

Governance built in

Human-in-the-loop control, with every action audited.

  • Jurisdiction-aware monitoring
  • Impact severity scoring
  • CIP audit trail

FAQ

Regulatory Agent FAQs

It is in development, expected 2027. Pilot-list members are contacted first, and the first pilots run on your own example before any commitment.

Federal Register, SharePoint, Jira, Microsoft 365, Slack and other systems through the same integration layer as the live Pegasus agents. Sources are monitored where they publish. Policies and actions stay in the systems you already use.

Your compliance team. Pegasus assesses relevance and proposes an impact; a person confirms every assessment before an action is assigned.

First access when pilots open, a walkthrough of the workflow on one of your own examples, and a say in which parts of the process it handles first. No commitment.

Additional resources

The workflow it is being built to run

A worked sample of the Regulatory Agent, and the pilot list for first access when pilots open.

200+ platforms through Merge

HRIS, ATS, accounting, CRM, ticketing and file storage, connected during onboarding with no custom integration build.

CIP, the control plane under every agent

Open-source governance: every action audited, every deployment versioned, every decision explainable. MIT-licensed.

Next step

Join the Regulatory Agent pilot list

No commitment. We email when pilots open, with a walkthrough on your own example.