CertScore.ai for Muse Agents

The four-tool workflow

1. 1→

   Start the scan

   certscore_scan_site

   Call certscore_scan_site with the site URL. Declare a purpose when one fits: prelaunch_review, vendor_review, tracking_check, consent_gpc_check, policy_review, recheck.

2. 2→

   Wait for completion

   certscore_get_scan_status

   Poll certscore_get_scan_status until the scan completes. Scans are asynchronous; allow a few minutes.

3. 3→

   Get the report

   certscore_get_scan_bundle

   Call certscore_get_scan_bundle for the scored results: overall score, findings, coverage, and the report link.

4. 4✓

   Check the evidence

   certscore_get_report_evidence_page

   Call certscore_get_report_evidence_page when a finding needs its underlying evidence.

By default, the service reuses a recent result for the same site. Request a fresh scan only when the user asks for one or wants a recheck after a change.

Share the results

Score and date

Label EU (GDPR/ePrivacy) and California (CCPA/CPRA) scores clearly, with their coverage and scan date.

Review focus

Open the EU or California report view using the same scan. Changing the view does not run another visit.

Scan location

Ask for Ireland, Germany, or California when you need a new visit from that location.

Findings and evidence

Show the findings that matter most, with the evidence for each.

Coverage and report link

State any reported coverage limits, such as completed_limited. Always include the report link.

Scan ID

Keep the scan ID as the baseline for a later recheck.

Never present a finding as a legal violation or describe a site as compliant or non-compliant. These are observations for human review.

If a call returns rate_limited, tell the user and stop. Do not retry in a loop.

Recheck after changes

Keep the first scan as a baseline. After you change the site, ask Muse for a fresh scan and compare the results.

1. Keep the scan ID from the first scan.
2. After the site changes, run a fresh scan with purpose recheck from the same location.
3. Compare the same review focus and equivalent coverage against the baseline scan ID.
4. Report what changed. A finding missing from a later scan is a change to note, not proof of a fix; say so.

When to scan again

Before launch

Scan a public staging or production URL before a launch or redesign.

After consent changes

Rescan when the banner, CMP, or tag setup changes.

New vendors

Review a vendor or partner's site before signing.

Periodic checks

With the user's approval, repeat a scan and compare it with the previous result.

Agency portfolios

Run the same review across client sites, with a separate report for each.

Only run scans the user has asked for or approved as a recurring pattern. Never scan sites on your own initiative.