Install Jentic One Beta

Connect the BotNotice API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BotNotice API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbotnotice.app%2Fbotnotice" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbotnotice.app%2Fbotnotice" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with BotNotice API.

Check whether an AI phone call may be placed to a number before dialing

Record and revoke a person's consent to receive AI calls

Store a tamper-evident receipt and opening disclosure for each AI call

Scan any website for chat tools, voice agents, and an existing AI notice

GET STARTED

Start building with BotNotice API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use BotNotice API for, with concrete tasks.

★ Agent-Gated AI Call Consent Check

An AI voice agent connected to the BotNotice API can confirm it is allowed to call a number before it dials. The agent sends the number to the consent-check endpoint, reads back whether consent is on record, and fetches the voice policy that states the disclosure the call must open with, so the dialer only proceeds for numbers that have agreed and always leads with the required notice.

Call the consent-check endpoint for a phone number, and if consent is on record, fetch the voice policy and return the opening disclosure the agent must read

Website AI Chat Disclosure Audit

Before launching a chatbot, a team can scan its own or a competitor's site with the BotNotice API to detect chat tools, voice agents, and whether an AI notice is already present. The scan endpoint needs no key, so an agent can audit many sites in sequence and report which ones are missing the 'you are talking to AI' disclosure that several jurisdictions now require.

Run the scan endpoint against a list of website URLs and return which sites have no AI disclosure notice present

AI Disclosure Law Lookup

Compliance and legal teams need to know which AI disclosure rules apply where. The BotNotice API serves a maintained dataset of tracked AI disclosure laws, including pending bills, as JSON or CSV, and a single law can be pulled in full by its slug. An agent can use this to answer which jurisdictions require a chatbot or voice-call disclosure without maintaining its own legal register.

Fetch the AI disclosure law dataset and return every jurisdiction whose rules cover automated phone calls

Call Receipt and Content Provenance Records

To prove disclosure happened, the BotNotice API stores a receipt for each AI call through the voice-event endpoint and registers media through the content-ingest endpoint as it is created or uploaded. This builds a tamper-evident record a team can produce if a regulator or customer asks whether a given call opened with the required notice.

Post a voice event receipt for a completed AI call recording that the opening disclosure was played

Key Endpoints

10 endpoints — the botnotice api displays a visible 'you are talking to ai' notice beside a website's chat and keeps a tamper-evident record of every notice shown.

METHOD

PATH

DESCRIPTION

POST

/api/scan

Check a website for chat tools, voice agents, and an existing AI notice

POST

/api/consent/check

Pre-dial check whether an AI call may be placed to a number

POST

/api/consent

Record that a person agreed to receive AI calls

POST

/api/consent/revoke

Revoke consent for a number

GET

/api/voice/policy

The opening disclosure a call for this site must use

POST

/api/voice/event

Store the receipt for a completed call

POST

/api/ingest/content

GET

/datasets/ai-disclosure-laws.json

Every tracked AI disclosure law with pending bills

POST

/api/scan

Check a website for chat tools, voice agents, and an existing AI notice

POST

/api/consent/check

Pre-dial check whether an AI call may be placed to a number

POST

/api/consent

Record that a person agreed to receive AI calls

POST

/api/consent/revoke

Revoke consent for a number

GET

/api/voice/policy

The opening disclosure a call for this site must use

POST

/api/voice/event

Store the receipt for a completed call

POST

/api/ingest/content

GET

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the BotNotice API by hand means juggling two per-site bearer tokens, remembering which endpoints are open and which need a token, and threading the voice policy into your dialer. Through Jentic you install once, import BotNotice from the API Directory, store the tokens once, and your agent calls it.

Permission scoping

BotNotice carries the site in its per-site token and the phone number in the request body, so rules bound which operations your agent may call rather than which site or number. You can let it call the consent-check and voice-policy operations to verify a call before it happens without granting the consent-revoke or content-register operations.

Credential isolation

Your BotNotice tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check consent before an AI phone call' or 'scan a site for an AI notice', and Jentic returns the matching BotNotice operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using BotNotice API through Jentic.

What authentication does the BotNotice API use?

The BotNotice API uses per-site bearer tokens per its OpenAPI spec: a voice token (starting with bni_) for the consent and voice endpoints and a content-register token for the content-ingest endpoint, both issued from the dashboard. The free site scan and the AI-disclosure law dataset need no key. Through Jentic each token is stored once by your own self-hosted instance and injected at call time, so it never sits in your agent's prompt or logs.

Is there a BotNotice MCP server?

You do not need an MCP server to give your agent the BotNotice API. Jentic connects it directly from the API Directory: import it, store your site token once, and your agent calls the consent, voice, and scan endpoints on demand. Operations are discovered when needed, so no extra server's tool definitions are loaded into the agent's context.

Can I limit what my agent is allowed to do with the BotNotice API?

Yes. Write a rule that allows only the consent-check and voice-policy operations, so the agent can confirm a number may be called and read the required opening disclosure, but cannot record or revoke consent or register content. Every call it makes is logged, so you can audit exactly what the agent touched.

Can I check consent before an AI phone call with the BotNotice API?

Yes. Send the phone number to the pre-dial check at /api/consent/check and it returns whether that number has consent on record, which lets a voice agent decide to proceed or stop. You record consent with /api/consent, revoke it with /api/consent/revoke, and read the mandatory opening line for the site from /api/voice/policy.

What are the rate limits for the BotNotice API?

The OpenAPI spec does not specify rate limits for the BotNotice API. Check the documentation and dashboard at https://botnotice.app for current limits and plan allowances before running an agent at volume.

How do I check call consent with the BotNotice API through Jentic?

Search Jentic for 'check consent before an AI phone call' and it returns the POST /api/consent/check operation with its input schema. Pass the phone number and the agent gets back whether consent is on record so it can gate the dial. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Botnotice App BotNotice API

AI ReadinessAI-Aware (B)63/100

See full scorecard

Official vendor OpenAPI document · agent-readySecurityCompliancebearer10 EndpointsREST

For Agents

Check and record consent before AI phone calls, show an AI-disclosure notice on a website's chat, store a receipt per call, and register content provenance. Includes a free site scan and a dataset of AI disclosure laws.

Use for: Check whether I can legally place an AI phone call to this number, Record that a customer consented to receive AI calls, Revoke a customer's consent after they asked to stop, Scan a website to see if it already shows an AI disclosure notice

Not supported: Does not place phone calls, send messages, or provide legal advice. Use for AI disclosure notices, call-consent records, and content provenance only.

The BotNotice API displays a visible 'you are talking to AI' notice beside a website's chat and keeps a tamper-evident record of every notice shown. It checks consent before an AI phone call is placed, records and revokes that consent per number, and stores a receipt for each call alongside the opening disclosure the call must use. A free scan endpoint inspects any site for chat tools, voice agents, and an existing notice, and a maintained dataset tracks AI disclosure laws and pending bills by jurisdiction.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

45%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

25%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the BotNotice API to your agent

Capabilities

Start building with BotNotice API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Botnotice App BotNotice API

Jentic AI Readiness Score

BotNotice API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness