Map a website's URL structure via Tavily's AI-powered site mapper, paid per call over MPP/Tempo.
What it does
The Tavily Map endpoint discovers and returns URLs from a given website. You provide a starting URL and optional parameters controlling crawl depth, breadth, result limit, and natural-language instructions to guide URL discovery. The endpoint returns a structured list of discovered URLs, making it useful for building sitemaps, auditing site structure, or feeding downstream crawl/extract pipelines.
This endpoint is served through the Locus MPP (Micropayment Protocol) gateway and settles payments on Tempo L2 using pathUSD. Each call costs $0.09 (90,000 base units at 6 decimals). The payment intent is "charge", meaning a one-shot payment per request. The OpenAPI spec is well-defined with a clear request schema (required field: `url`; optional: `max_depth`, `max_breadth`, `limit`, `instructions`).
Note that the endpoint is part of a broader Tavily suite exposed through the same MPP gateway, which also includes search, extract, and crawl endpoints at sibling paths. The probe returned 404 on HEAD/GET because this endpoint only accepts POST requests — this is expected behavior, not a sign the endpoint is down. Official Tavily documentation is available at docs.tavily.com, and Locus-specific docs are referenced at beta.paywithlocus.com/mpp/tavily.md.
Capabilities
Use cases
- —Generating a sitemap of all discoverable URLs on a target domain
- —Auditing website structure before a migration or redesign
- —Feeding discovered URLs into a downstream extract or crawl pipeline
- —Filtering site URLs with natural-language instructions (e.g., only blog posts)
- —Enumerating pages for SEO analysis
Fit
Best for
- —AI agents that need to understand a website's structure before deeper extraction
- —Automated site auditing and link discovery workflows
- —Developers who want pay-per-call site mapping without managing API keys
Not for
- —Full-page content extraction (use the /tavily/extract or /tavily/crawl endpoints instead)
- —High-volume bulk crawling where per-call pricing becomes expensive
- —Users who cannot settle payments via Tempo L2 / pathUSD
Quick start
curl -X POST https://tavily.mpp.paywithlocus.com/tavily/map \
-H "Content-Type: application/json" \
-d '{"url": "https://example.com", "limit": 50}'Example
Request
{
"url": "https://example.com",
"limit": 50,
"max_depth": 3,
"max_breadth": 10,
"instructions": "Only discover blog and documentation pages"
}Endpoint
Quality
The OpenAPI schema is complete with clear request parameters, pricing, and payment method. However, the probe did not capture a live 402 challenge (only 404 on HEAD/GET, expected since the endpoint is POST-only), no response schema or example response is available, and crawled pages returned only generic 404 JSON. No actual 200 response example exists in the bundle.
Warnings
- —Probe returned 404 on HEAD and GET; endpoint likely only accepts POST — not confirmed live via 402 challenge on POST
- —No response schema or example response provided in the OpenAPI spec
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on context; not independently verified
Citations
- —The /tavily/map endpoint costs 90,000 base units in pathUSD per call (≈$0.09)https://tavily.mpp.paywithlocus.com
- —Payment settles via Tempo L2 with intent 'charge'https://tavily.mpp.paywithlocus.com
- —Request schema requires 'url' and optionally accepts max_depth, max_breadth, limit, and instructionshttps://tavily.mpp.paywithlocus.com
- —Official Tavily API documentation is at docs.tavily.comhttps://tavily.mpp.paywithlocus.com
- —Locus-specific docs referenced at beta.paywithlocus.com/mpp/tavily.mdhttps://tavily.mpp.paywithlocus.com