CrawlDex
Blockers

What's stopping agents right now

Login walls, CAPTCHAs, handoffs, policy prompts, unstable pages, and confirmation traps - the walls agents hit most and which routes have them.

Blocker types 17 tracked in taxonomy
Affected routes 324 routes with known friction
Most common login_required 275 routes
Severity 3 / user

login required

The flow requires account authentication.

275 routes friction
Severity 3 / merchant

human handoff required

The final step requires chat, phone, email, or manual review.

104 routes friction
Severity 4 / merchant

hidden fee

Mandatory fee appears late in the flow.

66 routes friction
Severity 3 / user

2fa user present

A user-present identity step is required before continuing.

61 routes friction
Severity 2 / merchant

dynamic dom unstable

Selectors or visible state move during the task.

56 routes friction
Severity 3 / user

payment 3ds user present

A 3-D Secure, bank, wallet, or payment authorization step requires the user to be present.

46 routes friction
Severity 3 / merchant

forced account creation

Guest or agent-friendly completion is not available.

44 routes friction
Severity 4 / merchant

price mismatch

The amount changes or is ambiguous near confirmation.

37 routes blocking
Severity 4 / merchant

dark pattern cancel

Cancellation path uses confusing or adversarial retention mechanics.

9 routes friction
Severity 2 / merchant

confirmation email missing

The flow completes, but durable confirmation evidence is missing.

8 routes friction
Severity 5 / merchant

bot blocked

The site blocks the agent runtime or IP class.

4 routes blocking
Severity 3 / merchant

policy unparseable

Policy terms are not machine-readable enough to evaluate eligibility.

3 routes friction
Severity 4 / merchant

captcha

Interactive bot challenge blocks autonomous completion.

2 routes blocking
Severity 2 / merchant

hidden modal

A popup, interstitial, or overlay interrupts navigation.

2 routes friction
Severity 1 / merchant

confirmation email clean

The flow emits durable, machine-readable confirmation evidence.

0 routes friction
Severity 1 / merchant

human handoff clean

A required handoff is explicit, bounded, and easy for the user to complete.

0 routes friction
Severity 1 / merchant

policy parseable

Relevant policy terms are clear enough for an agent to parse and cite.

0 routes friction