We read the public market
Operator info panels, public big-win streams, on-chain settlement, regulator filings, retailer feeds. Every signal is cite-able. Every source is named on this page.
12,847 named sources, 30+ AI models, 847,000 entities monitored across the registry. Every live counter, big-win row, RTP scan, flagged scam, and ranking position on this site sources back to a public-market signal we can name. Read this page like a regulator.
Trust commitments
These apply to every surface ShouldEye ships, regardless of vertical. Per-vertical sections below extend them with named upstream sources and polling cadences.
Operator info panels, public big-win streams, on-chain settlement, regulator filings, retailer feeds. Every signal is cite-able. Every source is named on this page.
ShouldEye does not proxy spins, deposits, trades, baskets, or any operator-side action. The verdict layer reads. It does not transact.
Spin history, basket, wallet, positions, and operator-side identity stay with the operator. Site telemetry is page-level, scoped to your ShouldEye account, never sold, never shared with operators.
Operator-side player handles stay as the operator publishes them. Wallet addresses truncate. Email and phone never display. PII never leaves the source.
The Advisory Board
Every ShouldEye verdict is the synthesis of multiple frontier models, in-house specialist fine-tunes, and a routing classifier that decides which engines see which query. No single engine ever gets the final word. The registry below names twelve of the engines in current production. The full Board, including standby engines and shadow models in evaluation, is published in the operating-agreement appendix.
OpenAI
Synthesis and complex reasoning. Lead author on contested verdicts.
Anthropic
Nuance, multi-step analysis, regulator-grade copy review.
Multi-modal. Reads PDFs of regulator filings and pricing screenshots.
DeepSeek
Cost-efficient synthesis for high-volume verticals.
Meta
Open-weights. Used for verdicts where a reproducible chain is needed.
xAI
Real-time signal sweep. Picks up public-feed reports before consensus.
ShouldEye
Scam-pattern detection, fine-tuned on 4.1M historical scam patterns.
ShouldEye
On-chain transaction analysis, honeypot detection, ownership tracing.
ShouldEye
RTP variance reconciliation. Monte Carlo session simulation at scale.
ShouldEye
90-day historical pricing reconciliation. Fake-markup detection.
ShouldEye
Cross-source dissent reconciliation. Calibrates the final verdict.
ShouldEye
Intent classifier. Decides which subset of engines a query fans out to.
Every query is classified by intent before any frontier engine sees it. Slot questions fan out to SE-Slots-Math plus three frontier models. Rug-check queries trigger the on-chain pull, SE-Rug-Forensics, and four frontier models in parallel. The router itself is a small in-house classifier optimized for sub-50ms decisioning so the fan-out is invisible to the user.
Engines vote. When they agree, the verdict ships immediately. When they disagree, SE-Trust-Graph-1.5 drills into the source data, names the dissenting engines, and surfaces the disagreement on the verdict artifact. The verdict ships with the dissent visible. No single engine ever gets the final word.
Every verdict is logged with the engines that voted, the sources they pulled, the polling timestamps, and the dissent summary at issue time. The log is append-only and powers the public /track-record ledger. If a verdict is later contradicted, the original log entry stays in place, with the contradiction appended.
The verdict pipeline
Every verdict travels the same five stages. The pipeline is the same whether the query is a slot RTP scan, a rug-check on a fresh contract, a deal-verification pull, or a scam check on a typed domain. The work each stage does is named, the latency budget is named, the artifacts at every stage are auditable.
Public-market signals are pulled into the system at the edge. Polling cadences are public, listed per vertical below, falsifiable against the source.
Raw signals are normalized, deduplicated, and stamped with the entity they refer to. Stamping is what makes a verdict cite-able later. Every observation carries the source URL, the timestamp, and the entity ID.
Each fact is reconciled against at least one independent source before it can drive a verdict. Single-source facts can inform a verdict but cannot be the only basis for it. Cross-check is what kills false positives.
The Advisory Board synthesizes. Frontier models read the reconciled facts and produce a draft. Specialist engines weigh in on domain math. SE-Trust-Graph reconciles dissent and ships the final call with a confidence band.
The verdict is logged append-only on the public ledger at /track-record. The full source list, engine vote breakdown, and dissent summary are preserved indefinitely so a future reader can reproduce the call. The ledger is the receipt.
Per-vertical lineage
Each register names the upstream sources, the polling cadence, the Board engines that actually issue the verdicts, the masking policy, and what we explicitly do not collect for that surface.
Companies & entity registry
Before any verdict is issued, the system identifies the entity. The companies registry is the canonical record: 847,000 companies, 12,000 brands, 4 million domains, reconciled against eight independent registers. Every other vertical on this page reads off this registry first.
Board engines on call
Surfaces this lineage informs
Upstream sources (7)
Polling cadence
WHOIS once per hour per tracked domain. Public registers refreshed daily. Social profile pages weekly. OFAC and OpenSanctions every six hours. New-entity discovery rolling, two-minute floor.
What we mask
Director and beneficial-owner names display only as the source publishes them. PII never leaves the source. Truncated handles ("J*** S***") stay truncated.
What we do not collect
Private corporate filings, internal email addresses, employee-list scrapes, or any data behind a paywall or login. The registry only ingests public-record material.
Methodology last reviewed May 2026
Browse the registryScam intel & rug detection
Scam, rug, and account-locked verdicts are reconciled from regulator paperwork, registration histories, on-chain forensics, and public consumer outcomes. No private complaint pipelines. No paid removals. Median time-to-flag against MetaMask blocklist: 11 days ahead.
Board engines on call
Surfaces this lineage informs
Upstream sources (7)
Polling cadence
WHOIS once per hour per tracked domain. Regulator filings once per day. Review corpora rolling 60 seconds. On-chain rug indices rolling 30 seconds. Wallet blocklists hourly. Policy archive once per day.
What we mask
Reporter usernames stay as the source masks them. Original review handles where Trustpilot or BBB has already redacted them. Wallet addresses display truncated. Email and phone never display.
What we do not collect
Your search queries outside your own ShouldEye account. Anonymous visitor pastes into the chat are session-local and never written to disk.
Methodology last reviewed May 2026
See a scam verdictTop rankings & trust scores
Rankings on /top-rankings are not opinion. Every position is a function of measured signals. The Top Rankings layer reads off the companies registry and the verdict ledger, then applies a weighted scoring model that is itself public. No paid placement. No affiliate-influenced positions.
Board engines on call
Surfaces this lineage informs
Upstream sources (6)
Polling cadence
Rankings recomputed daily at 04:00 UTC. Trust-score components refreshed hourly. Press-citation scan rolling 5 minutes. Ledger weight recompute live on each new verdict.
What we mask
Nothing on the scoring side. The scoring model is public. Every ranking row carries a "why this position" link that opens the score breakdown.
What we do not collect
Paid placement. ShouldEye has never accepted payment to influence a ranking position, will not, and the policy is in the operating agreement, not just the marketing.
Methodology last reviewed April 2026
See live rankingsDeal & price intelligence
Every deal verdict is anchored against the price-history archive. We do not take a vendor's word for "60% off". We compare today's price against three years of every observed price for that SKU. Median fake-markup detection: 8 minutes from claim posting to flag.
Board engines on call
Surfaces this lineage informs
Upstream sources (6)
Polling cadence
Tracked SKUs every 60 to 120 seconds. Full catalogue refresh once per day. MSRP sheets once per week and on every detected manufacturer announcement. Coupon codes verified on first use and every six hours thereafter.
What we mask
Nothing on the deal side. Retailer name, observed price, and observation timestamp are the disclosure.
What we do not collect
Your basket, wishlist, or purchase history outside your ShouldEye account. Affiliate clicks route from your browser direct to the retailer. We never intercept your checkout.
Methodology last reviewed May 2026
See live dealsPrediction markets
Predict verdicts read off public, on-chain, regulated, or self-published market data. We do not custody a position or settle a trade. ShouldEye is a read layer over the markets that already exist. Settlement data is on-chain where possible so any reader can independently verify.
Board engines on call
Surfaces this lineage informs
Upstream sources (6)
Polling cadence
Market prices every 15 seconds. News sentiment every 5 minutes. On-chain settlement live, block-by-block. Regulator filings polled once per day.
What we mask
Nothing. Markets and price tape are public.
What we do not collect
Your positions on any third-party prediction market. We do not custody, route, or settle prediction-market trades.
Methodology last reviewed May 2026
See live marketsSlots & gaming
Big-win rows, live RTPs, and bonus-EV verdicts read off operator-published streams and slot info-panels. Player handles stay as the operator publishes them. We never sit between you and the casino. The verdict layer reads. It does not transact.
Board engines on call
Surfaces this lineage informs
Upstream sources (6)
Polling cadence
Operator big-win streams every 30 seconds. RTP info-panel rolling scan, full coverage every 24 hours per operator. Provider top-wins every 5 minutes. Bonus terms polled hourly.
What we mask
Operator-side player handles stay as the operator publishes them. The "D**4f" you see is the operator's mask, not ours. We do not unmask, deanonymise, or correlate handles across operators.
What we do not collect
Your gambling session. Your deposits, withdrawals, spin history, balance, or operator account identity. We never sit between you and the casino.
Methodology last reviewed May 2026
See live slotsSide-by-side product analysis
Every comparison verdict reconciles three independent registers: the manufacturer's spec sheet, certified test reports, and the owner-review corpus. When the three disagree, the verdict surfaces the disagreement. We do not pretend consensus exists when it does not.
Board engines on call
Surfaces this lineage informs
Upstream sources (6)
Polling cadence
Spec sheets once per week per SKU and on every detected manufacturer announcement. Reviews rolling daily. Availability rolling hourly. Recall and warranty registers daily.
What we mask
Nothing on the spec side. Manufacturer name, SKU, observed availability, and observed review count are the disclosure.
What we do not collect
Your past purchases or browsing history outside your ShouldEye account.
Methodology last reviewed April 2026
Compare anythingThe trust graph
The trust graph sits above every vertical above. Every claim from every Expert Engine, on every verdict, is reconciled against the public-market source it rests on before the verdict ships. When sources disagree, dissent is named. When sources are stale, the verdict is flagged.
Board engines on call
Surfaces this lineage informs
Upstream sources (3)
Polling cadence
Live. The trust graph reconciles on every verdict request and stamps the verdict with the source list, polling timestamps, agreement rate, and dissent summary at the moment of issue. The outcome reconciler runs continuously.
What we mask
Nothing in the audit log itself. The audit log is the receipt.
What we do not collect
Any data not already collected by the per-vertical layers above. The trust graph is a reconciliation surface, not a separate ingestion path.
Methodology last reviewed May 2026
Read the ledgerInfrastructure & compliance
Where the system runs. What it complies with. How much it processes. The audit cadence. Read this row before you ask us to fill in your vendor questionnaire.
Open it in the Advisory Board chat and we will show you the named source list, the polling timestamp, the Board engines that voted, and the agreement rate behind that exact verdict.