Aidbase API

Name: Aidbase API API
Brand: Aidbase API
Availability: InStock

★ Only Publicly Available SpecCRMCustomer Supportbearer42 EndpointsREST

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.

Quickstart

Get started with Aidbase API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"ingest a website into a knowledge base"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Aidbase API 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 API

Explore with Jentic

View OpenAPI Spec

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.

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.

Use Cases

Patterns agents use Aidbase API 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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Aidbase Bearer token is stored encrypted in the Jentic vault. Agents call /knowledge, /chatbots, and /tickets endpoints through Jentic without ever seeing the raw token.

Intent-based discovery

Agents search 'ingest a website into a knowledge base' and Jentic returns /knowledge/website with its source URL schema, ready to execute alongside the matching /knowledge/{id}/finalize call.

Time to first call

Direct integration: 2-3 days for Bearer auth, multi-source ingestion handling, and finalize step coordination. Through Jentic: under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Aidbase API

Earlier published Aidbase surface with a different base path and apiKey scheme

Pick the aidbase.ai variant if you already use its base URL and apiKey-with-Bearer-prefix scheme; pick this aidbase variant for the broader knowledge ingestion surface.

Alternative

Intercom API

Customer messaging and support platform

Choose Intercom for richer customer messaging, segmentation, and outbound campaigns alongside support.

Alternative

Zendesk API

Mature help-desk with tickets, users, and macros

Pick Zendesk when you need a mature help-desk with strong reporting and a large integration ecosystem.

FAQs

Specific to using Aidbase API 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 at https://app.jentic.com/sign-up.

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. Sign up at https://app.jentic.com/sign-up.