The main compliance endpoint. Send a geometry (and/or a typed identifier) plus a ruleset, get back a structured verdict with per-check evidence.Documentation Index
Fetch the complete documentation index at: https://code4source.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Request
| Field | Required | Notes |
|---|---|---|
input.geometry | yes¹ | GeoJSON Polygon, MultiPolygon, or Point. |
input.scheme | yes¹ | Typed identifier {type, value} for subject-register checks. |
input.crs | no | Source CRS (e.g. EPSG:31983). Default: EPSG:4326. |
ruleset_id | yes² | name@version for a pinned version, or name for the latest. |
ruleset | yes² | Inline ruleset document. |
geometry or scheme is required.
² Exactly one of ruleset_id / ruleset.
Response
Two distinct fields
status— execution health:okif every check ran cleanly,degradedif any source or check could not be evaluated.outcome— compliance result:compliant,warning,non_compliant, ordegraded.
status: ok with outcome: non_compliant (clean evaluation, policy violated). A status: degraded is incomplete — treat with caution and consider retrying.
See Verdicts for the full semantics.
Idempotency
PassIdempotency-Key: <unique-string> to make the call safely
retryable. The first response is replayed for matching keys; key
collisions with different bodies are rejected.
Output formats
- Default: JSON.
Accept: application/geo+json— return a GeoJSON FeatureCollection of evidence features.