Data
LuperIQ Scout Ingest
Included on Free
Receives consented competitor-research captures from distributed LuperIQ Scout browser extensions. Panel participants self-enroll for a revocable per-install token; captures are organized by search type into a capped side-store, and an operator-only harvest summary reports participant and capture counts. Installs are event-sourced on the journal; captures live OFF the WAL.
What it covers
Available during early release on the Free plan and every Pro account.
- Self-serve panel enrollment with consent disclosure + abuse guards
- Per-install revocable bearer tokens (event-sourced installs)
- Capped, deduped capture side-store organized by search type
- Operator-only harvest summary (capability-gated, 404-invisible)
- Optional env-sourced redacted forwarder (off by default)
Where LuperIQ Scout Ingest belongs
LuperIQ Scout Ingest sits in the Data layer of LuperIQ and focuses on Collector for consented competitor-research captures from distributed LuperIQ Scout browser extensions. For a site owner, the practical value is not the module name by itself; it is whether Self-serve panel enrollment with consent disclosure + abuse guards, Per-install revocable bearer tokens (event-sourced installs), and Capped, deduped capture side-store organized by search type 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 Data. Those details help the reader understand the module without turning the page into a technical inventory.
Setup checks for LuperIQ Scout Ingest
- Verify that "Self-serve panel enrollment with consent disclosure + abuse guards" is represented in the live setup before treating LuperIQ Scout Ingest as ready for customers or staff.
- Verify that "Per-install revocable bearer tokens (event-sourced installs)" is represented in the live setup before treating LuperIQ Scout Ingest as ready for customers or staff.
- Verify that "Capped, deduped capture side-store organized by search type" is represented in the live setup before treating LuperIQ Scout Ingest as ready for customers or staff.
- Verify that "Operator-only harvest summary (capability-gated, 404-invisible)" is represented in the live setup before treating LuperIQ Scout Ingest as ready for customers or staff.
- Verify that "Optional env-sourced redacted forwarder (off by default)" is represented in the live setup before treating LuperIQ Scout Ingest as ready for customers or staff.
- Open the Data admin section during setup so the owner knows exactly where this module is managed after launch.
Dependencies and AI connections
LuperIQ Scout Ingest can be reviewed directly from the Data admin area. If the owner expects it to affect another part of the site, that connection should be tested during setup instead of assumed.
LuperIQ Scout Ingest 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 Data 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.