# NextBillion.ai vs Woosmap

> Woosmap scores 59.4 (C) to NextBillion.ai's 55.4 (C) for geo routing. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/nextbillion-vs-woosmap
- Markdown: https://www.anchorterminal.com/compare/nextbillion-vs-woosmap.md (~3,850 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Woosmap scores 59.4 (C) on agent readiness against NextBillion.ai's 55.4 (C), and leads in 3 of 7 scored categories. NextBillion.ai leads on maintenance & community. Both do geo routing.

- NextBillion.ai: grade C, 55.4/100, rank #874 of 1510. Markdown https://www.anchorterminal.com/tools/nextbillion.md · JSON https://www.anchorterminal.com/api/v1/tools/nextbillion.json
- Woosmap: grade C, 59.4/100, rank #707 of 1510. Markdown https://www.anchorterminal.com/tools/woosmap.md · JSON https://www.anchorterminal.com/api/v1/tools/woosmap.json
- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md
- All 153 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md

## Which one, for what

### NextBillion.ai (C)

Good for: Fleet and delivery routing, distance matrices and route optimisation with truck profiles, plus geocoding and POI search, for companies ready for an annual contract.

Ahead on:
- Maintenance & community, 73 against 26

Watch for: Pricing is by quote on annual licences, with no public unit prices

### Woosmap (C)

Good for: Store locators, address autocomplete and distance for retail and logistics teams that keep their own location data in the platform, with an MCP server for agents.

Ahead on:
- Reliability, 78 against 45
- Schema & documentation, 81 against 73
- Payments & pricing, 30 against 20

Watch for: No public changelog or release notes for the APIs


## Why the edge

### Maintenance & community: NextBillion.ai +47

- NextBillion.ai (73): MCP server 0.5.3 on 30 October 2026 (30). Eleven tagged MCP releases between 7 October and 30 October, adding hosted mode, truck routing and geometry tools (20). Support by email, a public MCP repository with a changelog, but no public API changelog (8). The MCP server isn't in the official MCP registry, and we didn't check the mobile SDK versions (7). The MCP repository runs CI with unit and end-to-end tests (8). 30+20+8+7+8 = 73.
- Woosmap (26): No dated API release, changelog or release note found. The newest dated activity we saw is the public woosmap-samples repository on 16 September 2026, which isn't an API release (10). No dated changes to count in the last 90 days (0). Support by email and a support centre, with no public changelog (5). Official JavaScript, iOS and Android SDKs exist, but we couldn't check their versions because the GitHub API was rate-limited and two SDK repository names didn't resolve; the MCP server isn't in the official MCP registry (8). The samples carry tests, per the rate-limits page (3). 10+0+5+8+3 = 26.

### Reliability: Woosmap +33

- NextBillion.ai (45): Hosted lines, for the REST APIs at api.nextbillion.io and the hosted MCP server. A status page at status.nextbillion.io, 'NextBillion.AI API Status', renders only in a browser, and its Statuspage-style JSON paths return 404, so we couldn't see its components (10) or read any history. That's our limit, not a finding, and the rubric gives 5 (5). The API reference states 2,400 queries a minute, or 40 a second, for continuous requests (15). Each endpoint's error table lists 429 as 'QPM or API request count quota reached', with no Retry-After or backoff guidance (5). No SLA found; the terms say access isn't warranted to be uninterrupted (0). The REST APIs are GA. The MCP server is at version 0.5.3 (10). 10+5+15+5+0+10 = 45.
- Woosmap (78): Hosted lines. Atlassian Statuspage at status.woosmap.com with seven components (Localities, Store Search, Geolocation, Distance, Address, Map and Indoor APIs) (20). The status home page lists no incidents from 23 October to 6 November 2026. The full history page loads by script and the site's robots.txt disallows /api/, so the rest of the 90 days wasn't read and the line is held between the unreadable and minor tiers (10). Each endpoint's reference states its own rate limit, such as 50 a second, shared by a project's keys (15). Every response carries RateLimit-Policy and RateLimit headers, and the rate-limits page says to wait `t` seconds after a 429, retry at most three times and back off 1, 2 and 4 seconds when the header is missing, with sample code (15). A 99.9% SLA on the Enterprise plan per the pricing page; we didn't read its terms (8). GA (10). 20+10+15+15+8+10 = 78.

### Payments & pricing: Woosmap +10

- NextBillion.ai (20): No x402, MPP or L402 (0). Pricing is by quote, with annual licences per order, asset or API call and no published unit price (0). A 7-day free trial with an API key and 'No credit card required' (20). A person signs up through the console or emails support for a key (0). 0+0+20+0 = 20.
- Woosmap (30): No x402, MPP or L402 (0). Plans and per-API tier breakpoints are public, but per-request prices sit in a script-driven calculator we couldn't read, so plan-only credit (10). Free plan up to 10,000 requests a month with 'No Credit Card Required' (20). A person signs up and creates a key in the console (0). 0+10+20+0 = 30.

### Schema & documentation: Woosmap +8

- NextBillion.ai (73): No OpenAPI document for the REST APIs was found in llms.txt or the docs. The hosted MCP server's 27 tools are defined with Zod schemas, so they carry typed JSON Schema inputs (15 of 25). llms.txt, llms-full.txt and a Markdown file for each docs page (10). Endpoint pages explain each parameter, and MCP tool descriptions say when not to use a tool, such as the geometry tools being straight-line rather than road distance (16). Parameter tables give types, allowed values and defaults, such as `types` and `limit` (default 10), though `in` packs several filters into one string (12). curl examples and a per-endpoint error table with causes (13). The MCP server has a dated changelog. No API changelog or versioned path was found (7). 15+10+16+12+13+7 = 73.
- Woosmap (81): OpenAPI 3.1 spec, version 1.46.3, with 47 paths across Localities, Stores, Distance, Datasets, Indoor, Map and what3words endpoints (25). llms.txt as a routing index, llms-full.txt and a Markdown twin of every page (10). llms.txt says which pages are authoritative for parameters and which explain products, and endpoint pages describe purpose, with little on when not to call one (15). Typed parameters from the spec with enums and required fields (13). The spec documents 400, 401, 402, 403, 404, 409, 422 and 429 responses, and pages carry examples (13). The spec is versioned, but no public changelog or release notes were found (developers.woosmap.com/changelog/ and /release-notes/ return 404) (5). 25+10+15+13+13+5 = 81.

## Score by category

| Category | Weight | NextBillion.ai | Woosmap | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 45 | 78 | Woosmap +33 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 73 | 81 | Woosmap +8 |
| Agent ergonomics | 13% (16.2 this run) | 77 | 76 | NextBillion.ai +1 |
| Security & auth | 14% (17.5 this run) | 46 | 43 | NextBillion.ai +3 |
| Payments & pricing | 10% (12.5 this run) | 20 | 30 | Woosmap +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 73 | 26 | NextBillion.ai +47 |
| Transparency & trust | 7% (8.8 this run) | 58 | 54 | NextBillion.ai +4 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **55.4 · C** | **59.4 · C** | |

## Facts side by side

| Fact | NextBillion.ai | Woosmap |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | NextBillion.ai Pte. Ltd. | WOOSMAP SAS |
| Hosted endpoint | `https://mcp.nextbillion.io` | `https://api.woosmap.com/mcp` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Tools exposed | 27 | 9 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | none |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 2024-07-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |

## Verdicts

**NextBillion.ai.** NextBillion.ai covers routing, distance matrices, route optimisation, geocoding and places, and runs a hosted MCP server with 27 read-only annotated tools and OAuth sign-in. Pricing is by quote on annual licences, the REST API key travels in the query string, and no OpenAPI spec, API changelog or readable status history was found.

**Woosmap.** Woosmap publishes an OpenAPI 3.1 spec, llms.txt with Markdown pages, per-endpoint rate limits and 429 retry rules, plus a hosted nine-tool MCP server. No changelog, security.txt, API data retention statement or readable per-request price was found, and private keys can travel in the query string.

## Before you call either

### NextBillion.ai

1. Connect through https://mcp.nextbillion.io so the key stays in a Bearer header or OAuth token rather than in request URLs
2. Use the geometry tools only for straight-line questions; use directions or distance_matrix for travel time
3. Batch up to 100 geocodes with geocode_batch instead of one call per address
4. On 429 the quota or the 2,400-a-minute limit is reached; slow down and tell the user if credits are spent
5. Search the docs with the MCP documentation tools before guessing a parameter

### Woosmap

1. Send the private key in the X-Api-Key header, not the private_key query parameter
2. Use a read-only private key for the MCP server unless the task writes stores or datasets
3. On 429 wait the `t` seconds from the RateLimit header, retry at most three times, and pause batches when `r` reaches 0
4. Use find_stores_nearby for the customer's own locations and find_nearby for public POIs
5. Read endpoint parameters from the /api-reference/ Markdown pages, which llms.txt marks as authoritative

## Questions

### Which is better for AI agents, NextBillion.ai or Woosmap?

Woosmap scores 59.4 (C) on agent readiness against NextBillion.ai's 55.4 (C), and leads in 3 of 7 scored categories. NextBillion.ai leads on maintenance & community.

### Do NextBillion.ai and Woosmap need an API key?

