Find the feed.
Keep the evidence.

Help agents reach a website’s release feed or machine-readable updates, with the source and verification kept in view.

Live lookups are not yet open. Start with the illustrative result or the agent instructions below.

View the evidence example

When enabled, the bounded checker accepts one public HTTP or HTTPS website URL. URLs with query strings bypass shared caching and contribution storage.

Illustrative example — not a live check
  1. https://example.test/notes
  2. Advertised feed
  3. https://example.test/releases.xml
  • ATOM
  • Reachable
  • Valid format
Inspect the example evidence

How Pathmote finds a route

Pathmote follows a website’s own signals to surface a source you can inspect. It checks in a fixed order, reports limits beside findings, and never recursively crawls or guesses common paths.

  1. Start with the website.Classify a direct feed or inspect one HTML landing page. Every redirect counts toward the 10-request maximum.
  2. Follow explicit signals.Feed links lead; robots, API Catalog and sitemap signals add bounded context. Pathmote does not guess paths or execute advertised tools.
  3. Keep the boundary clear.Verify candidates in stable order for up to 10 seconds total, return at most 10 findings, and show skipped or failed checks as evidence.

Illustrative example — not a live check

Synthetic .test data shows the source, candidate and verification path you can inspect.

Synthetic data

2 entry points found

https://example.test/notes
Status
Found
Coverage
Partial
Findings
2
Coverage is partial. Useful findings may still be present; review the limitations and checks before relying on this result.
Fresh check Checked Expires Request illustrative-request

Limits of this result

  • The robots check timed out, so coverage is partial.
  • The advertised API catalog was retained but not checked within this example's request budget.
View 3 checks
  1. Ok · HTTP 200 · 164 ms
  2. Ok · HTTP 200 · 91 ms
  3. Timeout · 3000 ms
Raw JSON