Skip to content
SkillVerification

Outside-In Agent Crawl Verification

Verify a deployed public surface from outside the runtime using canonical URLs, machine endpoints, representative crawler user agents, payload-leak checks and provider indexing observations instead of trusting deployment success.

Problem
CI and deployment commands can pass while public routing, DNS, canonical origins, crawler handling, static metadata or provider discovery are wrong.

Core outcomes

  • Post-deploy public route readback
  • Representative crawler user-agent checks
  • Canonical-origin and sitemap consistency proof
  • Machine-surface inventory validation
  • Payload and retired-route fencing
  • Provider crawl/index state kept separate
  • Deployment regressions caught before promotion

Requirements

Preconditions an agent should verify before selecting this capability.

  • A deployed public origin
  • Known canonical route inventory
  • Machine discovery surfaces to verify
  • Ability to make unauthenticated outside-in HTTP requests
  • Expected product/capability count
  • Optional search-provider inspection access

Boundaries

Published limitations that constrain safe use.

  • HTTP 200 does not prove indexing
  • Sitemap submission does not prove crawl or index
  • Crawler user-agent acceptance does not prove provider ingestion
  • Synthetic checks do not prove every geographic edge
  • Do not perform unauthorised mutating probes

Catalogue source

Repository:
AyobamiH/agent-shop-products (main)
Payload path:
products/outside-in-agent-crawl-verification/SKILL.md

Price, ratings, reviews and the full prompt body are not published. Nothing on this page is inferred from data the catalogue does not contain.

Machine-readable

metadata Markdowncanonical catalogue JSONagent discovery text

Tags

  • #outside-in
  • #crawl-verification
  • #deployment-acceptance
  • #crawler-user-agent
  • #indexing
  • #readback

Related products

Selected by shared category and catalogue tags. No popularity or purchase signal exists.

  • SkillAgent Governance

    State-Transition Evidence Contract

    Define and enforce separate availability, execution, consequence, readback, outcome, evidence and freshness states so agents cannot promote a lower-layer success into an unverified higher-layer claim.

    products/state-transition-evidence-contract/SKILL.md

    #state-machine#evidence#readback+4
    inspect