Detect fuel card abuse API
Flag fuel card transactions that exceed tank capacity, mismatch fuel type, duplicate within a time window, share one card across vehicles, overflow the tank without mileage burn evidence, or appear too far from the vehicle for the supplied max speed. Volumes are millilitres. Every flag includes deterministic evidence. No telematics or merchant network is queried.
The Detect fuel card abuse operation is part of the Fleet Fuel Card Controls API on BRAINIAC.software. Flag fuel card transactions that exceed tank capacity, mismatch fuel type, duplicate within a time window, share one card across vehicles, overflow the tank without mileage burn evidence, or appear too far from the vehicle for the supplied max speed. Volumes are millilitres. Every flag includes deterministic evidence. No telematics or merchant network is queried. It is exposed as POST /api/v1/fleet-operations/fuel-card-abuse-detect and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied fuel card transactions, vehicles, odometer readings, and locations processed locally Limitations: Volumes are millilitres and amounts are integer minor units. No unit conversion is invented. Mileage burn requires expected_consumption_ml_per_km and odometer readings. Consumption is never assumed. Location checks use rounded haversine meters and supplied max_speed_meters_per_hour only. No telematics, card network, or mapping API is queried. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include the other resources on the product page. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/fleet-operations/fuel-card-abuse-detectExample request
curl -i -X POST "https://www.brainiac.software/api/v1/fleet-operations/fuel-card-abuse-detect" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"duplicate_window_minutes": 120,
"vehicles": [
{
"id": "v1",
"registration": "AB12 CDE",
"fuel_type": "diesel",
"tank_capacity_ml": 60000,
"expected_consumption_ml_per_km": 80,
"max_speed_meters_per_hour": 120000
},
{
"id": "v2",
"registration": "XY99 ZZZ",
"fuel_type": "diesel",
"tank_capacity_ml": 50000
}
],
"transactions": [
{
"id": "t1",
"card_id": "card-1",
"vehicle_id": "v1",
"purchased_at": "2026-11-05T08:00:00.000Z",
"volume_ml": 40000,
"amount": 6000,
"currency": "GBP",
"fuel_type": "diesel",
"station_id": "s1",
"latitude": 51.5,
"longitude": -0.12
},
{
"id": "t2",
"card_id": "card-1",
"vehicle_id": "v1",
"purchased_at": "2026-11-05T09:00:00.000Z",
"volume_ml": 40000,
"amount": 6000,
"currency": "GBP",
"fuel_type": "diesel",
"station_id": "s1",
"latitude": 51.5,
"longitude": -0.12
},
{
"id": "t3",
"card_id": "card-1",
"vehicle_id": "v2",
"purchased_at": "2026-11-05T09:30:00.000Z",
"volume_ml": 20000,
"amount": 3000,
"currency": "GBP",
"fuel_type": "diesel",
"station_id": "s2"
},
{
"id": "t4",
"card_id": "card-2",
"vehicle_id": "v1",
"purchased_at": "2026-11-05T18:00:00.000Z",
"volume_ml": 70000,
"amount": 9000,
"currency": "GBP",
"fuel_type": "petrol",
"latitude": 52,
"longitude": 0.5
}
],
"odometer_readings": [
{
"id": "o1",
"vehicle_id": "v1",
"reading_km": 1000,
"recorded_at": "2026-11-05T07:00:00.000Z"
},
{
"id": "o2",
"vehicle_id": "v1",
"reading_km": 1005,
"recorded_at": "2026-11-05T17:00:00.000Z"
}
],
"locations": [
{
"id": "l1",
"vehicle_id": "v1",
"latitude": 51.5,
"longitude": -0.12,
"recorded_at": "2026-11-05T17:30:00.000Z"
}
]
}
JSONAn unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.
FAQ
- Do I need an API key? No. Pay the listed USDC amount with x402.
- What network? Base (eip155:8453), USDC.
- Is this an official determination? No. Results are for human review against the cited sources.