CrawlDex
Check

Blocked

Can an AI agent check Case Status on Uscis?

Blocked - as of Jun 17, 2026, AI agents can check Case Status on Uscis. 70% task outcome signal across 3 observations; main blocker: Login Required.

Last verified Jun 17, 2026Based on 3 observationsMain blocker: Login Required

AES

70

70% outcome signal

70
Success 0%Handoff 5%Partial 10%Blocked 85%

What happens when an agent tries

Agent path for check Case Status

CrawlDex currently marks this route as blocked. Agents should treat the route as a measured website task, verify the current page state, and stop before irreversible user actions unless the human has approved them.

Recipe signal: recipe://uscis.gov/legal_admin.check_case_status/public-preflight-v1

What blocks agents

Observed friction

Login RequiredBot Blocked

Human handoff

What a human must still do

This route has authentication, payment, user-presence, or handoff friction. Keep the human available for identity checks, account decisions, price confirmation, and any final submission.

Evidence

Observation basis

Based on

3

observations

Confidence

low

Confidence reflects 0.81 effective weight, Wilson bounds 0.086617-0.982641, and Beta posterior mean 0.55731.

Freshness

fresh

Latest evidence is 0 days old.

Route key: uscis.gov / legal_admin.check_case_status

For agent buildersPreflight before acting
curl -X POST https://crawldex.com/api/v1/preflight \
  -H 'content-type: application/json' \
  -d '{"site":"uscis.gov","task":"legal_admin.check_case_status"}'
Developer hubMCP endpoint

Lattice links

Related CrawlDex paths

Blocker pages

Websites with Login Required frictionWebsites with Bot Blocked friction

Other tasks on Uscis

Uscis check Form Edition reportAES 80Uscis find Form Filing Guidance reportAES 80Uscis download forms reportAES 50Uscis find Case Status Tool reportAES 0

Negative or friction claim

Think this is wrong? Dispute this report. CrawlDex keeps methodology and correction paths visible for measured claims.

Dispute this report