AISTA API

Name: AISTA API
Brand: AISTA API
Availability: InStock

★ 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.

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.

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

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

GET STARTED

Start building with AISTA API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

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

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

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

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

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.

AISTA API

Connect the AISTA API to your agent

Capabilities

Start building with AISTA API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs