Full URL list
Get back a flat array of every page URL the site exposes, ready to feed straight into another endpoint.
POST /v1/map
Discover every page URL for a domain before you crawl or extract.
Point your agent at a domain and get back a flat list of every page URL, parsed from robots.txt and sitemap.xml. Built in Rust, it resolves sitemap indexes recursively so one request can surface thousands of links, ready to feed into batch or crawl.
Get back a flat array of every page URL the site exposes, ready to feed straight into another endpoint.
Nested sitemap indexes are followed automatically, so a single request can surface thousands of links from one domain.
It reads robots.txt for sitemap references first, then falls back to /sitemap.xml when none are declared.
Map a site before you scrape it to scope the work, skip dead routes, and feed the right URLs into batch.
01
POST the base URL of the site you want to map with your API key.
02
We read robots.txt for declared sitemaps, then look for /sitemap.xml if none are listed.
03
Sitemap indexes are expanded recursively to collect every listed page in one pass.
04
You get a deduplicated array of discovered URLs plus a total count.
A sitemap API takes a domain and returns the list of page URLs that site publishes, parsed from its robots.txt and sitemap.xml. It is how an agent learns what pages exist before deciding what to crawl or extract.
Send the base URL to POST /v1/map. It reads robots.txt for declared sitemaps, falls back to /sitemap.xml, resolves any sitemap indexes recursively, and returns a flat array of every discovered URL with a total count.
Map only discovers URLs from a site's sitemaps and returns them as a list, so it is fast and cheap. Crawl actually visits pages and extracts their content. A common pattern is to map first, then feed the URLs into batch or crawl.
It checks robots.txt and /sitemap.xml first. If neither exists, the URL list will be limited to what those sources expose, so for sites without a sitemap you will want crawl instead, which follows links from the pages themselves.
No. Credits are only consumed on successful responses. A standard page is 1 credit; heavier work like JS rendering or protected-site access costs a few extra credits.
One credit pool, every endpoint. Cancel anytime, or self-host the open-source core for free.
Cookies & analytics
We'd like to use analytics to understand how this site is used. Nothing loads or fires until you agree. See our privacy policy for the full list of processors.