Build on Enakt.

A brief returns as data — every figure carrying the document it was proven against, plus an explicit list of what couldn't be proven.

Not a developer? Start with Solutions.

Start over REST

Creating an engagement returns 202 Accepted immediately; poll it for the result. Every request carries your key in an X-API-Key header.

shell · rest

curl -X POST https://api.enakt.live/api/v1/intelligence \
  -H "X-API-Key: $ENAKT_API_KEY" \
  -d '{"target_name": "Apple Inc.", "target_ticker": "AAPL"}'

# → 202 Accepted, with an engagement_id. Poll it:
curl https://api.enakt.live/api/v1/intelligence/$ID \
  -H "X-API-Key: $ENAKT_API_KEY"

Full endpoint and schema reference is at api.enakt.live/docs.

Get a key

Create one in the dashboard under Settings → API keys. Keys are stored hashed and scoped to your account. Sign in with Google to mint a trial account.

Read the result

Every claim comes back in exactly one of three states:

verified — Proven against a primary source, at a cited locator.
sourced — Quoted from a named filing item — read, not proven.
gap — Not disclosed, or not confirmable — returned with the item to pull.

A sourced finding never counts as verified, at any layer — enforced by a parity test in CI, not by convention.

The Python SDK

shell

pip install enakt

Not on PyPI yet — the package is built and tested but unpublished. Ask us for a wheel, or use the REST API above.

python

from enakt import Enakt

client = Enakt()
brief = client.briefs.run("Apple Inc.", ticker="AAPL")

print(brief.counts())
# {'verified': 61, 'flagged': 2, 'gap': 1}

Webhooks for async runs, a CLI, and exports to PDF, DOCX, and Sheets are all documented in the full reference below.

Full reference

How verification is measured, and what it does and doesn't cover yet, is on the Reliability page.