NextBillion.ai takes an API key or an OAuth sign-in. Woosmap needs an API key.

### Can an agent call NextBillion.ai and Woosmap without installing anything?

Yes. NextBillion.ai has a hosted endpoint at https://mcp.nextbillion.io and Woosmap at https://api.woosmap.com/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/nextbillion-vs-woosmap.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nextbillion-vs-woosmap.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "nextbillion", "b": "woosmap"}`. From a terminal: `anchor compare nextbillion woosmap`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nextbillion.json and https://www.anchorterminal.com/api/v1/tools/woosmap.json

## Other comparisons with NextBillion.ai or Woosmap

- [Amazon Location Service vs NextBillion.ai](https://www.anchorterminal.com/compare/amazon-location-vs-nextbillion.md)
- [Amazon Location Service vs Woosmap](https://www.anchorterminal.com/compare/amazon-location-vs-woosmap.md)
- [ArcGIS Location Platform vs NextBillion.ai](https://www.anchorterminal.com/compare/arcgis-vs-nextbillion.md)
- [ArcGIS Location Platform vs Woosmap](https://www.anchorterminal.com/compare/arcgis-vs-woosmap.md)
- [Azure Maps vs NextBillion.ai](https://www.anchorterminal.com/compare/azure-maps-vs-nextbillion.md)
- [Azure Maps vs Woosmap](https://www.anchorterminal.com/compare/azure-maps-vs-woosmap.md)
- [Geoapify Location Platform + MCP vs NextBillion.ai](https://www.anchorterminal.com/compare/geoapify-vs-nextbillion.md)
- [Geoapify Location Platform + MCP vs Woosmap](https://www.anchorterminal.com/compare/geoapify-vs-woosmap.md)
- [Geocodio vs NextBillion.ai](https://www.anchorterminal.com/compare/geocodio-vs-nextbillion.md)
- [Geocodio vs Woosmap](https://www.anchorterminal.com/compare/geocodio-vs-woosmap.md)
- [Google Maps Platform + Grounding Lite MCP vs NextBillion.ai](https://www.anchorterminal.com/compare/google-maps-platform-vs-nextbillion.md)
- [Google Maps Platform + Grounding Lite MCP vs Woosmap](https://www.anchorterminal.com/compare/google-maps-platform-vs-woosmap.md)
- [HERE Location Services vs NextBillion.ai](https://www.anchorterminal.com/compare/here-location-services-vs-nextbillion.md)
- [HERE Location Services vs Woosmap](https://www.anchorterminal.com/compare/here-location-services-vs-woosmap.md)
- [LocationIQ vs NextBillion.ai](https://www.anchorterminal.com/compare/locationiq-vs-nextbillion.md)
- [LocationIQ vs Woosmap](https://www.anchorterminal.com/compare/locationiq-vs-woosmap.md)
- [Mapbox APIs + MCP vs NextBillion.ai](https://www.anchorterminal.com/compare/mapbox-vs-nextbillion.md)
- [Mapbox APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/mapbox-vs-woosmap.md)
- [MapQuest vs NextBillion.ai](https://www.anchorterminal.com/compare/mapquest-vs-nextbillion.md)
- [MapQuest vs Woosmap](https://www.anchorterminal.com/compare/mapquest-vs-woosmap.md)
- [MapTiler Cloud vs NextBillion.ai](https://www.anchorterminal.com/compare/maptiler-vs-nextbillion.md)
- [MapTiler Cloud vs Woosmap](https://www.anchorterminal.com/compare/maptiler-vs-woosmap.md)
- [NextBillion.ai vs Nominatim](https://www.anchorterminal.com/compare/nextbillion-vs-nominatim.md)
- [NextBillion.ai vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/nextbillion-vs-opencage.md)
- [Nominatim vs Woosmap](https://www.anchorterminal.com/compare/nominatim-vs-woosmap.md)
- [OpenCage Geocoding API vs Woosmap](https://www.anchorterminal.com/compare/opencage-vs-woosmap.md)
- [Radar vs Woosmap](https://www.anchorterminal.com/compare/radar-vs-woosmap.md)
- [Stadia Maps vs Woosmap](https://www.anchorterminal.com/compare/stadia-maps-vs-woosmap.md)
- [TomTom Maps APIs + MCP vs Woosmap](https://www.anchorterminal.com/compare/tomtom-vs-woosmap.md)
- [NextBillion.ai vs Radar](https://www.anchorterminal.com/compare/nextbillion-vs-radar.md)
- [NextBillion.ai vs Stadia Maps](https://www.anchorterminal.com/compare/nextbillion-vs-stadia-maps.md)
- [NextBillion.ai vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/nextbillion-vs-tomtom.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp