Consent monitoring across every client site you run

Agencies add the pixels, the chat widgets and the tag manager containers, and they are usually the first call when something fires that should not. RegSentry gives you one account that watches each client site, checks each client deploy and keeps dated evidence you can hand over.

Multi-site monitoring

Team covers up to 10 sites and Protect up to 25. Each site carries its own consent policy (strict, standard or permissive), monitoring switch and optional alert email, so the right client contact or account manager hears about that site only.

Or ask an agent with the MCP server connected: "List my RegSentry sites with open findings and summarize what changed this week." It uses list_sites, get_findings and list_recent_activity.

Evidence exports per client

Every scan is dated and kept for the plan's retention period. Pull a per-site report as JSON, CSV or PDF with the capture date, sampled pages, first-request timings, finding records and the limitations of the method.

curl -s "https://regsentry.com/api/v1/sites/$SITE_ID/report?format=csv" -H "Authorization: Bearer $REGSENTRY_API_KEY"

Protect adds an evidence vault and attestation reports. Reports describe technical observations; they are not a legal opinion or a certification, and should be presented to clients that way.

CI checks per client repo

Call the deploy-check API from your CI with a key for each client repository. One key per repo (up to 10 active keys per account) keeps revocation simple when an engagement ends. Inspect the returned exitCode and choose how your pipeline handles inconclusive results.

curl -s https://regsentry.com/api/v1/checks \
  -H "Authorization: Bearer $REGSENTRY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://preview-123.vercel.app","policy":"standard","authorizationAcknowledged":true}'

# => { "check": { "status": "complete", "policy": { "result": "fail", "reasons": [...] }, ... }, "exitCode": 1 }

Checks and scans started from CI count toward the plan's API runs (100 per month on Team, unlimited on Protect).

Webhooks into your tools

Register an https endpoint and subscribe to finding.new, consent.regression, check.failed or any other event. Every payload includes the site's domain, so one receiver can route to the right client channel, ticket queue or status board. Deliveries are signed with HMAC-SHA256 and retried with backoff.

curl -s https://regsentry.com/api/v1/webhooks \
  -H "Authorization: Bearer $REGSENTRY_API_KEY" -H "Content-Type: application/json" \
  -d '{"url":"https://ops.youragency.example/hooks/regsentry","events":["finding.new","consent.regression","check.failed"]}'

Signature verification and the full event list are in the API reference.

Before you add a client site

Related guides