Compare what a page returns, not a story about what it might do.
A Jacobi audit starts with a public URL that an authenticated workspace is allowed to submit. The service asks for that URL through a configured set of request profiles within a short window, extracts usable prices, and shows the observations side by side.
The result is evidence for review. It can show a price spread, a MAP-floor undercut, a partial response set, or a blocked target. It does not turn one set of requests into a legal conclusion about a seller's intent or a site's pricing policy.
How an audit becomes evidence.
A configured set of request contexts — country, device, session, network tier.
The same URL is asked through every profile inside one short audit window.
Usable prices are pulled from each response with its source context kept.
Observations are placed side by side; coverage gaps stay visible.
A coverage-aware finding or MAP result, timestamped and reviewable.
What changes between observations.
A profile is a configured request context, not a real person. Depending on the audit mode, Jacobi can compare selected country, device headers, session and referrer state, network labels, and a controlled language pair. The exact context that is available is retained with the evidence.
Why this matters. Jacobi treats price variation, attributable variation, and a MAP-floor comparison as different outputs. A difference is recorded; it is not automatically assigned a cause.
How Jacobi stays restrained.
Coverage before confidence
Blocked, missing, and unusable responses stay visible. Thin coverage limits a comparison's confidence instead of being rounded into a clean answer.
MAP is a separate policy check
A MAP finding needs a configured floor, a recorded observed low price below that floor, and enough usable coverage for the rule to run.
No automatic legal conclusion
Findings describe what was observed at a point in time. They support your review; they are not an adjudication, guarantee, or legal advice.
What a reviewer can trace.
Watchlist
Product, seller, MAP floor, and target URL.
Scan job
Role, target limit, budget, rate, and status controls.
Evidence rows
Observed prices with source and extraction context.
Finding
Coverage-aware comparison or MAP policy result.
Export or share
Server-generated PDF or JSON, checksum, and controlled access.
Workspace exports are generated on the server and recorded. A public share can be redacted, time-limited, and revoked; redacted packets remove internal workspace identifiers, probe session identifiers, extraction metadata, and URL paths while keeping the useful evidence context.
A clear result is never more certain than its inputs.
- Third-party sites can rate limit, block, change, or require a login. Jacobi shows the resulting limitation rather than promising a complete read.
- Managed provider access can improve reach. Guarded direct requests can be a fallback, but they do not carry the same configured proxy context.
- Smart-24 names a configured profile matrix. Matching scout observations can be inferred to avoid needless identical external requests.
- A captured price is a timestamped observation, not continuous monitoring and not a guarantee of a future offer.
- Demo results are clearly cached samples. They are never represented as a live capture.
For access, data handling, and acceptable use, see the Privacy Policy and Terms of Service.