# NextBillion.ai

> NextBillion.ai is a Singapore mapping and routing platform for fleets and logistics. Its REST APIs cover directions, distance matrices, route optimisation, navigation, geocoding and places, with a hosted MCP server for agents.

- Canonical: https://www.anchorterminal.com/tools/nextbillion
- Pricing: https://www.anchorterminal.com/tools/nextbillion#pricing
- Reviews: https://www.anchorterminal.com/tools/nextbillion#reviews
- Markdown: https://www.anchorterminal.com/tools/nextbillion.md (~8,350 tokens)
- Slim: https://www.anchorterminal.com/tools/nextbillion.min.md (~1,680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/nextbillion.json (this page as data, same URL with Accept: application/json)
- 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 nextbillion.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

## Overview

**Grade C · 55.4/100 · rank #869 of 1486 · #15 in Maps, geocoding & places · not agent-ready · confidence medium**


## Assessment

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.

## Facts

| Field | Value |
| --- | --- |
| Vendor | NextBillion.ai Pte. Ltd. (https://nextbillion.ai) |
| Kind | HTTP API |
| Category | Maps, geocoding & places (https://www.anchorterminal.com/categories/maps) |
| Transport | HTTP, Streamable HTTP |
| Endpoint | `https://mcp.nextbillion.io` |
| Auth | OAuth or key · REST APIs take a 32-character key as the `key` query parameter, issued in the console at console.nextbillion.ai or by emailing support. Keys can carry an IP allowlist. The hosted MCP server is its own OAuth 2.1 authorisation server with PKCE: a sign-in page asks for the key once and seals it into the tokens. Scripts can send the key as a Bearer header to the MCP server instead. |
| Pricing | Paid (Paid) · By quote. Annual licences priced per order, per asset or per API call, paid monthly or yearly, with extra usage at a rate set in the plan. A 7-day free trial with an API key and no credit card. |
| x402 | No · No x402, MPP or L402 in the docs, llms.txt, the MCP server source or the pricing page (checked 2026-11-06). Contracts are invoiced. |
| Licence | unknown |
| Tools exposed | 27 |
| Source | https://github.com/nextbillion-ai/nextbillion-mcp |
| Docs | https://docs.nextbillion.ai/ |
| llms.txt | https://docs.nextbillion.ai/llms.txt |
| Last release | 2026-10-30 |
| Surface listed | The REST APIs at api.nextbillion.io and the hosted MCP server at mcp.nextbillion.io, read from docs.nextbillion.ai (llms.txt and Markdown pages), nextbillion.ai (pricing, trial, terms, privacy, about), the nextbillion-mcp repository and the MCP server's OAuth metadata on 6 November 2026. No account was made, no key was used and no MCP session was opened |
| APIs | Directions, Distance Matrix (sync and async), Navigation, Isochrone, Snap to Roads, Hours of Service, Route Report, Batch Routing, Route Optimization, Driver Assignment, Clustering, Forward, Reverse, Structured, Batch and Postcode Geocode, Autocomplete, Autosuggest, Discover, Browse, Place Lookup, tracking and geofencing APIs, maps and static images |
| MCP tools | autocomplete, autosuggest, directions, distance_matrix, geocode_batch, geocode_forward, geocode_reverse, geocode_structured, isochrone, place_browse, place_lookup, place_search, postcode_lookup, search_along_route, static_map_image, static_route_map, four documentation tools and seven local geometry tools |
| Rate limits | 2,400 queries a minute, or 40 a second, for continuous requests. 429 when the per-minute rate or the request quota is reached |
| SDKs | Android, iOS, Flutter and React Native navigation, maps and tracking SDKs and a web maps SDK. No official server-side client found |
| Pricing model | Three bundles (Basic, Advanced and Bespoke Route Planning) priced per order, asset or API call on annual licences, by quote |
| Ownership | Founded in 2020 by Ajay Bulusu, Gaurav Bubna and Shaolin Zheng, and part of Velocitor Solutions of Charlotte, North Carolina, since 2025 |
| Legal entity | NextBillion.ai Pte. Ltd., Singapore, under Singapore law |
| Capabilities | geo.routing, geo.geocode, geo.reverse, geo.places, geo.tiles |
| Tags | hosted, mcp, remote-mcp, oauth, api-key, llms-txt, official, sales-led, annual-contract, free-trial, no-card, enterprise, android, ios, closed-source |
| JSON | https://www.anchorterminal.com/api/v1/tools/nextbillion.json |

## Score breakdown (methodology v0.7, October 2026 research run)

Assessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points.

| Category | Weight | This run | Score (0–100) | Points |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 20 | 45 | 9.0 |
| Performance | 10% | pending | pending | n/a |
| Schema & documentation | 13% | 16.2 | 73 | 11.9 |
| Agent ergonomics | 13% | 16.2 | 77 | 12.5 |
| Security & auth | 14% | 17.5 | 46 | 8.1 |
| Payments & pricing | 10% | 12.5 | 20 | 2.5 |
| Task success | 10% | pending | pending | n/a |
| Maintenance & community | 7% | 8.8 | 73 | 6.4 |
| Transparency & trust (editorial 43, provenance 73) | 7% | 8.8 | 58 | 5.1 |
| Negative events | up to −15 | up to −15 | none recorded | 0 |
| **Total** | | | | **55.4 → C** |

### Why each score

- Reliability 45 (checked 2026-11-06): 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.
- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.
- Schema & documentation 73 (checked 2026-11-06): 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.
- Agent ergonomics 77 (checked 2026-11-06): 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.
- Security & auth 46 (checked 2026-11-06): 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.
- Payments & pricing 20 (checked 2026-11-06): 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.
- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.
- Maintenance & community 73 (checked 2026-11-06): 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.
- Transparency & trust 58 (checked 2026-11-06): 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.

Fix list, everything this grade says the listing lacks, the biggest gain first (16 items). What it covers is at https://www.anchorterminal.com/fixes/nextbillion.md (JSON https://www.anchorterminal.com/fixes/nextbillion.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "nextbillion", "plan": "read"}`, free while the beta runs

### What we couldn't check

- unchecked: incident history on status.nextbillion.io, which renders only in a browser
- unchecked: whether the 7-day trial key is issued instantly or after review, since the trial page doesn't say
- No OpenAPI document or API changelog was found in the docs or llms.txt
- The ISO 27001 statement on the about page doesn't say whether NextBillion.ai holds the certificate

### Sources

- docs llms.txt: <https://docs.nextbillion.ai/llms.txt> (seen 2026-11-06)
- site llms.txt: <https://nextbillion.ai/llms.txt> (seen 2026-11-06)
- Forward Geocode API reference: <https://docs.nextbillion.ai/md/places/geocoding/forward-api.md> (seen 2026-11-06)
- MCP server repository and changelog: <https://github.com/nextbillion-ai/nextbillion-mcp> (seen 2026-11-06)
- MCP protected resource metadata: <https://mcp.nextbillion.io/.well-known/oauth-protected-resource> (seen 2026-11-06)
- pricing: <https://nextbillion.ai/pricing> (seen 2026-11-06)
- trial page: <https://nextbillion.ai/start-trial> (seen 2026-11-06)
- terms of service: <https://nextbillion.ai/terms-of-service> (seen 2026-11-06)
- privacy policy: <https://nextbillion.ai/privacy> (seen 2026-11-06)
- about page: <https://nextbillion.ai/about-us> (seen 2026-11-06)
- status page: <https://status.nextbillion.io/> (seen 2026-11-06)

## Score history

Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/nextbillion/history.json

- 2026-11-06: graded 55.4 C (methodology 0.7)

## Who's behind it (provenance 73/100, checked 2026-11-06)

| Check | Finding | Points |
| --- | --- | --- |
| Legal entity named | NextBillion.ai Pte. Ltd. | 20/20 |
| Domain age | nextbillion.ai, registered 2019-08-07 (7 years) | 11/15 |
| Endpoint on the vendor's domain | mcp.nextbillion.io is not on nextbillion.ai | 0/15 |
| Terms of service | read, states 6 of the 7 things a reader expects | 9.1/10 |
| Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 |
| Status page | status.nextbillion.io | 10/10 |
| Changelog | published | 10/10 |
| security.txt | not found | 0/10 |
| People named | 3 named with their role, 3 with a public profile | 10/10 |
| Support route | a support address, help pages | 5/5 |

The terms name NextBillion.ai Pte. Ltd. and choose Singapore law, with mediation first. The privacy policy names Nextbillion.AI Pte. Ltd. and its affiliates.

The APIs and MCP server run on nextbillion.io, a second domain of the same company, while the site and docs are on nextbillion.ai.

nextbillion.ai/.well-known/security.txt and /security return 404. No vulnerability disclosure policy was found.

The changelog listed is the MCP server's; no changelog for the REST APIs was found.

RDAP gives nextbillion.ai a registration date of 7 August 2019. robots.txt on nextbillion.ai and docs.nextbillion.ai allows these pages, and docs robots.txt allows /llms*.txt.

The acceptable use clause bars reselling or making the services available to third parties. No clause on automated access to the website was found.

### Terms and privacy, as read

A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.

**Terms of service** (https://nextbillion.ai/terms-of-service), read 2026-11-06, gives no date, states 6 of the 7 things a reader expects.

- To know. Says access can be ended without notice or for any reason. "Further, NextBillion also reserves the right to terminate Your Account and/or use of the Services at any time by providing thirty (30) days written notice due to business reasons which shall include discontinuation of the Services."
- Not found in the text. Gives the date it was last updated.
- Names the governing law or courts. The law of Singapore.
- States a limit on its liability. Capped at the fees paid in the 12 months before the claim.
- Says how changes to the terms are announced. Gives ten days of notice before a change.

**Privacy policy** (https://nextbillion.ai/privacy), read 2026-11-06, gives no date, states 6 of the 8 things a reader expects.

- Not found in the text. Gives the date it was last updated.
- Not found in the text. Says whether personal data is sold or shared for advertising.
- Says where data is transferred or stored. Relies on standard contractual clauses.

## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade)

### Key people

- Gaurav Bubna, Co-founder. LinkedIn: https://www.linkedin.com/in/gauravbubna/. X: https://x.com/bubnagaurav
- Ajay Bulusu, Co-founder. LinkedIn: https://www.linkedin.com/in/ajaybulusu/. X: https://x.com/ajaybulls
- Shaolin Zheng, Co-founder. LinkedIn: https://www.linkedin.com/in/shaolin-zheng/
- Note: NextBillion.ai's about page, read on 6 November 2026, names Gaurav Bubna, Ajay Bulusu and Shaolin Zheng as co-founders, who met on Grab's Geo team in 2017 and launched the company in 2020, and links each one's LinkedIn and two of their X accounts. The same page names four investors (Lightspeed, Alpha Wave Global, M12 and Mirae Asset Capital) behind $34.25 million raised. NextBillion.ai's own post of 1 October 2025 says Velocitor Solutions, of Charlotte, North Carolina, completed the full acquisition of the company, and gives no price, so no valuation is set. Its post of 23 May 2022 announces a $21 million Series B led by Mirae Asset Capital, with FounderBank Capital and CSVE Ventures as new investors. Gunderson Dettmer's client news of 25 June 2020 says Lightspeed India Partners co-led the Series A. News reports of the Series A, which name Falcon Edge Capital as the other co-lead and M12 as the investor in a $6.25 million extension in May 2021, are on Inc42 and other hosts whose robots.txt shuts out Anthropic's crawlers, so they weren't used, and Alpha Wave Global and M12 keep the about page as their source without a round.
- NextBillion.ai: LinkedIn https://www.linkedin.com/company/nextbillion-ai/ X https://x.com/nextbillionai GitHub https://github.com/nextbillion-ai

### Ownership and investors

- Ownership: Acquired by Velocitor Solutions, 1 October 2025
- Raised: $34.25M in total, as of November 2026 (source https://nextbillion.ai/about-us)
- Backed by: Lightspeed Venture Partners, Alpha Wave Global, Microsoft, Mirae Asset, FounderBank Capital, CSVE Ventures

### Getting support

- Support email: support@nextbillion.ai
- Help: https://docs.nextbillion.ai/
- Sources: https://nextbillion.ai/about-us, https://nextbillion.ai/terms-of-service, https://github.com/nextbillion-ai/nextbillion-mcp, https://docs.nextbillion.ai/md/places/geocoding/forward-api.md, https://nextbillion.ai/blog/velocitor-solutions-completes-full-acquisition-of-nextbillion-ai, https://nextbillion.ai/blog/nextbillion-funding-series-b, https://www.gunder.com/en/news-insights/client-news/lightspeed-india-partners-co-leads-series-a-in-nextbillion-ai

## Live (updated 2026-11-07 17:49 UTC)

- Right now: up, HTTP 405, 395 ms, checked 2026-11-07 17:49 UTC (get on `https://mcp.nextbillion.io`)
- Uptime 24h 100.0% (195 probes) · 30 days 100.0% (195 probes) · p50 383 ms · p95 517 ms
- Vendor status page: not read, no machine-readable status found
- github `nextbillion-ai/nextbillion-mcp` v0.5.3, released 2026-10-30
- security.txt: none
- Watching changelog <https://raw.githubusercontent.com/nextbillion-ai/nextbillion-mcp/main/CHANGELOG.md>
- Watching privacy <https://nextbillion.ai/privacy>
- Watching terms <https://nextbillion.ai/terms-of-service>
- Tools it lists (27, about 17,777 tokens of context, `tools/list` without credentials over MCP 2026-07-28, checked 2026-11-07 01:46 UTC):
  - `autocomplete` (read-only): Complete a partial address or administrative-area prefix into full valid addresses (e.g. "stat" -> "State Capitol, ..."). Use for prefix completion as the user…
  - `autosuggest` (read-only): Suggest address and place candidates from an incomplete or misspelled query (typo-tolerant, e.g. "aqaurium" still matches aquariums). Use for…
  - `bbox` (read-only): The smallest latitude/longitude box around a set of points, a line or a polygon, optionally padded in metres — for example a viewport for static_map_image or a…
  - `buffer` (read-only): Build the zone within a given straight-line distance of a point (a circle), a line (a corridor, e.g. 1 km along a route) or a polygon (grown outward, or shrunk…
  - `centroid` (read-only): The area-weighted centre of a polygon and a label point that is guaranteed to lie inside it (the centroid of a C- or ring-shaped area falls outside; the label…
  - `directions` (read-only): Calculate a route between an origin and a destination with optional waypoints; returns distance (meters), duration (seconds) and an encoded polyline per route,…
  - `distance_matrix` (read-only): Compute travel distance (meters) and duration (seconds) for every origin-to-destination pair in one call; one row per origin with one element per destination,…
  - `geocode_batch` (read-only): Forward-geocode up to 100 free-text queries in one request; returns one ranked result set per query, in input order. Use it instead of repeated geocode_forward…
  - `geocode_forward` (read-only): Convert a free-text address, place name, locality or administrative area into coordinates and a full postal address; tolerates incomplete or partly wrong…
  - `geocode_reverse` (read-only): Find the nearest address for a coordinate; returns the full postal address, the matched position and a bounding box. Parameters: coordinate {latitude,…
  - `geocode_structured` (read-only): Geocode an address given as separate fields instead of one string; searches addresses and administrative areas only, never POIs. Use when the components are…
  - `get_api_parameters` (read-only): Get structured parameter details for a NextBillion REST API endpoint: type, required, default, allowed values, units and description. More precise than a prose…
  - `get_documentation` (read-only): Fetch the full text of one documentation page by its doc_id, as returned by search_documentation. Use when an excerpt is not enough to answer accurately. Pages…
  - `isochrone` (read-only): Calculate the area reachable from a point within given travel times or distances; returns a GeoJSON FeatureCollection of contours (geometry coordinates are…
  - `list_documentation_topics` (read-only): List the available documentation categories, APIs and pages, with index metadata. Useful before searching, when the right terms are not yet known, e.g. to see…
  - `measure` (read-only): Measure straight-line (geodesic, WGS84) distance between two points, the length of a line, the area and perimeter of a polygon, or the bearing from one point…
  - `nearest` (read-only): Find the candidate points nearest to a target as the crow flies (e.g. the closest depots to a customer), or snap the target onto a line and report the closest…
  - `place_browse` (read-only): List places of given categories around a location, ranked by distance, without a text query - e.g. all restaurants or schools near a point. Use place_search…
  - `place_lookup` (read-only): Fetch the full details of a place (address, position, access points, categories, contacts) by its unique id, as returned by place_search, geocode_forward,…
  - `place_search` (read-only): Search for places, points of interest and businesses with a free-text query (e.g. "gas station", "coffee"), ranked by relevance around a location. Use…
  - `points_in_polygon` (read-only): Geofencing: tell which of up to 1,000 points lie inside a polygon, for example which delivery addresses fall within an isochrone contour or a service area.…
  - `polygon_ops` (read-only): Combine polygons: union (merge), intersect (overlap) or difference (first minus the others), for example the overlap of two isochrones or the part of a zone…
  - `postcode_lookup` (read-only): Get the centroid and boundary polygon of a postal/ZIP code, or find the postal code that contains a coordinate; one lookup per call. Supported countries: USA,…
  - `search_along_route` (read-only): Find places matching a text query along a driving route, with the detour time and distance each stop adds - for "find X on the way" questions. Pass the route…
  - `search_documentation` (read-only): Search NextBillion's official API and SDK documentation. Use for any question about how NextBillion works: calling an API, what a parameter means, which API to…
  - `static_map_image` (read-only): Render a static map image centered on a location, with optional markers and line/polygon overlays; returns the image inline (path in the result text). For a…
  - `static_route_map` (read-only): Render a static map auto-fitted to a route and/or overlays: a route from directions, and/or lines and filled polygons such as isochrone contours; very long…
- How its tools read to an agent (0 errors, 6 warnings, 1 note, about 17,777 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score):
  - warn TC11 bbox: 3 parameters without a description: points, points[].latitude, points[].longitude
  - warn TC11 geocode_structured: 8 parameters without a description: city, county, house_number, neighborhood, postal_code, state and 2 more
  - warn TC13 static_map_image: paths[].geojson_coordinates[] (array with no items)
  - warn TC13 static_route_map: paths[].geojson_coordinates[] (array with no items)
  - warn TC22 directions: the definition is about 1,699 tokens
  - warn TC23 server: 27 tools, about 17,789 tokens of definitions
  - note TC24 server: 27 of 27 tools have no outputSchema
- Always current: https://www.anchorterminal.com/api/v1/live/nextbillion.json

## Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.

## Strengths

- Hosted MCP server at mcp.nextbillion.io with OAuth 2.1 and PKCE, and every API tool annotated read-only and idempotent
- Routing, distance matrix, isochrone, route optimisation, geocoding and places APIs under one key
- llms.txt, llms-full.txt and Markdown versions of the docs pages
- Documented rate limit of 2,400 queries a minute and a per-endpoint error table
- 7-day free trial with no credit card

## Weaknesses

- Pricing is by quote on annual licences, with no public unit prices
- The REST APIs take the key only as a `key` query parameter
- No OpenAPI spec or API changelog found
- No security.txt or vulnerability disclosure policy, and no SLA
- The status page renders only in a browser, so its history couldn't be read



## Before you call it (notes for agents)

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

## Connect

First request:

```bash
curl "https://api.nextbillion.io/geocode?q=market&at=40.720685,-74.044772&in=countryCode:USA&key=$NBAI_API_KEY"
```

Claude Code:

```bash
claude mcp add --transport http nextbillion https://mcp.nextbillion.io
```

MCP client configuration:

```json
{
  "mcpServers": {
    "nextbillion": {
      "url": "https://mcp.nextbillion.io"
    }
  }
}
```

Through letme: https://letme.dev/nextbillion. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md

## Similar tools

Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.

| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |
| --- | --- | --- | --- | --- | --- | --- |
| Mapbox APIs + MCP | BB | 77.2 | 35 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/mapbox.md |
| Amazon Location Service | BB | 76.5 | 43 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/amazon-location.md |
| Google Maps Platform + Grounding Lite MCP | BB | 75.4 | 63 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/google-maps-platform.md |
| Azure Maps | B | 67.1 | 338 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/azure-maps.md |
| ArcGIS Location Platform | B | 66.1 | 380 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/arcgis.md |
| Stadia Maps | B | 65.2 | 431 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/stadia-maps.md |

## Panel reviews (0)

Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .

Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md

## Notable

- Hosted MCP server at https://mcp.nextbillion.io with 27 tools (16 API tools, four documentation tools, seven local geometry tools), Apache-2.0, version 0.5.3 on 30 October 2026 (source: <https://github.com/nextbillion-ai/nextbillion-mcp>)
- The MCP server went hosted-only in version 0.4.2 on 27 October 2026, removing the local stdio mode (source: <https://github.com/nextbillion-ai/nextbillion-mcp/blob/main/CHANGELOG.md>)
- Every API tool in the MCP server carries readOnlyHint, idempotentHint and destructiveHint false (packages/server/src/tools/types.ts)
- Rate limit of 2,400 queries a minute, or 40 a second, stated in the API reference (source: <https://docs.nextbillion.ai/md/places/geocoding/forward-api.md>)
- Part of Velocitor Solutions since 2025, per the about page, after raising $34.25 million in venture capital (source: <https://nextbillion.ai/about-us>)

- #15 of 18 in 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

## Compare

- [Amazon Location Service vs NextBillion.ai](https://www.anchorterminal.com/compare/amazon-location-vs-nextbillion.md): BB 76.5 vs C 55.4
- [ArcGIS Location Platform vs NextBillion.ai](https://www.anchorterminal.com/compare/arcgis-vs-nextbillion.md): B 66.1 vs C 55.4
- [Azure Maps vs NextBillion.ai](https://www.anchorterminal.com/compare/azure-maps-vs-nextbillion.md): B 67.1 vs C 55.4
- [Geoapify Location Platform + MCP vs NextBillion.ai](https://www.anchorterminal.com/compare/geoapify-vs-nextbillion.md): C 58.1 vs C 55.4
- [Geocodio vs NextBillion.ai](https://www.anchorterminal.com/compare/geocodio-vs-nextbillion.md): BB 72.2 vs C 55.4
- [Google Maps Platform + Grounding Lite MCP vs NextBillion.ai](https://www.anchorterminal.com/compare/google-maps-platform-vs-nextbillion.md): BB 75.4 vs C 55.4
- [HERE Location Services vs NextBillion.ai](https://www.anchorterminal.com/compare/here-location-services-vs-nextbillion.md): C 58.4 vs C 55.4
- [LocationIQ vs NextBillion.ai](https://www.anchorterminal.com/compare/locationiq-vs-nextbillion.md): C 60.3 vs C 55.4
- [Mapbox APIs + MCP vs NextBillion.ai](https://www.anchorterminal.com/compare/mapbox-vs-nextbillion.md): BB 77.2 vs C 55.4
- [MapQuest vs NextBillion.ai](https://www.anchorterminal.com/compare/mapquest-vs-nextbillion.md): F 35.4 vs C 55.4
- [MapTiler Cloud vs NextBillion.ai](https://www.anchorterminal.com/compare/maptiler-vs-nextbillion.md): B 62.1 vs C 55.4
- [NextBillion.ai vs Nominatim](https://www.anchorterminal.com/compare/nextbillion-vs-nominatim.md): C 55.4 vs B 63.5
- [NextBillion.ai vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/nextbillion-vs-opencage.md): C 55.4 vs B 67.5
- [NextBillion.ai vs Radar](https://www.anchorterminal.com/compare/nextbillion-vs-radar.md): C 55.4 vs D 53.3
- [NextBillion.ai vs Stadia Maps](https://www.anchorterminal.com/compare/nextbillion-vs-stadia-maps.md): C 55.4 vs B 65.2
- [NextBillion.ai vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/nextbillion-vs-tomtom.md): C 55.4 vs E 45.9
- [NextBillion.ai vs Woosmap](https://www.anchorterminal.com/compare/nextbillion-vs-woosmap.md): C 55.4 vs C 59.4

## Verify this listing

For the vendor. The badge or a plain link to this page verifies the listing, from a page on nextbillion.ai or one of its subdomains, or the README at the root of github.com/nextbillion-ai/nextbillion-mcp. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "nextbillion", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify

HTML badge:

```html
<a href="https://www.anchorterminal.com/tools/nextbillion"><img src="https://www.anchorterminal.com/badges/nextbillion.svg" alt="NextBillion.ai on Anchor Terminal" height="20"></a>
```

Markdown badge, for a README:

```markdown
[![NextBillion.ai on Anchor Terminal](https://www.anchorterminal.com/badges/nextbillion.svg)](https://www.anchorterminal.com/tools/nextbillion)
```

Plain link:

```html
<a href="https://www.anchorterminal.com/tools/nextbillion">NextBillion.ai on Anchor Terminal</a>
```

## Share this listing

For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say NextBillion.ai is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.

- Dark: https://www.anchorterminal.com/assets/share/nextbillion-dark.png
- Light: https://www.anchorterminal.com/assets/share/nextbillion-light.png

---

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