Add LTC

Developers

Consent analysis you can call.

The same engines that power the extension, as an API, an SDK, and a review tool for your own documents.

LTC API

Versioned, authenticated, rate limited. The full specification is at /openapi.json, with an interactive reference at /docs that will load no third-party script. Neither exists yet: the API is not open during Early Access. Future tense on purpose, because a link to a schema that is not there is worse than saying so.

POST /v1/analyse
Authorization: Bearer ltc_live_...

{ "event": { "siteDomain": "example.com",
             "action": "accept",
             "subjects": ["cookies_advertising"],
             "surface": "cookie_banner",
             "metrics": { ... } } }

Note what the request body does not contain. There is no field for page text or a page URL anywhere in this API — not an omission from the example, but an absence from the schema.

LTC Preflight

Review your own terms, privacy policy and subscription flow before you ship them. Preflight runs the same taxonomy against documents you supply and reports what LTC would say about them, with the passage behind each finding.

Documents you send to Preflight are analysed and discarded. They are never added to the knowledge graph, and never appear on a company page.

LTC Inside

Embed LTC in your own product — a bank warning customers before they connect a third-party app, a security suite adding consent analysis, a browser building it in. The SDK exposes detection and analysis without LTC’s consumer interface, so it fits your product rather than colonising it.

What the API will not do

  • It will not accept page content, because there is no field for it.
  • It will not return a score. It returns findings, each with the evidence behind it.
  • It will not return “low concern” for a company it has read nothing about. That case returns unverifiable, and you should render it as such.