Skip to main content

​
1. Get an API key

API keys are issued per Organization on contract. Request access if you don’t have one yet. Keys look like atk_live_.... Pass them as a Bearer token on every request.

​
2. Check what overlaps a polygon

curl -X POST https://api-attestly.code4source.com/v1/intersections \
  -H "Authorization: Bearer atk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "input": {
      "geometry": {
        "type": "Polygon",
        "coordinates": [[[-60,-3],[-60,-2],[-59,-2],[-59,-3],[-60,-3]]]
      }
    }
  }'
You get back a list of reference areas (protected areas, indigenous territories, embargoed zones, etc.) that intersect the polygon — with overlap area and ratios for each.

​
3. Run a full ruleset

curl -X POST https://api-attestly.code4source.com/v1/evaluate \
  -H "Authorization: Bearer atk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "input": {
      "geometry": { "type": "Polygon", "coordinates": [...] }
    },
    "ruleset_id": "br-bacen-cmn-5193-credito-rural@1"
  }'
The response carries:
  • status — ok or degraded (execution health).
  • outcome — compliant, warning, non_compliant, or degraded (compliance result).
  • checks[] with per-check evidence.
  • projections[] with the numeric values the ruleset computed.

​
Next steps

How it works

Geometry → sources → checks → verdict.

Author your own ruleset

Encode your compliance policy in JSON.