Geocoding APIs you can pay per call

What geocoding APIs do

A geocoding API connects a place description with coordinates. Forward geocoding takes a name or address and returns a geographic match; reverse geocoding starts with coordinates and describes the surrounding place. Nearby search asks a different question: which named places or points of interest lie around that position? A route calculation uses locations to estimate a journey rather than to establish the identity of an address.

An agent can use these calls when planning a visit, attaching a location to a customer record or finding services near a meeting. The first decision is the output your next step consumes. A latitude and longitude can place a marker, but do not prove that a package can be delivered. A named business can help a traveler, but does not establish that the submitted street address is complete. Keep the original input beside the selected match so a later reviewer can distinguish what was typed from what the provider inferred.

Pay-per-call access fits an occasional lookup inside a larger workflow. A caller requests the documented resource, inspects the HTTP 402 payment terms and pays for that request. The payment mechanism does not change geographic ambiguity. A place name shared by different cities still needs country or regional context, and a coordinate near a boundary may describe a different administrative area from the one a user expected.

For a batch, define when an input is accepted, sent for review or rejected. A provider can return a plausible point at a city center when a caller expected a building. Store any precision or match-level field the response actually supplies. If that field is absent, avoid inventing a rooftop-quality label from the number of decimal places in the coordinate.

Which outputs the documented endpoints provide

Forward and reverse lookup belong in separate result types. Place search may return a collection of candidates; nearby search depends on the chosen center and radius. Routes and matrices describe travel between positions. They are included as adjacent geographic products when the endpoint explicitly documents them, with their own prices rather than the quote for address lookup.

An IP location describes a network address, a wallet lookup describes a blockchain account, and a bank routing number describes payment infrastructure. None establishes a postal location merely because the description contains “address” or “routing.” Weather at a city and property records at an address can consume a location without returning geocoding. Endpoint selection excludes those products from the geography table.

Each price is the cheapest endpoint of that service for that kind of data: the same number wherever this page quotes it.

Check the provider's declared coverage for the specific route. A coordinate input alone is not a worldwide coverage statement. A source label such as OpenStreetMap identifies the advertised dataset; it does not prove address freshness, uniform completeness or permission for a particular downstream use. Preserve the source attribution required by the provider and inspect its terms before storing or redistributing results.

Compare 8 geocoding services

One row per service, ordered by observed paying wallets. The quote belongs to the endpoint named in that row. Primary data types determine the row quote when available; adjacent products keep their own type prices below.

$/CALL is the price of the endpoint named under it: the cheapest forward address or locality coordinates endpoint of the service or, for a service without one, its cheapest geocoding endpoint. Never the cheapest tool of a gateway. Other kinds of data have their own price in the tables below. GEOCODING ENDPOINTS counts the geocoding endpoints out of all the endpoints the service lists. BUYERS 30D counts distinct wallets that paid the whole service on-chain in 30 days, not only its geocoding endpoints. "Generalist" marks a gateway that sells more than three unrelated kinds of tools: it is never called the cheapest.

How to choose a geocoding endpoint

Resolve ambiguity before choosing a point

Send the country, region and postal context that the endpoint accepts. Compare a complete address, a shortened address and an ambiguous place name. Decide whether the caller can ask the user to choose a candidate or must stop when a unique match is unavailable. A silent first-result policy can turn a successful lookup into the wrong destination.

Keep coordinate conventions explicit

Confirm latitude versus longitude order, the coordinate reference system and any distance unit. Test the same known landmark through forward and reverse calls, then inspect the returned components rather than demanding a byte-identical address string. A reverse lookup can describe the closest mapped feature without proving that the input lies at that feature's entrance. A route needs a travel mode and practical endpoint locations, not merely points with sufficient numeric precision.

Decide what counts as validation

A normalized address, a point on a map and a delivery confirmation solve different tasks. Before accepting a record, specify required country and postal fields and whether a missing unit number requires review. Record both the provider's match and your acceptance rule. This makes later changes auditable without presenting a geometric match as a deliverability guarantee.

Match the request to the output

Start with one representative input and a written acceptance criterion. A successful HTTP status is not enough: inspect the fields your application needs, the distinction between missing and negative results, and the provenance supplied with the response. Keep a small reviewed evaluation set that includes ambiguous inputs as well as straightforward examples. Changing a request parameter can change the product and its payment requirement, so preserve those parameters alongside the endpoint name.

