Yes, with a human handoff

Can an AI agent find Status Page Guidance on Github?

As of Jun 27, 2026, CrawlDex verdict for github.com/dev_saas_api.find_status_page_guidance is Yes, with a human handoff (n=48).

Yes, with a human handoff - as of Jun 27, 2026, CrawlDex evidence shows that AI agents can find Status Page Guidance on Github with a human handoff. 40% task outcome signal across 48 observations; leading observed condition: Public Url Verified.

Last verified Jun 27, 2026Based on 48 observationsMain blocker: Public Url Verified

AES

40% outcome signal

Success 6%Handoff 35%Partial 12%Blocked 47%

What happens when an agent tries

Agent path for find Status Page Guidance

CrawlDex currently marks this route as constrained. 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.

Agent notes

Preflight notes for Github

Github find Status Page Guidance currently reports yes, with a human handoff with 48 observations and medium confidence.
The main observed blocker is Public Url Verified; keep the human available before login, payment, identity, or final-submission steps.
Use this as a preflight signal, then compare the ranking and same-task links below before choosing whether to send a browser agent.

What blocks agents

Observed friction

Public Url Verified Sparse Public Text

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

observations

Confidence

medium

Confidence reflects 2.91 effective weight, Wilson bounds 0.08305-0.830712, and Beta posterior mean 0.440715.

Freshness

stale

Latest evidence is 80.6 days old.

Route key: github.com / dev_saas_api.find_status_page_guidance

Agent Trust Record

Get this as a Trust Record

Use the citable ATR before an agent attempts this public website task. It includes verdict, confidence, blockers, user-presence rules, evidence links, and the correction path.

curl -s https://crawldex.com/api/v1/trust-record/github.com/dev_saas_api.find_status_page_guidance

Trust Record API

For agent buildersPreflight before acting

curl -X POST https://crawldex.com/api/v1/preflight \
  -H 'content-type: application/json' \
  -d '{"site":"github.com","task":"dev_saas_api.find_status_page_guidance"}'

Developer hub MCP endpoint

Lattice links

Related CrawlDex paths

Github agent reliability report Browse agent task evidence Submit an observation for Github find Status Page Guidance

Blocker pages

Websites with Public Url Verified friction Websites with Sparse Public Text friction

Same task on other sites

Atlassian find Status Page Guidance reportAES 80 Fastly find Status Page Guidance reportAES 80 Linear find Status Page Guidance reportAES 40 Postman find Status Page Guidance reportAES 40

Other tasks on Github

Github read docs reportAES 100 Github monitor prices reportAES 100 Github cancel a subscription reportAES 100 Github check rate limits reportAES 94

Source: CrawlDex, 48 observations, June 2026 — https://crawldex.com/sites/github.com/dev_saas_api.find_status_page_guidance

Negative or friction claim

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

Dispute this report