Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / AI/ML / AISTA API
AISTA API logo

AISTA API

★ Only Publicly Available OpenAPI DocumentAI/MLLanguage ModelsapiKey6 EndpointsREST

For Agents

Create and manage custom-trained chatbots, then upload training data or scrape a website to ground them. Useful for an agent that builds vertical assistants on demand.

Use for: Create a new chatbot trained on my product docs, List all chatbots on my AISTA account, Upload a training file to chatbot {id}, Scrape https://docs.example.com and use the content as training data

Not supported: Does not host raw LLM completions, vector databases, or analytics dashboards — use for chatbot creation and training only.

Jentic publishes the only available OpenAPI specification for AISTA API, keeping it validated and agent-ready. AISTA is a chatbot creation and management platform that lets developers spin up ChatGPT-style assistants trained on custom data. The 6-endpoint API covers chatbot listing, creation, retrieval, deletion, and two training paths — uploading training data directly or scraping a website to harvest source content. Authentication uses an X-API-Key header.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the AISTA API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AISTA 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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 AISTA API.

Create new chatbots with a custom configuration

List existing chatbots scoped to the API key

Retrieve a chatbot's metadata and current training state

Delete chatbots that are no longer needed

Upload structured training data to a specific chatbot

Trigger a website scrape that ingests pages as training material

Use Cases

Patterns agents use AISTA API for, with concrete tasks.

★ Custom support assistant from a docs site

Stand up a customer-support chatbot grounded in a product's public documentation. Create the chatbot via POST /chatbots, then call POST /chatbots/{id}/scrape to ingest a docs URL — AISTA crawls and indexes the pages so the bot answers from real product content.

POST /chatbots to create 'docs-bot', then POST /chatbots/{id}/scrape with url=https://docs.example.com

Programmatic bot fleet management

Run a catalogue of chatbots — one per customer or one per product line — and manage their lifecycle from a back-office tool. The API exposes list, get, and delete so an internal admin agent can audit and clean up bots without using the AISTA dashboard.

Call GET /chatbots, identify any chatbot whose name starts with 'test-', and DELETE each via /chatbots/{id}

AI agent integration via Jentic

Allow an orchestration agent to provision bots on demand — for example, when a new customer signs up, the agent searches Jentic for chatbot creation, calls AISTA to create the bot, and uploads onboarding training data, all without holding the X-API-Key.

Search Jentic for 'create a chatbot trained on uploaded data', load the AISTA POST /chatbots and POST /chatbots/{id}/training operations, and execute

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/chatbots

Create a new chatbot

GET

/chatbots

List chatbots on the account

GET

/chatbots/{id}

Get a chatbot's configuration

DELETE

/chatbots/{id}

Delete a chatbot

POST

/chatbots/{id}/training

Upload training data

POST

/chatbots/{id}/scrape

Scrape a website for training

POST

/chatbots

Create a new chatbot

GET

/chatbots

List chatbots on the account

GET

/chatbots/{id}

Get a chatbot's configuration

DELETE

/chatbots/{id}

Delete a chatbot

POST

/chatbots/{id}/training

Upload training data

POST

/chatbots/{id}/scrape

Scrape a website for training

Why Jentic?

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

Credential management

Credential isolation

AISTA X-API-Key tokens are stored encrypted in the Jentic vault. Agents receive scoped execution capabilities — the raw key never enters the agent's prompt or memory.

Intent-based discovery

Intent-based discovery

Agents search by intent (e.g., 'create a chatbot trained on a website') and Jentic returns the AISTA /chatbots and /scrape operations with their schemas so the agent calls them in sequence.

Time to first call

Time to first call

Direct AISTA integration: a day to wire auth, training uploads, and scrape polling. Through Jentic: well under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

CustomGPT

→

Build custom-trained chatbots from documents and websites with a comparable feature set.

Pick CustomGPT for a more mature product with broader content sources; pick AISTA when you want a lightweight chatbot platform for ChatGPT-style bots.

Alternative

Chatbot.com

→

Visual chatbot builder with conversation flow design.

Use Chatbot.com when you need scripted dialogue flows; use AISTA when an LLM-grounded answer over custom data is enough.

Complementary

OpenAI API

→

Use OpenAI directly for raw LLM completions outside the AISTA chatbot wrapper.

Pair OpenAI with AISTA when an agent needs both a managed support bot (AISTA) and ad-hoc LLM calls (OpenAI).

FAQs

Specific to using AISTA API through Jentic.

Why is there no official OpenAPI spec for AISTA API?

AISTA does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AISTA 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 AISTA API use?

AISTA uses an API key passed in the X-API-Key header. Through Jentic the key is stored encrypted in the Jentic vault and injected at execution time, so it never appears in agent code or prompts.

Can I train an AISTA chatbot from a website URL?

Yes. Call POST /chatbots/{id}/scrape with the target URL — AISTA will crawl the site and index the content as training material. For structured uploads, POST /chatbots/{id}/training accepts training files directly.

How do I create a chatbot through Jentic?

Use the Jentic search query 'create a chatbot trained on custom data'. Jentic returns the POST /chatbots operation; supply the chatbot config, then chain into POST /chatbots/{id}/training or /scrape to load content.

Are there rate limits for AISTA?

Rate limits are not declared in the OpenAPI spec; usage is governed by your AISTA plan. Spread bulk training uploads over time and watch for 429 responses on rapid scrape requests.

GET STARTED

Start building with AISTA API

Explore with Jentic
View OpenAPI Document