Proof pages

Open the read-only page behind an agent's answer, check the claim, and share the link.

On this page

Your agent does the work. A proof page lets you check it.

A proof page is one page in the Console that shows exactly what an agent's answer is about: one person, one issue, one trace, and so on. The agent gives you a link. You open the link, look at the evidence, and decide whether you agree. You can send the same link to a teammate.

A proof page is not a dashboard to browse. It has no menu, no list to go back to and no button that changes a saved object or a setting.

The nine kinds

Every proof page shows one thing. The page type is in the address.

Kind	Address	It shows	Tools whose results carry it
Finding	`/view/finding/<id>`	Immutable conclusion, author-stated measurements, capture snapshots and withdrawal state	`get_finding`, `create_finding`, `revise_finding`, `withdraw_finding`
Person	`/view/person/<id>`	One person's story: events, errors, traces, logs, replays and agent runs in time order	`search_persons`, `resolve_person`, `get_person_profile`, `get_person_timeline`
Issue	`/view/issue/<group-id>`	One error issue: its occurrences, stack trace, affected people and history	`list_issues`, `search_issues`, `get_issue`
Trace	`/view/trace/<trace-id>`	One distributed trace with its spans	`search_traces`, `get_trace`
Agent run	`/view/agent-run/<run-id>`	One run of one of your own AI agents: steps, tools, tokens and cost	`list_agent_runs`, `get_agent_run`, `get_agent_run_graph`
Incident	`/view/incident/<id>`	One incident's case file: timeline, evidence and linked signals	`list_incidents`, `get_incident`, `create_incident`
Dashboard	`/view/dashboard/<dashboard-id>`	One of your saved dashboards, as your agent built it	`get_dashboard`, and the writes that create or change a dashboard
Replay	`/view/replay/<session-id>`	One recorded session, played back	`list_recordings`, `get_session_signals`, `find_trace_recording`
Result	`/view/result`	One analytics result, in one of four modes	The analytics tools. See The result viewer

A tool result carries a link when a proof page exists for the thing it is about. A list of people, issues or traces carries one link on each row. A result that is about many things at once, such as a count or a time series, carries none. Read the tool's own description in the MCP tool reference. Do not assume that every result has a link.

The link is in the result. A row or an object carries it in a url field. Many results also list it in links, as an entry with rel set to detail, a title that says which page it opens, and the address in href. The title lets the agent say what you are about to see.

A proof page only reads

Running a read query to show a result is a read, not a product write. A dashboard proof page may execute the queries of its widgets and rerun them. A retained result is a cache with a retention period, not product configuration.

A viewing page may never change something you own: a dashboard, a widget, a saved query, an alert, a finding or a setting. This is true of every page above:

It has no Resolve, Snooze, Delete, Save or Edit button.
Its requests read evidence or execute read queries. They never change a saved object or a setting.
It does not change which project you have selected in the Console.

When a page opens, the Console sends one short report that it opened. Anectico keeps it, so the workspace can see which proof links its people open. See What is recorded when you open a proof page.

To change something, ask your agent. For example, to resolve an issue, ask the agent. It calls the write tool, shows you a preview, and applies the change only after you confirm. See How agent access is enforced.

You can Copy link and refresh the evidence. A dashboard can rerun its widget queries.

What is recorded when you open a proof page

The Console records that you opened the page: the kind of page, the project, the id in the link for an issue, trace, agent run, incident, dashboard, finding or stored result, your name as a member of the workspace, and the time. It records no page content. For a person or a session replay it records the kind only and never the id.

Everyone in the workspace who can read the agent activity record sees how many pages were opened. Only owners and administrators see who opened. The record is kept 30 days. It is one request with your own sign-in. It uses no cookie and no other service. See Which proof pages people opened.

The project is in the link

Every proof link names its project. The address ends with ?project_id=<project-id>. The page reads only that project, even when you have selected a different project in the Console. The page shows the project name and your signed-in account at the top, so you can see whose data you are looking at.

A link without a project is never guessed. A tool result that cannot name its project carries no link at all. If you receive a link that has no project, the page says This link does not name a project and shows nothing. Ask the agent for a new link.

When you cannot open a link

You must be signed in, and you must be allowed to read what the page shows. A link does not give access to anyone. It only points to a page, and the page checks your permissions every time.

What you see	Why	What to do
The sign-in page	You are not signed in	Sign in. The Console then returns you to the link.
You can't open this project	The link is for a project you do not belong to, or the project no longer exists. Nothing from it is shown.	Ask a workspace owner for access, or ask the agent for a link to a project you can open.
This link does not name a project	The project is missing from the link	Ask the agent for a new link.
A message that a permission is required	Your role cannot read this kind of data. For example, analytics results need analytics and person read permissions.	Ask an owner or administrator to give you the permission.
Measurement expired or Measurement withdrawn	An analytics result is kept for a limited time, and a result can be withdrawn	Ask your agent to measure it again.
Link incomplete or damaged	The address is missing a part, for example the result id	Ask the agent for a new link.

Page content that you are not allowed to see is hidden. It is never shown in part.

Select Copy link in the page header. The link has everything the page needs. Send it to a teammate in your workspace. They sign in, and they see the page if their role can read it.

Do not send a proof link to a person outside your workspace. They cannot open it. If you need to show a screen to anyone without signing in, use a Live link instead. A Live link is a different thing: it contains a secret, shows its screen to anyone who holds it, and is not a proof page. You list and revoke Live links in the Console under Published links. See Live viewing links and access.

What the agent should say

A good answer from an agent has three parts: the conclusion, the evidence it used, and the link that opens the proof. If the answer does not have a link, ask the agent for the exact tool result that supports each claim. Every result also lists its evidence as citations that you can fetch with the fetch tool.

The result viewer: the four ways /view/result opens an analytics result.
The Console: the ten control pages.
Quickstart: sign up, connect your agent, ask, and open the proof.