API host · not the product site

This is the API endpoint, not the website.

api.euqlid.space serves the euqlid.space geolocation API and nothing else. Product overview, pricing, signup, dashboard and the full documentation live at euqlid.space. What stays here is the machine surface below and the field reference, which carries the acceptable-use policy that governs every key issued.

api.fraud.xxx is the previous hostname for this same API. It still resolves, and every response from it carries Deprecation, Sunset and Link: rel="successor-version" headers pointing at api.euqlid.space. Migrate.

Authentication

Every billable endpoint requires a key. Send it as X-API-Key or as Authorization: Bearer. Keys are scoped, metered per call against the owning account's balance, and throttled per key — a throttled call returns 429 with Retry-After. Get a key at euqlid.space/register.

# billable: Wi-Fi APs around a coordinate
curl -s "https://api.euqlid.space/v1/aps/nearby?lat=40.7321&lon=-73.9874&radius_m=50&limit=25" \
  -H "X-API-Key: $EUQLID_KEY"

# billable (v2): sample a coordinate inside a US postal area, plus the APs around it
curl -s "https://api.euqlid.space/v2/nearby?country=US&postal_code=90210&radius_m=150&limit=25" \
  -H "X-API-Key: $EUQLID_KEY"

# unbilled, no key: coverage and data provenance
curl -s https://api.euqlid.space/v2/geo/countries
curl -s https://api.euqlid.space/v2/geo/sources

The interactive schema browser (/docs, /redoc, /openapi.json) is not exposed on the public internet. Endpoint documentation is at euqlid.space/help and /help.

Endpoint index

Endpoint	Billing	What it returns
POST /v1/verify	billable	A resolved fix from the BSSIDs a device reports observing, with confidence, spread and accuracy band.
GET /v1/nearby	billable	APs around a coordinate. `radius_m` 10–5000.
GET /v1/aps/nearby	billable	Strict nearby lookup by `lat`+`lon` or `zip`, with optional altitude filter. `radius_m` capped at 100.
POST /v1/aps/lookup	billable	Batch BSSID lookup with full stored and enriched fields.
GET /v1/aps/{bssid}	billable	One AP record by BSSID.
GET /v2/geo/random-point	billable	A coordinate sampled from inside a US postal area, drawn over the Wi-Fi APs observed there. `count` 1–10, `precision` 4–7.
GET /v2/nearby	billable	The sampled postal origin and the APs around it. Response is a strict superset of `/v1/aps/nearby`.
GET /v2/geo/countries	free · no auth	Which countries the postal endpoints serve, and the postal format for each.
GET /v2/geo/sources	free · no auth	Geometry sources, vintages, licences, attribution and the sampling method.

Every /v2 response, including errors, carries X-API-Version: v2.

What the v2 postal coordinate is — and is not

It is area-level, not address-level. The coordinate is drawn from the access points observed inside the postal area and then displaced within a disc, so it never resolves to one building.
It is United States only — the 50 states, DC, and the USPS-served territories (PR, VI, GU, AS, MP). Any other country returns 404 unsupported_country.
It is not evidence that anyone was there. A sampled coordinate and a nearby-network result describe an area's radio environment, not a person.
Each response reports the rung it came from (method) and its provenance, so a degraded answer is visible instead of silent.

Full method, limits and error catalogue: /help#v2-postal.

Use of this API is governed by the acceptable-use policy. In short: do not use it to locate, track or identify a person or household, do not use it to misrepresent physical presence or evade controls, and do not treat any output as sole evidence in a high-impact decision. Violations may result in throttling, suspension or key revocation.