agenttru.st

Flusterduck bronze

flusterduck.com

“Flusterduck detects UX friction automatically from behavioral signals (rage clicks, dead clicks, form abandonment, navigation loops, and more). It computes a real-time confusion score for every page, clusters repeated signals into ranked UX issues tied to specific elements, and verifies with deploy correlation whether a shipped fix actually reduced friction. No session replay, no DOM recording, no form values, no keystrokes. The browser SDK observes behavioral signals (clicks, scroll, timing), element selectors, visible element labels (PII-redacted in the browser before sending), and acquisition context (UTM parameters, referrer host).

a2a https://flusterduck.com talk to it https://flusterduck.com/.well-known/agent-card.json its card
πŸ‡ΊπŸ‡Έ US Β· Amazon.com, Inc. Checked 2h ago pushNotifications, stateTransitionHistory, streaming

we checked this    the operator says this

Community rating 0 0 up Β· 0 down β€” sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate
Issued by Let's Encrypt domain-validated
Valid until 26 Nov 2026.
Control of the hostname was checked; nothing about who operates it.
DANE / TLSA
Not verified
Discovery
Well-known document
AI-facing documents
Publishes /llms.txt β€” “Flusterduck” a curated map of the site's content for language models
Fetched from this host during verification. Neither document is how this agent was discovered.
First seen
2 Sep 2026
View verification details
Assurance
bronze Bronze β€” agent card fetched over HTTPS with a valid certificate
Protocols
A2A verified by handshake or card fetch, not merely advertised
Hosted in
πŸ‡ΊπŸ‡Έ US Β· Amazon.com, Inc. (AS16509)
Last checked
2h ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks β€” the operator of flusterduck.com controls every word below.

Query confusion scores and UX issues

Read per-page confusion scores (0-100, z-score normalized against a 7-day baseline), ranked UX issues tied to specific elements, active alerts, and deploy verification history for a site.

ux-analyticsreadmonitoring
Examples it gives
  • What's broken on /checkout right now?
  • List open UX issues sorted by severity.
  • Did the last deploy make confusion on /pricing worse?

Run typed Explore queries over behavioral data

A deterministic, closed-vocabulary query engine (no natural language, no LLM) over session and event data: a time window, up to 12 AND-ed filters (signal, page, source, confused, converted, event_type), and one output mode: list matching sessions or measure a metric (count, avg_pageviews, conversion_rate, avg_dwell_ms, bounce_rate), optionally grouped by page/source/day/signal/cohort.

ux-analyticsreadquery-engine
Examples it gives
  • List sessions with a rage click on /checkout in the last 14 days.
  • What's the conversion rate for sessions that hit a dead click, grouped by traffic source?

Confused-vs-calm conversion analysis

Splits a site's sessions into a confused cohort (produced at least one friction signal) and a calm cohort (zero friction signals), then compares conversion rate, session duration, pages per session, and bounce rate between them, broken down by page and traffic source, with ranked narratable insights.

ux-analyticsreadrevenue
Examples it gives
  • How much less do confused sessions convert than calm ones?
  • Which pages bleed the most conversions to confusion this week?

Verify deploys against confusion scores

Records a deploy's pre-release confusion snapshot, then compares it against post-release confusion once enough traffic accumulates (typically 5 minutes) to verify whether a shipped fix actually reduced friction or introduced a regression.

ux-analyticsreadci-cd
Examples it gives
  • Did yesterday's deploy break anything on checkout?
  • Show me confusion_before and confusion_after for the last release.

Triage issues and manage alert rules

Update UX issue status/assignment/notes, acknowledge or resolve alerts, and create or update alert rules (spike, anomaly, trend, co-occurrence, positive, budget) with email, Slack, webhook, or PagerDuty delivery. Requires a manage:write-scoped key or a signed-in user.

ux-analyticswritetriage
Examples it gives
  • Triage the open issues and tell me what to fix first.
  • Create a spike alert for the pricing page and notify Slack.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider
Flusterduck β€” what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol
a2a
Version
1.0.0
Auth schemes
bearerAuth
Card completeness
a2a.proto v1.0 requires eight top-level fields. This card omits:
supportedInterfaces
Missing fields do not affect listing β€” they describe how much the operator has published, not whether the agent was verified.
View all card details
Capabilities
pushNotifications stateTransitionHistory streaming
Agent card
https://flusterduck.com/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.