# NextBillion.ai vs Woosmap (slim)

> 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.

- Full: https://www.anchorterminal.com/compare/nextbillion-vs-woosmap.md (~3,850 tokens) · this version ~1,780 tokens · JSON https://www.anchorterminal.com/compare/nextbillion-vs-woosmap.json · canonical https://www.anchorterminal.com/compare/nextbillion-vs-woosmap
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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: C 55.4, rank #869 of 1486 · https://www.anchorterminal.com/tools/nextbillion.min.md
- Woosmap: C 59.4, rank #704 of 1486 · https://www.anchorterminal.com/tools/woosmap.min.md
- NextBillion.ai, 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.
- Woosmap, 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.

| Category | NextBillion.ai | Woosmap |
| --- | --- | --- |
| Reliability (16%) | 45 | 78 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 73 | 81 |
| Agent ergonomics (13%) | 77 | 76 |
| Security & auth (14%) | 46 | 43 |
| Payments & pricing (10%) | 20 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 73 | 26 |
| Transparency & trust (7%) | 58 | 54 |

| Fact (where they differ) | NextBillion.ai | Woosmap |
| --- | --- | --- |
| Vendor | NextBillion.ai Pte. Ltd. | WOOSMAP SAS |
| Hosted endpoint | `https://mcp.nextbillion.io` | `https://api.woosmap.com/mcp` |
| Auth | OAuth or key | API key |
| Pricing | Paid | Freemium |
| Tools exposed | 27 | 9 |
| Last release | 2026-10-30 | none |
| Privacy policy last updated | no date given | 2024-07-01 |

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.)