# SuVerse Freight — GPS Trip Telematics Analytics

> SuVerse Freight — GPS Trip Telematics Analytics is a paid API for AI agents from api.suverse.io, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Analyzes a sequence of GPS pings from a freight trip to compute distance, duration, fuel consumption, cost, and driving efficiency metrics.

## Facts

- Endpoint: POST https://api.suverse.io/v1/freight/trip_telematics
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/suverse-freight-gps-trip-telematics-analytics-ec6b2ba0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_z5kJAlK018OiKe5Jwnasi

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability suverse-freight-gps-trip-telematics-analytics-ec6b2ba0 -d '<json body>'
```

Example prompt: Analyze this truck trip's GPS log for me — here are 45 pings with lat/lon, speed, timestamp, and fuel rate in GPH. Use a fuel price of $3.85 per gallon and an assumed 6.5 MPG, and give me the full trip summary including distance, duration, fuel burned, and total fuel cost.

## When to prefer this

Choose this endpoint when you have raw GPS telemetry data (lat/lon/speed/timestamp/fuel rate) from a freight trip and need computed analytics like distance, fuel cost, and efficiency — especially within a freight operations or fleet management workflow already using the SuVerse Freight platform. Prefer this over manual calculations or generic mapping APIs when fuel economics are central to the output.

## Known failure modes

- Empty or single-ping array returns insufficient data error
- Missing or malformed timestamp fields cause processing failure
- Unrealistic speed or fuel rate values may produce skewed results
- Missing fuel_price or assumed_mpg falls back to defaults or returns partial metrics
- Pings out of chronological order may cause incorrect duration/distance calculations

## How this service works

SuVerse Freight — GPS trip analytics (freight.trip_telematics)

## Output

Returns a structured telematics summary for the trip, including total distance traveled, trip duration, average and max speed, total fuel consumed, estimated fuel cost, and efficiency metrics derived from the GPS ping sequence and fuel parameters provided.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "pings": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "lat": {
      "type": "number"
     },
     "lon": {
      "type": "number"
     },
     "speed": {
      "type": "number"
     },
     "timestamp": {
      "type": "string"
     },
     "fuelRateGph": {
      "type": "number"
     }
    }
   }
  },
  "options": {
   "type": "object",
   "properties": {
    "fuel_price": {
     "type": "number"
    },
    "assumed_mpg": {
     "type": "number"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/suverse-freight-gps-trip-telematics-analytics-ec6b2ba0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.suverse.io](https://www.zero.xyz/host/api.suverse.io/llms.txt)