> ## Documentation Index
> Fetch the complete documentation index at: https://docs-attestly.code4source.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Make your first compliance check in under a minute.

## 1. Get an API key

API keys are issued per Organization on contract.
[Request access](https://attestly.code4source.com/contact) 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

```bash theme={null}
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

```bash theme={null}
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

<CardGroup cols={2}>
  <Card title="How it works" icon="diagram-project" href="/concepts/how-it-works">
    Geometry → sources → checks → verdict.
  </Card>

  <Card title="Author your own ruleset" icon="pen" href="/authoring/ruleset-basics">
    Encode your compliance policy in JSON.
  </Card>
</CardGroup>