⬡ fencemaker
DocsPricing Control Tower
CAPABILITY 04 · THE ENGINE UNDERNEATH

Geofencing

Check whether a coordinate falls inside any registered geofence — instantly. This is the territory engine that GPS Ingestion, Trips, and Action Engine are all built on top of.

Coordinate in{{lat, lng}}Point-in-Polygon engineMatched fence IDs+ metadata
SERVER-SIDE · PURE REST · UNDER 10MS

Point-in-Polygon API

Send a coordinate, get back matched fence IDs and metadata. Under 10ms latency, server-side, pure REST — no SDK, no client library, no polling.

Coordinate-in-polygon or circle checks
Multi-fence matching in a single call
Real-time response, under 10ms
Batch endpoint — up to 30,000 coordinates per call on Premium
Query by fence ID or tag
Typical uses
Delivery zone validation at checkoutDark-store radius checksGeo-risk underwriting lookupsField-visit verification
ENDPOINT
POST /v1/pip

Each call — or each coordinate tested in a batch call — counts as one PiP check against your plan's daily limit.