QUICKSTART
GET request
curl "https://travelsafepilot.com/api/v1/ser?q=magic%20roundabout%20swindon&country_hint=gb" \ -H "Authorization: Bearer YOUR_API_KEY"
SER™ API · VERSION 1
Make the first authenticated spatial-evidence request.
SER™ accepts clean or messy location language and returns ranked spatial evidence with confidence, ambiguity, alternatives, explanation, and audit fields where available.
AUTHENTICATION
Account session and API authentication are separate.
The developer console uses the signed-in TravelSafePilot account session. SER requests use the generated bearer API key. Keys are tied to the canonical account and active product entitlement.
Authorization: Bearer YOUR_API_KEY
REQUEST FORMAT
GET and POST are supported.
GET
/api/v1/ser?q=...&country_hint=gb
POST
JSON body with q or query, plus optional country_hint.
Country hints contribute evidence; they do not turn the platform into a country-hardcoded geocoder.
INTERPRETING OUTPUT
Treat ambiguity as part of the answer.
GID: traceable candidate or decision identifier
Candidate SHA-256: candidate audit identity where returned
Confidence: evidence signal, not a guarantee
Alternatives: meaningful competing interpretations
Geometry class: point, segment, corridor, area, junction, or unresolved context
Software version: engine version used for the decision
USAGE AND PRICING
Metered through the standard developer account.
The first 1,000 SER™ queries are free per governed account or billing identity. Thereafter, public reference pricing is USD $1.50 or ZAR R30 per 1,000 queries. Enterprise fair-use access is available from USD $1,499 or ZAR R30,000 monthly.
Requests are authenticated, entitlement-checked, classified, metered, and logged without plaintext API-key exposure.
ERRORS AND RECOVERY
Fail safely and never treat an error as a location decision.
200 · Governed response returned
The response may still contain ambiguity, alternatives, weak confidence, or unresolved evidence.
400 · Malformed request
The query is missing, invalid, or does not match the supported request shape.
401 · Missing or invalid API key
Add the bearer header or rotate the key from the developer console.
403 · SER access not active
The account or key is recognised, but the required SER entitlement is not active.
429 · Rate or usage control reached
Back off and review the active account, usage, and commercial state.
5xx · Transient service failure
Retry safely. Never treat an error payload as a valid spatial decision.