POST/verify
Raw device verification
Send one JPEG plus challenge data. The endpoint computes the expected solar position from lat, lng, and UTC time, then checks whether the device capture matches the claimed coordinate.
25 credits
Bwendi Verify is a device location verification layer. We use solar math and camera-captured evidence to test whether a device was actually at the claimed coordinate. It is built for agent check-ins, field verification, compliance workflows, and anti-spoofing pipelines.
Verify a claimed device location with one capture, signed challenge data, and a clear pass, fail, or inconclusive verdict backed by computed solar position. The hosted turnkey flow is currently billed at 400 credits.
Use the raw endpoint if you already control the capture flow. Use the challenge flow if you want Bwendi to handle the mobile verification journey and return a final result to your backend. The hosted flow currently costs 400 credits end to end.
Send one JPEG plus challenge data. The endpoint computes the expected solar position from lat, lng, and UTC time, then checks whether the device capture matches the claimed coordinate.
Your backend creates a short-lived challenge using lat and lng. That signature prevents a client from silently changing the claimed coordinate before upload, and it is the single billable step for the hosted turnkey flow.
When you use the turnkey flow, redirect the user to verify.bwendi.com, then poll the result endpoint until the verification completes.
The verification stack starts from a fixed physical truth, then uses capture analysis to see whether the device evidence matches that truth. That makes it materially harder to spoof than a simple GPS claim.
For any latitude, longitude, and UTC timestamp, the sun position is fixed. That gives you a hard physical baseline before any model interpretation begins.
The captured image is inspected for shadow length, direction, outdoor lighting, and artificial-light artifacts. It is not just "is this image real?" but "does this device capture match this place and time?"
All user-facing coordinate inputs now use lat and lng consistently. That keeps verify aligned with the rest of the Bwendi API surface.
The observed shadows are consistent with the claimed coordinate and timestamp. Use this when you need a strong, machine-readable check before continuing a workflow.
The solar evidence contradicts the claim. Typical causes are spoofed GPS, replayed media, or a photo taken in a materially different place or time.
Indoor scenes, heavy cloud cover, weak shadows, or ambiguous lighting can prevent a confident decision. The system tells you that explicitly instead of fabricating certainty.
Use Verify for field operations, merchant onboarding, compliance spot-checks, delivery handoffs, and any workflow where a coordinate claim needs stronger evidence than device GPS alone.