Skip to main content
Audact
See the offer

API · Multi-regulation

One engine. A policy pack per regime.

Public API host: In development

POST https://api.audact.ai/v1/policy/evaluate

The public API host. The code examples document the intended interface and the endpoints used within the current product.

No public API is served on this host yet, apart from the published Merkle roots at /v1/metachain. The endpoints used inside the product are not the same thing as a public API.

Why this status
Claim
In development · By application
Scope
The public API host. The code examples document the intended interface and the endpoints used within the current product.
Ground
No public API is served on this host yet, apart from the published Merkle roots at /v1/metachain. The endpoints used inside the product are not the same thing as a public API.
What it does not establish
That any individual endpoint works today. That is confirmed per endpoint, and the confirmation is open.
What you can get today
Production access sits inside an applicable paid agreement. Endpoints are not priced separately.
Last checked
5 October 2026
Where to check it
/apis

Germany: national policy layer active. Netherlands: in development. Belgium and Austria: planned.

Regimes differ; the machinery underneath does not. You enable a policy pack per country and per regime, and every decision it makes writes into the same evidence chain. An auditor asking about the AI Act and an auditor asking about consent get one export rather than two systems. Switching a pack on is a configuration change, not a release.

POST /v1/policy/evaluate

curl -X POST https://api.audact.ai/v1/policy/evaluate \
  -H "Authorization: Bearer $AUDACT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jurisdiction": "DE",
    "packs": ["aia-50", "gdpr", "uwg-outbound"],
    "channel": "voice",
    "action": "outbound_dial",
    "context": { "consent_reference": "consent_8h2k9d7" }
  }'

Packs compose. Enabling a second one does not change how the first behaves.

200 OK · one verdict, per-pack reasons

{
  "verdict": "ALLOW",
  "conditions": [
    { "pack": "aia-50", "requires": "spoken_disclosure_before_first_turn" },
    { "pack": "uwg-outbound", "requires": "opt_out_offer_before_close" }
  ],
  "pack_versions": {
    "aia-50": "2026.08.02",
    "gdpr": "2026.05.01",
    "uwg-outbound": "2026.07.01"
  },
  "call_id": "7f3c2a1e-0000-4000-8000-000000000000"
}

The dates that already passed

The transparency duties of Article 50 apply. It is a transparency duty, not a prohibition.
Regulation (EU) 2024/1689, Art. 50 · applicable since 2 August 2026
Unsolicited commercial communication to a natural person requires prior consent.
Telecommunicatiewet (NL), art. 11.7 · amendment in force since 1 July 2026
ICT-related incident management and reporting obligations for financial entities.
Regulation (EU) 2022/2554 (DORA), Art. 17 · applicable since 17 January 2025
Transparency obligations for online platforms, including advertising and recommender systems.
Regulation (EU) 2022/2065 (DSA) · applicable since 17 February 2024
For SMEs and start-ups the penalty ceiling under the AI Act is the lower of €15 million or 3% of worldwide annual turnover, not the higher.
Commission guidelines C(2026)5054 of 20 July 2026, point (152)

What runs on the engine

Article 50 disclosure and its attestation, per jurisdiction.
In controlled testing
GDPR: lawful basis, consent provenance, decision trail under Art. 22.
In development
Outbound eligibility under the German and Dutch rules.
In controlled testing · Germany: national policy layer active. Netherlands: in development. Belgium and Austria: planned.
One auditor export covering every pack you have enabled.
Working today
DORA, MiCA, MDR/IVDR and ISO 42001 control-evidence packs.
In development

Coverage

What the law says, and what we do about it.

What the law demands carries a source, what we build carries a status.

  • Regime
    EU AI Act, Art. 50(1)
    Source
    Reg. (EU) 2024/1689 · in force 2 Aug 2026
    What Audact does
    Disclosure in the call, recorded
    Pack status
    In controlled testing
  • Regime
    EU AI Act, Art. 50(2)
    Source
    Reg. (EU) 2024/1689
    What Audact does
    Machine-readable marking of synthetic audio
    Pack status
    Planned
  • Regime
    GDPR
    Source
    Reg. (EU) 2016/679 · Art. 6, 7, 17, 22
    What Audact does
    Consent provenance and decision trail
    Pack status
    In development
  • Regime
    NL Telecomwet
    Source
    Telecommunicatiewet art. 11.7 · since 1 Jul 2026
    What Audact does
    Outbound eligibility chain
    Pack status
    In controlled testing · Germany: national policy layer active. Netherlands: in development. Belgium and Austria: planned.
  • Regime
    UWG (DE)
    Source
    § 7(2) UWG
    What Audact does
    Consent and opt-out conditions on outbound
    Pack status
    In controlled testing
  • Regime
    DSA
    Source
    Reg. (EU) 2022/2065 · since 17 Feb 2024
    What Audact does
    Content and algorithm transparency records
    Pack status
    In development
  • Regime
    DORA
    Source
    Reg. (EU) 2022/2554 · since 17 Jan 2025
    What Audact does
    ICT incident and resilience records
    Pack status
    In development
  • Regime
    MiCA
    Source
    Reg. (EU) 2023/1114 · since 30 Dec 2024
    What Audact does
    Communications policy pack
    Pack status
    In development
  • Regime
    MDR / IVDR
    Source
    Reg. (EU) 2017/745 and 2017/746
    What Audact does
    Clinical-communication scope gating
    Pack status
    In development
  • Regime
    Product liability
    Source
    Dir. (EU) 2024/2853 · applies 9 Dec 2026
    What Audact does
    Records that show who put their name on what
    Pack status
    In development
  • Regime
    ISO 42001
    Source
    Voluntary standard, no certification claimed
    What Audact does
    Control-evidence export for your own audit
    Pack status
    In development

Why one engine

Two auditors, one export.

  • A single evidence substrate with policy-specific controls on top, not one chain that claims to satisfy every regulator.
  • Per-jurisdiction overlays: the same engine, a different pack, applied at dispatch time.
  • Product liability changes on 9 December 2026, and it is a directive: transposition runs per member state.

Questions

What does a pack status of 'in development' mean?
That we are building it and it is not available to switch on. It does not mean certified, third-party attested, or piloted with a customer.
Does one evidence chain satisfy every regulator?
No, and nobody should claim that. What it gives you is one evidence substrate with policy-specific controls on top: the plumbing is shared, the controls are per regime.
Do you hold an ISO 42001 certification?
No. The pack exports control evidence for your own management system; it is not a certification of Audact and it is not a certification of you.

Every framework, with its source

The compliance index carries one page per regime: what it requires, since when, and which article says so.

See all frameworks

Related