Check the operating evidence

The table reports service monitoring, with a median uptime of 100% and a median selected endpoint price of $0.0075. Monitoring latency describes our checks, rather than a benchmark of a complete paid workflow. A request that triggers a larger job may have a different duration. Compare a provider's documented limits with the concurrency, timeout and result size your caller can handle. Record errors separately from empty answers so an outage does not look like a meaningful absence.

Plan changes and retries

Cache according to the provider's terms and the freshness your task needs. Keep a versioned record of input normalization and response mapping so a later provider change can be investigated. Before an automatic retry, decide whether the previous request could have completed and whether repeating it incurs another charge. An agent should have a request budget and an explicit stopping condition, especially when one answer causes follow-up calls. Validate required fields before submitting a payment rather than discovering an invalid input through a long retry loop.

Choose by the job your caller needs to complete

Start with the result your next step can consume. The candidates below come from the same data-type classification as the comparison table. The displayed job quote is the lowest matching type price for that job, with its source endpoint retained.

Forward address or locality coordinates

Compare the documented input, returned fields and paid unit for this output. Preserve ambiguity and missing-result states in the caller.

Candidates today, most buyers first: IPIntel.ai Satellite & GeoRisk API ($0.002/call, 25 buyers) · API Acre ($0.002/call, generalist, 20 buyers) · Datakoot ($0.01/call, generalist, 7 buyers) · x402-tools / Open Claw Productions diagnostics ($0.005/call, 3 buyers)

Reverse lookup: addresses or nearby populated places

Compare the documented input, returned fields and paid unit for this output. Preserve ambiguity and missing-result states in the caller.

Candidates today, most buyers first: IPIntel.ai Satellite & GeoRisk API ($0.002/call, 25 buyers) · API Acre ($0.002/call, generalist, 20 buyers)

Place discovery and business profiles

Compare the documented input, returned fields and paid unit for this output. Preserve ambiguity and missing-result states in the caller.

Candidates today, most buyers first: Places & Local Business Search ($0.02/call, 38 buyers) · fetcher.sh — Twitter, TikTok, Instagram & Web Data APIs ($0.003/call, generalist, 29 buyers) · CONNSKILL Growth Services ($0.03/call, 19 buyers) · agdata ($0.0322/call, generalist, 19 buyers)

What the providers describe

The descriptions below attribute advertised behavior and limitations to the provider. They were reviewed against its public listing and endpoint descriptions captured on October 21, 2026; operating figures and prices are generated from the page model.

API Acre

API Acre describes different geographic products behind its POST routes. Forward locality lookup starts at $0.002 and uses GeoNames to rank bounded city or locality candidates by population. Its separate US address route advertises U.S. Census MAF/TIGER coordinates, normalized geography and explicit range-interpolation limits. That street-address contract differs from a city-center point. Reverse lookup costs $0.002 and ranks nearby GeoNames populated places by great-circle distance. The provider says those routes return source freshness without a request-time network call; that is a provenance and implementation claim, rather than a guarantee of rooftop precision. Keep the selected route beside the input and inspect which geographic level it returns.

3 geocoding endpoints of 74 · $0.002/call (POST /v1/data/place-geocode) · Base/SOL · uptime 30d 100% · 121 ms · 20 buyers in 30 days

Datakoot

DataKoot describes /api/geocode as a US street-address or city lookup using the U.S. Census Geocoder, at $0.01. Its other products include weather and elevation, which should not supply the address lookup quote. This is useful when the caller needs a coordinate for a US address, provided the returned match level meets the application's requirement. The source name alone does not establish building-entrance precision or international coverage. Inspect the chosen match and preserve the submitted address; a successful match to a city is a different result from a successful street-address match.

1 geocoding endpoint of 48 · $0.01/call (GET /api/geocode) · Base · uptime 30d 100% · 86 ms · 7 buyers in 30 days

IPIntel.ai Satellite & GeoRisk API

IPIntel's satellite and georisk listing separates geographic lookup from satellite imagery and hazard products. It describes forward address-to-coordinate lookup at $0.002 and reverse coordinate-to-address lookup at $0.002. The endpoint descriptions advertise worldwide inputs and normalized address components. For forward lookup, the provider mentions confidence metadata; retain it instead of deriving confidence from numeric coordinate precision. Satellite images do not replace a documented geocoding response, and a location-risk product does not validate the supplied address.

