Install Jentic One Beta

Connect the Aidbase API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Aidbase 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%2Faidbase%2Faidbase" | 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%2Faidbase%2Faidbase" | 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 Aidbase API.

Ingest knowledge from a website URL, video, uploaded document, or FAQ entry through the /knowledge endpoints

Finalize a document-based knowledge item with /knowledge/{id}/finalize once upload completes

Inspect knowledge sub-pages and FAQ items derived from an ingested source

Manage chatbots, their bindings, and their conversations across the chatbot endpoints

GET STARTED

Start building with Aidbase API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Aidbase API for, with concrete tasks.

★ Multi-Source Knowledge Ingestion

Build a knowledge base that draws from a help-centre website, a set of how-to videos, a few PDF manuals, and a hand-written FAQ. Use POST /knowledge/website, /knowledge/video, /knowledge/document, and /knowledge/faq with /knowledge/{id}/finalize to wrap up document uploads. The result is a unified knowledge surface a chatbot can answer from.

POST /knowledge/website with the help-centre URL, then POST /knowledge/document for each PDF and call /knowledge/{id}/finalize once each upload completes

Self-Serve Support Chatbot

Stand up a self-serve chatbot that answers from the ingested knowledge. The chatbot endpoints let you create the bot, bind it to knowledge, and send chat messages. Combined with sub-pages and FAQ items derived from sources, the bot can cite the original article that produced its answer.

Create a chatbot bound to the knowledge items ingested above, then send the customer's question to its chat endpoint and capture the cited sources

Custom Ticket Forms with Email Intake

Combine ticket forms and email inboxes so customers can submit structured tickets via a form or simply reply to a support email. Tickets are listed and updated through the /tickets endpoints, and email inboxes route inbound mail into the same pipeline.

Create a ticket form, register an email inbox, and configure the inbox to route inbound mail into the form to create tickets

Operational Knowledge Audit

Periodically audit which knowledge items power the chatbot by listing /knowledge, then drilling into /knowledge/{id}/sub-pages and /knowledge/{id}/faq-items. Items that no longer match the live product can be deleted via DELETE /knowledge/{id} so the chatbot stops citing stale content.

GET /knowledge, then for each item GET /knowledge/{id}/sub-pages and decide whether to keep or DELETE the item

Agent-Driven Support via Jentic

An AI agent automates support: ingest a new help article, retrain knowledge, and triage incoming tickets. Through Jentic the agent finds the right Aidbase operation by intent, the Bearer token is supplied from the vault, and the agent never sees the raw token.

Use Jentic search 'ingest a website into a knowledge base', execute /knowledge/website, then list /tickets and post a draft reply on each

Key Endpoints

42 endpoints — jentic publishes the only available openapi specification for aidbase api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/knowledge

List all knowledge items

POST

/knowledge/website

Ingest a website as a knowledge source

POST

/knowledge/document

Create a document knowledge item

POST

/knowledge/{id}/finalize

Finalize a document knowledge upload

POST

/knowledge/faq

Create an FAQ knowledge item

GET

/knowledge/{id}/sub-pages

List sub-pages derived from a knowledge source

GET

/knowledge/{id}/faq-items

List FAQ items derived from a knowledge source

GET

/knowledge

List all knowledge items

POST

/knowledge/website

Ingest a website as a knowledge source

POST

/knowledge/document

Create a document knowledge item

POST

/knowledge/{id}/finalize

Finalize a document knowledge upload

POST

/knowledge/faq

Create an FAQ knowledge item

GET

/knowledge/{id}/sub-pages

List sub-pages derived from a knowledge source

GET

/knowledge/{id}/faq-items

List FAQ items derived from a knowledge source

Why Jentic?

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

Setup

Wiring Aidbase by hand means handling its bearer token, sequencing ingestion calls like /knowledge/website then /knowledge/{id}/finalize, and writing your own retry logic. Through Jentic you install once, import Aidbase from the API Directory, store the token once, and your agent calls it.

Permission scoping

Aidbase puts the knowledge source id in the URL path (/knowledge/{id}/finalize, /knowledge/{id}/sub-pages), so a rule can pin your agent to one knowledge source. You choose the operations it may call, so ingesting a website or document is only included if you add it.

Credential isolation

Your Aidbase bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'ingest a website into a knowledge base', and Jentic returns the Aidbase /knowledge/website operation with its source URL schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Aidbase API through Jentic.

Why is there no official OpenAPI spec for Aidbase API?

Aidbase does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Aidbase API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Aidbase API use?

HTTP Bearer authentication. The Bearer token goes in the Authorization header. Through Jentic the token is held in the vault and never enters the agent's context.

Can I ingest a website into a knowledge base?

Yes. POST /knowledge/website with the source URL. Aidbase crawls the page tree, and you can later inspect the resulting sub-pages via GET /knowledge/{id}/sub-pages.

How do I upload a PDF as a knowledge document?

POST /knowledge/document to create the document, upload the file, then call POST /knowledge/{id}/finalize to mark ingestion complete and make the document available to chatbots.

What are the rate limits for the Aidbase API?

The spec does not declare explicit rate limits. Use list endpoints with reasonable page sizes when iterating over knowledge or tickets, and respect HTTP error codes returned by the server.

How do I drive Aidbase from Jentic?

Run pip install jentic, search 'ingest a website into a knowledge base', execute /knowledge/website, and chain in /knowledge/{id}/finalize for any document uploads. Run it through Jentic One, the self-hosted execution layer.

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

Yes. Because you run Jentic One yourself, your own rules decide which Aidbase operations and credentials the agent may use, so you can allow read-only calls like GET /knowledge and GET /knowledge/{id}/sub-pages while withholding ingestion operations such as POST /knowledge/website or POST /knowledge/document. Aidbase also carries the knowledge source id in the URL path (/knowledge/{id}/finalize, /knowledge/{id}/sub-pages), which lets a rule pin the agent to a single knowledge source. The agent can only call the operations you have explicitly permitted, and the bearer token stays with your own instance rather than the agent's context.

Aidbase API

Name: Aidbase API
Brand: Aidbase API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticCRMCustomer Supportbearer42 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Ingest knowledge from websites, videos, documents, and FAQs, manage chatbots and ticket forms, and triage tickets and email inboxes through a Bearer-authenticated REST surface.

Use for: I need to ingest a help-centre website into a knowledge base, Upload a PDF as a knowledge document and finalize it, Add an FAQ entry to a knowledge item, List all knowledge items I have ingested

Not supported: Does not handle outbound marketing, voice channels, or general CRM contact management - use for AI knowledge ingestion, support chatbots, and ticketing only.

Jentic publishes the only available OpenAPI specification for Aidbase API, keeping it validated and agent-ready. Aidbase is an AI-powered customer-support platform that helps businesses enhance self-serve and automate support. This spec covers a richer surface than the public Aidbase v1 - knowledge management with website, video, document, and FAQ ingestion, chatbots, ticket forms, tickets, and email inboxes. Authentication uses HTTP Bearer tokens. The base URL is https://api.aidbase.ai/v1.

Jentic One on Github View OpenAPI Document

Connect the Aidbase API to your agent

Capabilities

Start building with Aidbase API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Aidbase API