Source actionability · no agent task run
Your site, through
an agent’s eyes.
Enter any public page and choose an agent profile. AgentLens will inspect the page’s real public HTML, map what it can and cannot observe, and show a source-based readiness snapshot.
Agent profile
This score summarizes observable HTML signals from one public page. It does not certify overall agent readiness or predict how a named provider performs. JavaScript behavior, sign-in flows, connected apps, runtime browsing, and task success require separate tests.
Make every agent journey visible.
Know where agents get through, where they get stuck, and what your next release changed. AgentLens is being built to turn agent activity into evidence your team can act on.
Good work starts
with a clear view.
Tools for teams that move with intention.
Locate a team plan and API setup guide
starting goalFound the pricing and API guide paths
search resultsRead route hints, then opened key pages
/pricing · /docsFound the API quickstart link
evidence capturedTHE AGENTS PEOPLE USE
Same web. Different kinds of work.
Pick a profile to frame the evaluation. The source scan is shared across profiles; provider behavior needs its own observed run.
A different agent for every kind of work.
Compare the personal agents people are trying, the work they’re reported to handle best, and how you can access them.
Muse
Purchasing · Email
Hark
Email · Online tasks
Town
Connected apps · Email
Instinct
Routines · Recommendations
Pally
Routines · Restraint
Knowing when not to actDots
Email · Online tasks
Ollie
Routines · Restraint
szn
Memory · Phone calls
Shuffle
Travel · Recommendations
Kicker
Purchasing · Proactive help
Reported snapshot · Source and date were not supplied. Scores, strengths, and access have not been independently verified by AgentLens.
Not another score.
A better view of the work.
A site can look ready on paper and still leave an agent circling the wrong page. AgentLens is being shaped around real tasks: what an agent tried, what the website returned, and whether the intended result was verified.
See how a run readsStart with the task
Write the job a person actually needs done. Track the path toward that outcome across pages and tools.
TASK-BASEDShow the evidence
Put observed actions beside the URLs, responses, and checks that support the outcome.
SOURCE-LINKEDCatch the regression
Compare runs after a change and pinpoint the step where a previously successful journey diverged.
RELEASE-AWAREFollow the trail.
Find the turning point.
Replay a sample journey and see how task intent, page actions, and verification fit together. All values are illustrative—this demo does not browse a live site.
“Find the team plan, then locate the API quickstart.”
Observed activity
Find the team plan and API quickstart.
Goal · read-only taskSearch results point to pricing and docs.
Search · 2 relevant pathsRobots and sitemap paths were read.
GET /robots.txt · 200 OKPricing and API guide links were discovered.
/pricing · /docs · 3 linksPlan details match the stated team size.
/plans/team · page evidenceAPI quickstart link found on the docs page.
Assertion · destination presentWhen connected to an agent runner, this is the kind of trail AgentLens aims to make inspectable.
Show what happened.
Be honest about what didn’t.
Agent behavior is hard to interpret. AgentLens should make the evidence legible without presenting guesses as facts.
What the run can prove
- ✓ Pages and links visited
- ✓ Tool calls and returned status
- ✓ Checks that passed or failed
- ✓ Timing and provider-reported usage
What stays a boundary
- ↗ No invented private thoughts
- ↗ No “success” without a check
- ↗ No live claims from demo data
- ↗ No credentials in this prototype
“The goal isn’t to watch a cursor move. It’s to know whether the work got done—and why.”
THE AGENTLENS PRINCIPLEFrom first scan
to release confidence.
AgentLens is an early product direction. The first version is focused on making a small number of valuable, read-only journeys easy to inspect and repeat.
Choose a journey
Describe a task and the outcome a successful run should prove.
PLANNEDObserve the path
Replay the observable steps through the site and linked tools.
PLANNEDCompare releases
Spot the change that shifted a journey, with a report your team can use.
PLANNEDMake room for
the agentic web.
Help shape an observability tool that makes agent journeys easier to understand, test, and improve.