2 geocoding endpoints of 4 · $0.002/call (POST /address-to-coordinates) · Base · uptime 30d 100% · 194 ms · 25 buyers in 30 days

Places & Local Business Search

Places describes business discovery and place profiles backed by Google Maps, Apple Maps and DuckDuckGo Maps. Its place products start at $0.02. The endpoint descriptions distinguish a query-based search, nearby local search and a profile selected by a provider-specific place identifier. They advertise fields such as address, phone, website, categories, ratings and opening hours. Those fields help choose a venue; they do not prove that an arbitrary submitted postal address is deliverable. Preserve the map provider and identifier with the selected business so a later refresh can target the same product.

6 geocoding endpoints of 6 · $0.02/call (GET /apple/local) · ARB/Base/POL/SOL · uptime 30d 100% · 337 ms · 38 buyers in 30 days

x402-tools / Open Claw Productions diagnostics

The OpenClaw Productions diagnostics listing describes /api/v1/geocode as an OpenStreetMap Nominatim lookup returning latitude, longitude and a display name, at $0.005. Its endpoint quote is used directly rather than copied from the broader service description. The provider limits this route's upstream claim to Nominatim. Budget checks, denylist checks and payment diagnostics are separate tools, even when they share the host. A display name can identify the returned feature without establishing a complete structured mailing address.

1 geocoding endpoint of 24 · $0.005/call (GET /api/v1/geocode) · Base · uptime 30d 100% · 155 ms · 3 buyers in 30 days

Cost per call and at larger volumes

The median selected endpoint costs $0.0075 per call. At an unchanged request shape, 100,000 calls total $750.00. The table multiplies reference quotes so a prototype and a larger workload can be compared on the same basis.

Each service at the price of its main geocoding endpoint, the one named in the table above.

The paid unit matters. One request may return a bounded list, inspect one input, start a job or retrieve an existing result. Check that unit before multiplying a quote by your business volume. A second product, a deeper lookup or a retry can add a charge, while no-match and failure handling depend on the provider's terms. A catalog reference quote does not establish the amount for a larger batch or a changed request body.

For a production budget, measure the calls required for an accepted result. Save the endpoint, normalized request, quoted amount and outcome in the job record. This lets you distinguish a low submission price from a low effective cost. Read the payment requirement for the exact input when the provider describes variable pricing; do not substitute a gateway's cheapest unrelated tool.

What the captured 402 establishes

The catalog lists Datakoot at GET /api/geocode. The stored 402 for that resource gives its example input as POST with a JSON body containing address in extensions.bazaar.info.input; its input schema accepts POST or GET, in both cases with a JSON body that requires address. The catalog method and the captured example input disagree. That evidence does not establish the 402 of a bodyless GET, so this page does not pair a GET curl command with the captured payment terms. The service page retains the full stored response under Payment evidence; the advertised input schema is evidence to inspect, rather than a verified request trace. The catalog reference quote for this method and path is $0.01; it is not a verified quote for a different method or request body.

Read the provider's current input schema before building a request. Keep the requested resource, accepted network, asset and amount together when evaluating its challenge. Stored payment evidence does not show a tested paid answer, establish data accuracy or prove that a background job completed. Inspect the full payload on the linked service page and obtain the challenge for the exact request before authorizing payment.

How to interpret this comparison

The listing requires an online, payment-ready service, a usable description, a known price and at least 90% measured uptime over 30 days. Endpoint selection then keeps routes that describe the page's task. A candidate can match a word in its general description yet be excluded because its documented routes return a different product. These are discovery criteria rather than certification of delivered output.

Provider paragraphs attribute statements read in the public listing and endpoint descriptions captured on October 21, 2026. Source, scope and output claims belong to the provider. x402-list monitoring supplies the price and operating figures; it does not independently establish the correctness of the underlying dataset or a vendor's performance claims.

Buyer counts are distinct paying wallets observed for the service in the measurement window, with the coverage limits described on its service page. They do not count people or prove usage of a particular route. Endpoint prices, data-type counts and job candidates share one endpoint classification. If a service disappears, its generated candidates and token-dependent descriptions disappear with it. Open the methodology and linked service pages before deciding what that evidence means for a recurring workflow.

Questions

How to pay

Each service answers an unpaid call with HTTP 402 and its price; your agent signs a USDC payment on the listed network and retries. No API key, no account, no subscription. See what x402 is.