AuthorizationstringrequiredheaderRequired Bearer API key. Programmatic access to the World API needs a key; browsing nosible.world in a browser does not.
Example: Bearer nos_sk_...
Text to Geo (Batch)
Geocode a batch of texts and return predictions for each text, in input order.
How to use this endpoint
guidanceAvailable only in V2.0-preview. Send texts in one request. The response uses the same schema, model, and results envelope as ticker and NER batch APIs. Each result preserves its exact input text and contains geographic predictions, in input order. A text with no matches keeps its position with an empty predictions array. Invalid requests or failed upstream responses return an error; they are never silently replaced with empty results. Split larger workloads into bounded batches.
Response body
application/jsonThese are the fields you can build against. Nested names use dot notation; optional sections are called out in their descriptions.
schemastringStable response schema shared with the other text model endpoints.
Example: nosible_model_classification_v1
modelstringPinned geography tagger engine revision.
Example: NOSIBLE/geo-tagger-v2.0-preview@revision:c9fe46347e5422548c0e0780ddbc6252284619a1
resultsobject[]One result per input text, in input order.
Example: [{ text, predictions: [...] }, { text, predictions: [] }]
results[].textstringThe exact input text, preserved without trimming.
Example: A concert took place at Newlands Stadium in Cape Town, South Africa.
results[].predictionsobject[]Resolved geographic locations. An empty array is a successful no-match result.
Example: [{ continent, region, country, lat, lng, source, matched_on, entity_type }]
results[].predictions[].continentstring | nullContinent containing the resolved place, when known.
Example: Africa
results[].predictions[].regionstring | nullState or province associated with the resolved place, when known.
Example: null
results[].predictions[].countrystring | nullCountry containing the resolved place, when known.
Example: South Africa
results[].predictions[].latnumberRepresentative latitude in decimal degrees, from −90 to 90.
Example: -29
results[].predictions[].lngnumberRepresentative longitude in decimal degrees, from −180 to 180.
Example: 24
results[].predictions[].sourcestringLocation source. Text matching and supported graph associations use ner; the World location schema also supports llm.
Example: ner
results[].predictions[].matched_onstringThe text or supporting entity matched to this location.
Example: South Africa
results[].predictions[].entity_typestring (optional)Type of the supporting named entity, when available.
Example: GPE
Responses and errors
HTTP200Request succeeded. The response body is shown in the panel on the right.
400
invalid_json — Request body is not valid UTF-8 JSON.401
api_key_required / invalid_api_key — A valid NOSIBLE bearer API key is required.408
request_timeout — Request body did not finish within 5 seconds.413
request_too_large — JSON request body exceeds the endpoint's byte limit.422
validation_error — Text is missing, blank, too long, or contains unsupported request fields; a batch must also satisfy the item and total-text limits.429
rate_limited / model_rate_limited — Caller or upstream rate limit exceeded. Respect Retry-After when present.502
model_invalid_response — The geocoder returned an invalid location or an incomplete batch. This is distinct from a successful empty predictions array.502
model_upstream_error / model_upstream_unreachable — The geocoder rejected the request or could not be reached.503
model_not_configured — The geocoder is not configured for this deployment.503
api_key_auth_not_configured / api_key_auth_unavailable / api_key_metering_unavailable — Authentication or quota metering is temporarily unavailable.504
model_upstream_timeout — The geocoder did not respond within 10 seconds. No automatic retries are made.404
not_found — Ticker and Geo tagging are unavailable in V1.2. Use the /api/v2.0-preview/models/ routes.