1. Hot-link the assets in <head>

<link rel="stylesheet" href="https://nevadapoliticalestablishment.com/css/npe-flags.css">
<script src="https://nevadapoliticalestablishment.com/js/npe-flags.js" defer></script>

Both files live at the NPE origin with permissive CORS + 1-day cache. They are versioned by content hash on the URL — bookmark the URL above for stable embedding.

2. Mark up the entities you want flagged

Add a single empty <span> next to each lobbyist / client / legislator name in your HTML. The slug must match what we use on /lobbyists/<slug>/, /clients/<slug>/, or /legislators/<slug>/.

<!-- Lobbyist row -->
<li>Serena Kasama (Henderson Chamber)
  <span data-npe-flag-lobbyist="serena-kasama-6908"></span>
</li>

<!-- Client row -->
<li>Southwest Gas
  <span data-npe-flag-client="southwest-gas"></span>
</li>

<!-- Legislator row -->
<li>Elaine Marzola
  <span data-npe-flag-legislator="elaine-marzola"></span>
</li>

3. The flag indexes (raw JSON)

If you need programmatic access, the same data powering the badges is published at:

All endpoints are CORS-open (Access-Control-Allow-Origin: *) and cached for one day. Each flag entry has detector, severity, evidence_tier, summary, and score fields.

Findings policy

Every flag links back to the source page on this site, where the underlying data + a "submit correction" form lives. The badge framing is "research lead" — never an adjudicated claim. Sister sites that embed the badges inherit that posture; recommend pairing embeds with a brief footer line such as "Auditor flags from nevadapoliticalestablishment.com — research leads, not adjudicated findings."

Slug format reference

NPE slugs are lowercased, ASCII-folded, hyphen-joined. Lobbyists have a numeric session-tag suffix (e.g. serena-kasama-6908); clients/legislators do not. If the slug your tracker uses doesn't match, you can either pre-translate or open a tip via the corrections form.