List pages

Ask your agent to read a connected repo's page registry — the inventory of pages behind its e-commerce accessibility conformance report.

"List the pages Equall has registered for acme/shop." "Which pages on acme/shop still need a classification?"

Equall builds the registry from three sources, joined together:

• Code routes — patterns like /products/[slug] detected straight from the repo.
• Sitemap — concrete URLs pulled from the site's sitemap.xml, matched back to their route.
• Manual — pages added by hand with add_page, for anything the first two miss.

Each page also carries its resolved legal scope under the Belgian e-commerce accessibility guidelines (§5.6) — contract_path, product, editorial_out_of_scope, archived_exempt, or other_in_scope. A page inherits its route's classification unless it has its own; null means still unclassified.

Filtering

• By source: code_route, sitemap, or manual.

  "Show only the manually added pages on acme/shop."

• By scope: any of the five §5.6 scopes, or unclassified for the ones still needing a decision:

  "Which pages on acme/shop are still unclassified?"

• Large registries are capped per request (50 pages by default, up to 200). When the list is truncated, the agent is told the true total so it can narrow the filter or ask for more.

Classification stays a human decision

The registry can carry a suggested §5.6 scope, but confirming one is always done in the dashboard, by a workspace member — never through the agent. See Add a page for how a suggestion gets attached.