01 — CAPTURE
What was served, and when.
Each permitted fetch records the fingerprint of the bytes received and the capture time. No copy of the page is kept unless a documented legal basis allows it, and each record says what was not kept and why.
The record behind the commitment
Companies publish.
Pages change.
Keep the record.
Junctiq records what public company pages serve, and when: a fingerprint of the bytes and the capture time, timestamped and re-checked. Inspect the capture, follow its history, and see exactly what the evidence can and cannot establish.
Each capture states when it was fetched, whether a copy is held, and what may be shown.
Start with a defined question
The Starter Evidence Pack.
Up to eight public pages you choose, on a vendor you are deciding about. Each is captured when you order and again at day 30: its address, HTTP status, fingerprint and capture time, with a timestamp token over the pack. No copy of the page, no screenshot and no excerpt. A free two-URL sample can be requested first.
USD 750 per pack · invoiced
Requests are open. Captures for a new order cannot start yet.
Clearance for capturing pages a buyer names is pending. Nothing is invoiced before capture can begin.
The pages that matter
Terms & policiesPricingDocumentationChangelogsRoadmaps
01 / Start with evidence
A clearer path back
to the source.
A dated capture gives you a starting point. The record then separates what is held, what was checked, and what remains unanswered.
02 — RE-CHECK
A history of captures.
Scheduled checks add new captures. Different fingerprints show that the bytes differ; many pages differ on every load, so this alone does not show that the wording changed. An error answer, such as HTTP 404, is recorded as that answer at that time.
03 — INSPECT
The evidence and its limits.
Open the record to inspect its source address, timestamps, retention and history. Check an exported pack against a separately obtained receipt with the verifier.
Preservation records what was served. It does not establish that the publisher’s statement is true.
Read the method →02 / The full product
Evidence is the beginning.
The record goes further.
Junctiq’s product design connects source material to commitments, outcomes, research and institutional memory. Here is where it stands today.
The Vault
Inspect dated captures, retention status, fingerprints and the history of a page. Each unanswered question stays visible.
Explore the evidenceTHE CONNECTED PRODUCTDESIGNED · NOT AVAILABLE YET
Claims & actor histories
Follow a statement from its source to a commitment and an externally resolved outcome.
Research Workbench
Revisit what was knowable at a chosen time and keep research linked to evidence.
Direction & monitoring
Explore changes and contradictions with their supporting records and coverage limits.
Enterprise memory
Keep a team’s research, assumptions and decision history together across handovers.
MCP & read API
Give AI systems structured access to the same source records and provenance.
Availability is marked for each part.
03 / Put the record to work
When the source
matters to the decision.
Start with the company, page and question that matter to you. Junctiq keeps the distinction between a record and a conclusion visible.
Procurement & vendor risk
Was the page up, and did it stay the same?
Dated, fingerprinted records of a supplier’s pricing, policy and documentation pages during a decision, and whether their bytes differ thirty days later. Without a retained copy, the record does not show the wording.
Legal & compliance
What can the record establish?
Examine capture time, timestamps, retention and provenance. The record states its limits; it does not provide a legal opinion.
Research & journalism
When was it captured, and is it still served?
Trace a public page across captures. Publication time and capture time remain separate, and an error answer is recorded as an answer, not as proof the page is gone.
Clear by design
A few things
worth knowing.
What does the Starter Evidence Pack contain?
For each of up to eight URLs: the address requested and served, the HTTP status, a SHA-256 fingerprint, the capture time, the retention class, and an RFC 3161 timestamp over the pack; then the same again at day 30. It contains no copy of the page, no screenshot and no excerpt.
Can a record show what a page said, or what changed?
Not without a retained copy, and none is kept unless a documented legal basis allows it. A record shows that the page was served, when, and whether its bytes match a later capture.
Does a capture prove a company’s statement?
No. A capture records what was served at a particular time. It does not prove that a statement is true. Claims, attribution and externally resolved outcomes are separate parts of the product design.
What can I use today?
The public Vault and the evidence-pack verifier. The Starter Evidence Pack can be requested; captures for a buyer’s pages wait on legal clearance. The wider research, claim-history, monitoring, enterprise and machine workflows remain product designs.
Bring the question.
Start with the record.
Tell Junctiq which vendor and public pages matter to your decision.
Some earlier pages and endpoints were retired on 14 October 2026. Read the notice.