# MapTiler Cloud vs NextBillion.ai (slim)

> MapTiler Cloud scores 62.1 (B) to NextBillion.ai's 55.4 (C) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/maptiler-vs-nextbillion.md (~4,200 tokens) · this version ~2,130 tokens · JSON https://www.anchorterminal.com/compare/maptiler-vs-nextbillion.json · canonical https://www.anchorterminal.com/compare/maptiler-vs-nextbillion
- 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)

MapTiler Cloud scores 62.1 (B) on agent readiness against NextBillion.ai's 55.4 (C), and leads in 4 of 7 scored categories. NextBillion.ai leads on agent ergonomics. Both do geocoding.

- MapTiler Cloud: B 62.1, rank #576 of 1510 · https://www.anchorterminal.com/tools/maptiler.min.md
- NextBillion.ai: C 55.4, rank #874 of 1510 · https://www.anchorterminal.com/tools/nextbillion.min.md
- MapTiler Cloud, good for Map tiles, static maps and worldwide geocoding with storable results for apps that also show a map, with EU data residency. Ahead on Schema & documentation, 79 against 73; Security & auth, 64 against 46; Payments & pricing, 40 against 20; Transparency & trust, 80 against 58.
- 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 Agent ergonomics, 77 against 70. Also A hosted endpoint, with nothing to install.

| Category | MapTiler Cloud | NextBillion.ai |
| --- | --- | --- |
| Reliability (16%) | 43 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 79 | 73 |
| Agent ergonomics (13%) | 70 | 77 |
| Security & auth (14%) | 64 | 46 |
| Payments & pricing (10%) | 40 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 70 | 73 |
| Transparency & trust (7%) | 80 | 58 |

| Fact (where they differ) | MapTiler Cloud | NextBillion.ai |
| --- | --- | --- |
| Vendor | MapTiler AG | NextBillion.ai Pte. Ltd. |
| Hosted endpoint | no (local only) | `https://mcp.nextbillion.io` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Paid |
| Tools exposed | none | 27 |
| Read-only variant documented | no | yes |
| Last release | 2026-10-02 | 2026-10-30 |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 115k npm/wk | none |

Why the edge:
- Transparency & trust, MapTiler Cloud +22: MapTiler Cloud 80 (Editorial half only. Closed service with general and Cloud-specific terms under Swiss law, and SDKs under BSD 3-Clause and the skill under MIT (20). The privacy policy covers account and payment data and says legal-claim data is kept up to 10 years, but says nothing about how long API request logs are kept (15). A dated deprecation page for v3 maps and migration guides, with no written notice period (12). Hosting with OVHcloud and Google Firebase, data mainly in Switzerland and the EEA, and an EU-only endpoint. Google Analytics, Firebase and FastSpring named in the privacy policy (17). 20+15+12+17 = 64.); NextBillion.ai 58 (Editorial half only. Closed service under terms that name NextBillion.ai Pte. Ltd. and Singapore law, and an Apache-2.0 MCP server (18). The privacy policy keeps personal data while a legitimate business need exists, with no periods given. The MCP README says only tool arguments are sent to the API and nothing is retained between requests (14). No deprecation policy or dated notices found. The terms promise 10 days' notice of material changes to the terms (3). Data is mainly processed in Singapore, with transfers abroad under standard clauses. No sub-processor list found (8). 18+14+3+8 = 43.)
- Payments & pricing, MapTiler Cloud +20: MapTiler Cloud 40 (No x402, MPP or L402 (0). Per-1,000 prices for requests ($0.15) and sessions ($2.50) public without login (20). Free plan with no card, though only for testing and non-commercial use (20). Signup is a browser flow (0). 0+20+20+0 = 40.); 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.)
- Security & auth, MapTiler Cloud +18: MapTiler Cloud 64 (Revocable keys that can be limited to origins and a User-Agent substring and managed by the API keys API, and service tokens that sign requests so the token itself never travels, which earns 27. Less 10 because the key is 'always passed as a query parameter' (17). The public APIs are read-only, and account changes need a separate service token (16). Geocoding returns OpenStreetMap names and addresses, community-edited text, with no prompt-injection guidance (7). An Analytics API and account usage statistics (8). security.txt, a vulnerability disclosure policy and ISO/IEC 27001:2022 certification per the security page. No bug bounty found (16). 17+16+7+8+16 = 64.); NextBillion.ai 46 (The REST APIs take a single `key` query parameter, so a plain key that travels in URLs, which earns 20 less 10. The MCP server adds OAuth 2.1 with PKCE, seals the key into tokens with AES-256-GCM, accepts a Bearer header and stores nothing server-side, so 5 back (15). Every tool is read-only, and keys can carry an IP allowlist (12). Places results are POI and address text with no prompt-injection guidance (7). Usage alerts at 50, 75 and 90 per cent of credits, per the pricing FAQ. No per-call log found (5). /.well-known/security.txt returns 404, and we found no disclosure policy or bug bounty. The about page says the company follows ISO 27001 standards, without naming a certificate (7). 15+12+7+5+7 = 46.)
- Agent ergonomics, NextBillion.ai +7: MapTiler Cloud 70 (API reading. limit, types, bbox, proximity, country, language and fuzzyMatch size geocoding results, and the batch endpoint takes up to 50 queries (20). Country, bbox and type filters, no pagination (geocoding rarely needs it) (16). Errors are documented as 400 and 403 with no recovery guidance (10). Every public API reads and is safe to retry (12). Few required parameters, but official clients are JavaScript and TypeScript only, plus native mobile SDKs (12). 20+16+10+12+12 = 70.); NextBillion.ai 77 (MCP reading, since the hosted server is the agent surface. 27 tools, four of them for documentation and seven local geometry tools, with shapes simplified to a 500-vertex budget to save context (18). limit, types, country, bbox and circle filters, and batch geocoding of up to 100 queries (16). The error table explains each code, and the MCP masks the key in error text (15). Every API tool is marked readOnlyHint, idempotentHint and not destructive in the source (18). Few required parameters and explicit latitude and longitude objects, but no official server-side SDK, only mobile and web map SDKs (10). 18+16+15+18+10 = 77.)
- Schema & documentation, MapTiler Cloud +6: MapTiler Cloud 79 (OpenAPI 3.1.0 document with 32 paths for the public APIs (25). llms.txt, llms-full.txt and a Markdown twin of every page (10). Each API page says what it's for and when to use the SDK instead (session billing), with little on when not to call it (13). Parameters are typed with defaults, such as limit (default 5 forward, 1 reverse) and a types enum, but bbox and proximity are strings (11). Examples on every endpoint, and the spec documents 400, 403, 404 and 414, without an error reference page (10). A dated platform updates page and a geocoding index changelog, but no version in the API path and the spec is version '1.0' (10). 25+10+13+11+10+10 = 79.); 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.)