Firecrawl map sitemap skip/include/only: Sume crawl_map has no switch

Firecrawl's /map has a sitemap option (skip, include, only) and includeSubdomains. Sume's crawl_map takes only url and limit, and maps one origin.

4 min readSume
All posts

If your code sets sitemap to skip, include or only (default include), or leaves includeSubdomains on (default true), nothing in Sume's crawl_map request carries either. The request has url and limit; Sume maps the origin of the URL you give it.

Which map options carry over?

Firecrawl values are from its map reference; the Sume side is from the OpenAPI request schema for /v1/firecrawl/map.

What to do instead of a map option, read 2026-09-30
You wantFirecrawl optionOn Sume
Skip the sitemapsitemap: skipNo switch; request carries url and limit only
Sitemap URLs onlysitemap: onlyNo switch; scrape the sitemap file URL yourself
Include subdomainsincludeSubdomains (default true)Map each subdomain origin as its own call

What if I need a sitemap-only list?

There is no setting for it. If the site publishes a sitemap file at a URL you know, you can read that URL as an ordinary public page with crawl_scrape. That is a separate call and the page is untrusted content, as the tool description notes for all remote pages.

What if I need subdomains?

Map each subdomain you care about as its own call, since a call covers the origin of the URL you pass.

curl -X POST https://api.sume.com/v1/firecrawl/map \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "url": "https://docs.example.com", "limit": 100 }'

Where does the map fit in a workflow?

Per MCP tools and gates the sequence is map, pick, scrape. The numeric ceiling is covered in the 5000 vs 100 limit post.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume