Official vendor OpenAPI document · agent-readyCommunicationsChat Messagingbearer7 EndpointsREST
For Agents
Send prompts to a trained ChatNode chat agent, read its conversation history and session IDs, and verify an API key through the ChatNode API.
Use for: Send a prompt to my trained chat agent, Get the chat history for a bot, List the conversation IDs for my agent, Retrieve the session details captured by my bot
Not supported: Does not handle chatbot training, document uploads, or voice calls. Use for querying trained ChatNode agents and reading their conversations only.
The ChatNode API sends queries to your trained chat agents and returns their responses, with each agent addressed by its bot identifier. It lists the conversation and session IDs recorded for a bot, retrieves the messages exchanged with users, and verifies an API key. The endpoints are scoped to interacting with an already-trained agent rather than building one.
Install Jentic One Beta
Connect the ChatNode API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ChatNode 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fchatnode.ai%2Fchatnode" | sh2
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%2Fchatnode.ai%2Fchatnode" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 ChatNode API.
Send a query or prompt to a trained chat agent by its bot identifier
Retrieve the messages and conversations exchanged with a bot
List the conversation and session IDs recorded for a bot
Verify that an API key is valid
Use Cases
Patterns agents use ChatNode API for, with concrete tasks.
★ AI Agent Query Relay
An AI agent connected through Jentic can route a user's question to a trained ChatNode agent and return its answer. The orchestrating agent passes the bot identifier and prompt, and ChatNode responds from the agent it already trained, so the workflow adds conversational answers without hosting a model itself.
Send a user's question to a trained agent by its bot identifier and return the agent's answer
Conversation History Retrieval
Review past interactions by retrieving the messages and conversations recorded for a bot. ChatNode returns the exchange history so a workflow can summarize sessions or audit what the agent told users.
Retrieve the recent messages and conversations for a bot and summarize the main topics
Lead and Session Export
Feed downstream systems by listing the conversation and session IDs a bot has recorded, each tied to its captured lead. ChatNode exposes these identifiers so an integration can pull sessions for CRM or analytics.
List the conversation and session IDs for a bot and export them for downstream processing
Key Endpoints
7 endpoints — the chatnode api sends queries to your trained chat agents and returns their responses, with each agent addressed by its bot identifier.
METHOD
PATH
DESCRIPTION
POST
/{bot_id}
Send a query to a trained agent
POST
/get-chats/{bot_id}
Get messages and conversations for a bot
POST
/get-conversation-ids/{bot_id}
List conversation and session IDs
GET
/auth_me
Check the validity of an API key
POST
/{bot_id}
Send a query to a trained agent
POST
/get-chats/{bot_id}
Get messages and conversations for a bot
POST
/get-conversation-ids/{bot_id}
List conversation and session IDs
GET
/auth_me
Check the validity of an API key
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
O
OpenAPI Plant Store
- Non-Ready (F)35/100
100
Foundational Compliance68
Developer Experience & Jentic Compatibility13
AI-Readiness & Agent Experience94
Agent Usability60
Security59
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
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).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
68
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
25%
Example Density
How richly the API is illustrated with examples.
95%
Example Validity
Percentage of examples that conform to their schemas.
50%
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.
13
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
51%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
60
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).
59
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
59%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ChatNode by hand means handling its bearer-token auth and tracking the bot-query, conversation, and session paths yourself. Through Jentic you install once, import ChatNode from the API Directory, store the token once, and your agent calls it.
Permission scoping
The ChatNode surface is query and read operations, so a rule can allow your agent to query a bot and read its conversations and nothing more. You choose which operations it may call, so anything you leave out stays unavailable.
Credential isolation
Your ChatNode 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 'query a chat agent' or 'read conversation history', and Jentic returns the matching ChatNode operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ChatNode API through Jentic.
What authentication does the ChatNode API use?
The ChatNode API authenticates with a bearer token sent in the Authorization header, per its OpenAPI spec, and it offers an API-key check operation so you can confirm a key is valid. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never appears in the agent's prompt or logs.
Can I query a trained agent with the ChatNode API?
Yes. You send a query or prompt to a trained agent by its bot identifier and receive the agent's response. The API is scoped to interacting with an agent you have already trained, not to building or retraining one.
Can I read conversation history with the ChatNode API?
Yes. The API retrieves the messages and conversations recorded for a bot and lists the conversation and session IDs it has captured. This lets a workflow summarize sessions or export leads to another system.
Is there a ChatNode MCP server?
You do not need an MCP server to give your agent the ChatNode API. Jentic connects it directly from the API Directory: import ChatNode, store your token once, and your agent queries bots and reads conversations through the operations the API already exposes. Operations are discovered on demand, so no extra tool definitions are loaded into the agent's context.
Can I limit what my agent is allowed to do with the ChatNode API?
Yes. Write a rule that allows only the operations the agent needs, for example sending a query and reading conversations, so you expose just the bot interactions you intend. The agent works within those bounds, and every call it makes is logged.
How do I query a bot through Jentic with the ChatNode API?
Search Jentic for 'query a chat agent', which returns the ChatNode operation with its input schema, then supply the bot identifier and prompt and the agent runs it. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED