Clearance checks consent, do-not-call lists, the recipient's local calling hours and your AI disclosure against a policy you control, and keeps a tamper-evident record of every decision. One HTTP call before you dial.
Not legal advice. Clearance applies the rules you configure. The shipped policy is a conservative starting point that your lawyer must review. It does not make any call legal and does not protect you from liability.
+1 212 555 0123
10:00 New York · written consent · AI disclosed
+1 310 555 0123
07:00 Los Angeles · outside_calling_window
+1 605 555 0123
Denver 07:30 / Central 08:30 · must fit every zone
"Hi, this is Ava from Acme Dental"
ai_disclosure_missing
In February 2024 the FCC ruled that AI-generated voices count as "artificial" voices under the TCPA. Outbound AI calls in the US need prior express consent, and written consent for telemarketing. Your dialer has to know which numbers have it, and whether it was revoked.
The EU AI Act's Article 50 transparency obligations apply from 2 August 2026: people must be told they are talking to an AI. Builders running voice agents bring up the TCPA and the AI Act in public threads. A prompt edit can quietly remove the disclosure from your greeting.
Calling hours are in the recipient's local time. Some prefixes span several time zones (parts of the US, Spanish mobiles: Madrid and the Canaries). And when someone asks "why did you call me?", you need a record nobody could have edited afterwards.
Teams whose AI agents dial out to people who did not call first.
Check consent, do-not-call lists, local calling hours and AI disclosure before each call.
Block risky calls automatically and keep a signed record of why each call was allowed.
Rules as a versioned policy, so you can show what was checked and when. Not legal advice.
Import consent records (with the text the person saw), your internal opt-outs and a national DNC file you obtain yourself. Stored in SQLite on your machine.
POST /v0/check with the number, purpose and greeting. You get allowed, each reason, the rule it came from and the recipient's local time.
Every decision, consent and opt-out goes into a hash-chained log. clearance verify-log spots edits; clearance proof <number> shows the full history.
# install and run the demo (fixed clock, fictional numbers) pip install -e '.[dev]' && clearance demo clearance serve # before your agent dials curl -X POST localhost:8787/v0/check -d '{ "to_number": "+13105550123", "purpose": "telemarketing", "greeting_text": "Hi, this is Ava, a virtual assistant from Acme." }' { "allowed": false, "reasons": [{ "code": "outside_calling_window", "severity": "block", "message": "... America/Los_Angeles Fri 07:00.", "rule_source": "TCPA, 47 CFR 64.1200(c)(1) ... Verify with a lawyer." }], "recipient_local_time": "2026-11-06T07:00-08:00", "disclaimer": "Technical check against your configured policy. Not legal advice." }
Snippets for LiveKit outbound SIP, Twilio and TypeScript are in examples/.
Self-hosted, Apache-2.0. Your data stays on your server.
$99/month minimum. For agencies starting outbound campaigns.
Up to 500k checks per month.
The hosted version is not live yet. Prices may change before launch.
Tell us what you call for (sales, collections, appointments) and where (US, EU).
We only use your email to contact you about this. Privacy.