Platform

Verified Source

Included on Free

Provides the public-facing Verified Source proof pages and JSON verification API. Site visitors and automated tools can look up any seal ID to see its status, issuer domain, latest scan results, and sampled checked pages.

What it covers

Available during early release on the Free plan and every Pro account.

  • JSON seal verification API at /v1/seal/verify/{seal_id}
  • Public proof page with seal status and scan history
  • Seal lookup form for manual verification
  • Latest scan breakdown: clean, drift, mismatch, missing
  • Sampled checked pages with direct links
  • Baseline scan detection and display

Where Verified Source belongs

Verified Source sits in the Platform layer of LuperIQ and focuses on Public proof pages and JSON API for Verified Source seal verification. For a site owner, the practical value is not the module name by itself; it is whether JSON seal verification API at /v1/seal/verify/{seal_id}, Public proof page with seal status and scan history, and Seal lookup form for manual verification becomes easier to manage in the real customer or admin path.

For pricing and setup, the useful context is Free and Pro and the place the owner will likely manage it is Platform. Those details help the reader understand the module without turning the page into a technical inventory.

Setup checks for Verified Source

  • Verify that "JSON seal verification API at /v1/seal/verify/{seal_id}" is represented in the live setup before treating Verified Source as ready for customers or staff.
  • Verify that "Public proof page with seal status and scan history" is represented in the live setup before treating Verified Source as ready for customers or staff.
  • Verify that "Seal lookup form for manual verification" is represented in the live setup before treating Verified Source as ready for customers or staff.
  • Verify that "Latest scan breakdown: clean, drift, mismatch, missing" is represented in the live setup before treating Verified Source as ready for customers or staff.
  • Verify that "Sampled checked pages with direct links" is represented in the live setup before treating Verified Source as ready for customers or staff.
  • Open the Platform admin section during setup so the owner knows exactly where this module is managed after launch.

Dependencies and AI connections

Verified Source works best when SEO are already understood, because those surrounding tools shape where the data, settings, or customer actions will land.

Verified Source is documented as a practical module first. If the owner is evaluating AI help around the same area, the safer next step is to start in the Platform admin area and only add AI when there is a real task to run.

Related AI workflows

This module is documented first around the module itself. Public AI workflow pages are focused on the currently fixed-price credit jobs registered in Nexus.

Copyright © 2026 LuperIQ. All rights reserved. LuperIQ, Verified Source, ForgeVec, forge-embed, AI Cortex, and the LuperAI Dictionary are trademarks of LuperIQ.