For brandsRe-verify what’s already on the page

The Trust Score your reviews can finally defend.

Your product page already has a review widget. What it doesn’t have yet is the receipt the review is grounded in. Peerseal attaches a portable Trust Score — built from real human attestations, not vendor claims — to the posts that name your brand. The reader sees the score; you can point to the receipt.

Request verification accessSee the scoring model
Attestation kinds
4 additive weights
Independent of vendor
portable · contestable
Survival
travels with the author

Use cases — Pick the surface that fits

Two ways to attach a Trust Score to your brand today.

Peerseal runs as a portable trust layer — a partner integrates one of two surfaces depending on whether the consumer is reading or scoring on the back end. Both share the same scored bundle, so either surface — or both together — drops onto your stack with no schema work on your side.

01 · Marketplace widgetfull guide →

A portable trust badge next to the listing.

Drop a mount <div> next to the author byline and a single <script> renders the Trust Score in-place. The script reads the nearest data-peerseal-handle mount and pulls the bundle server-side. Live demo + the five-step integration guide live at /integrations/marketplace.

embed.html
<div data-peerseal-handle="demo0001"></div>
<script src="https://getpeerseal.com/embed/badge/demo0001.js"></script>
02 · Server-to-server lookupscore model →

Resolve a handle to a scored bundle, back-end first.

GET /api/lookup?handle=… with an x-api-key header returns the matching author’s 0–100 Trust Score plus the per-kind contribution breakdown, totals, and earned badges. Pair it with your own moderation or back-office review tooling; the response is safe to cache for ≤ 60 s because the score is a pure function of posts + attestations.

lookup.curl
curl -sS "https://getpeerseal.com/api/lookup" \
  -G \
  --data-urlencode "handle=demo0001" \
  -H "x-api-key: YOUR_KEY"

What you get

Three behaviours. One portable trust layer.

No new CMS, no widget migration, no locked-in ratings vendor. Peerseal attaches to the posts that already mention your brand and surfaces the receipts under them.

  1. 01

    Re-verify what’s already on the page

    the receipt below the review

    Plug Peerseal into the review widget you already ship. We attach a portable Trust Score drawn from real human attestations — a verified purchase receipt, an eyewitness event, an identity proof — to each post that names your product. Nothing changes in your CMS; the score lives next to the review like a notary seal.
  2. 02

    Surface the receipt next to the trust signal

    moot dispute, mooted

    A trust number is only as good as the receipts under it. Peerseal shows the underlying attestation alongside the score — the receipt hash, the witness handle, the ID-verification provider report — so any reader can audit it in one click. No more “Trust Score 87/100” with nothing to ground it.
  3. 03

    Marketplace trust whitelist

    opt-in verified brand registry

    Every brand that comes through this form gets a handle it can defend: when Peerseal’s attestations align, marketplaces running the protocol can opt the brand into a verified whitelist that surfaces at the listing level. The score travels with the brand across marketplaces, exchanges, and review platforms; the whitelist is the cross-platform acknowledgement.

Integration state

Read-side is shipping now. Write-side opens as attestations accrue.

The read path — scoring existing reviews/mentions — is live. The write path — helping your customers attach receipts, witnesses, and identity proofs to their posts about your brand — opens cohort-by-cohort. Joining early access puts you in the first write-side cohort.

public integration surface · Peerseal · no SDK lock-in · contract: /api/trust-score

FAQ

What brand teams ask before they sign.

Common questions from brand operators looking at the protocol for the first time. The brief version — the longer walk is the call after you submit the form below.

Inbound

Request verification access.

Already on Peerseal and want a specific review re-verified? Submit it from the in-app re-verification queue — rows triage in the order received. Otherwise tell us what you ship, where the reviews live, and the scale you’re working at. A 30-minute call follows — we walk through your surfaces, queue a scoped integration, and slot you into the next cohort.

  • Read-side can ship in days — no schema work on your side.
  • Write-side integration is scoped after a single working session.
  • No agreement to commit — the form is an introspective, not a purchase.

brand-access intake · routed to the operator inbox

Submissions write a row in the brand-request queue and email peerseal@polsia.app — a 30-minute reply follows during business hours.

Inbound · Re-verification

Request a re-verification.

Suspect a fake review, an impersonator, or a paid post naming your brand? Drop the URL and (optionally) the reason behind your hunch. The submission is a single-row, public, unauthenticated intake — no Peerseal account required — and lands in the re-verification queue at status: pending.

  • Read-side only — no integration required to flag a post.
  • Already signed in? You can also queue from /brands/dashboard.
  • One row per flagged post — single-shot intake, no commitment.

re-verification intake · status: pending → in_review → completed

Submissions write a row in the re-verification queue and notify peerseal@polsia.app. A reply is only possible if you include a contact email.