SER™ API
Spatial Evidence Resolution for messy real-world location input. SER™ turns ambiguous human location language into structured, auditable spatial evidence.
What SER™ is
SER™ is not commodity geocoding. It is a spatial evidence product for operational language: the kind of text, voice-note transcription, route clue, landmark reference, road fragment, or incident report that normal geocoders often flatten into one fragile coordinate.
The public API endpoint is intentionally simple for developers:
https://travelsafepilot.com/api/v1/ser
The response is built to preserve evidence, confidence, ambiguity, and traceability instead of pretending every query has one clean answer.
Developer path
1. Choose a SER™ API plan.
2. Create a TravelSafePilot API key.
3. Call the public SER™ endpoint.
4. Read candidates, confidence, SHA-256 audit fields, and explanation.
Messy location understanding
SER™ handles partial reports, intersections, landmarks, roundabouts, traffic circles, road names, route markers, and incident-style language instead of expecting perfect addresses.
Candidate-aware evidence
Responses can include ranked candidates, a selected decision, alternatives, confidence bands, ambiguity flags, match types, GIDs, and human-readable explanations.
Cryptographic audit trail
Returned candidates carry SHA-256 evidence keys. Responses and logs can carry SHA-256 integrity hashes so the decision path can be tied back to the software version and query-time evidence.
Built for high-stakes review
SER™ is designed for insurance, emergency response, logistics, safety operations, and risk platforms where a hidden best-guess coordinate is not good enough.
SER™ capabilities
Roundabouts and traffic-circle interpretation
Road, intersection, landmark, and route-marker evidence
Messy incident-style language and partial human descriptions
Ranked candidates with selected decision role
Confidence bands, ambiguity flags, and score spread
Geometry class and context labels where available
Global operation with country hints as evidence, not hardcoded bias
Audit fields
Unique GID for each selected or returned candidate where available
Candidate-level SHA-256 key for every returned candidate
Response SHA-256 to bind the public payload
Log SHA-256 to prove the stored audit record was not silently altered
Software-version trace showing which SER™ engine version performed the query
Human explanation for operational and commercial review
Example public response shape
{
"ok": true,
"product": "SER",
"version": "v1",
"query": {
"raw": "magic roundabout swindon",
"country_hint": "gb"
},
"top_candidate": {
"rank": 1,
"decision_role": "selected",
"gid": "2bc1a25c-cfe6-541d-a208-a9ba5919b6e5",
"candidate_sha256": "a4661d5c61b28181169521c27e4e01f0a474e6e94b66e34c1888e91d2429e355",
"software_version": "ser-v1",
"score": {
"band": "very_high",
"ambiguous": false
},
"explain_human": "Candidates found - high confidence match"
},
"audit": {
"response_sha256": "example-response-hash",
"log_sha256": "example-log-integrity-hash",
"software_version": "ser-v1"
}
}The exact response may vary by request and entitlement. The important point is that SER™ returns spatial evidence and audit identifiers, not just an unreviewable coordinate.
Who SER™ is for
Insurance claims and location consistency review
Emergency caller-location clarification
Fleet and logistics incident normalization
Risk platform and safety intelligence enrichment
Developer products that need explainable spatial decisions
Partner systems that need audit-grade evidence rather than opaque coordinates
Read next
Developer implementation belongs in the docs. Commercial and technical context belongs in the white paper.