Bindstack RAG Query API
34
AI ReadinessNon-Ready (F)34/100
Community OpenAPI document · agent-readyAI/MLEmbeddings Searchnone1 EndpointsREST
Know of an official OpenAPI document? Contribute it →
Install Jentic One Beta
Connect the Bindstack RAG Query API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bindstack RAG Query 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%2Fbindstack.ai%2Fbindstack" | 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%2Fbindstack.ai%2Fbindstack" | 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 Bindstack RAG Query API.
Run a retrieval-augmented query against a meeting's transcript
Return the most relevant transcript passages ranked by similarity score
Read the matched meeting title and total result count for a query
Use Cases
Patterns agents use Bindstack RAG Query API for, with concrete tasks.
★ AI agent transcript retrieval
An AI agent answering questions about past meetings can pull grounded context on demand. Through Jentic the agent searches by intent and calls the query endpoint, receiving ranked transcript passages with similarity scores it can cite rather than guessing from memory.
Use Jentic to search 'query a meeting transcript', call POST /v1/external/rag/query with meeting_code 'MTG-TUR7-WGK4' and query 'what did they decide about VS Code', and return the top results.
Meeting knowledge retrieval
A knowledge assistant surfaces what was said in a specific meeting without replaying the recording. The agent sends a query scoped to one meeting_code and reads the total_results count and the ranked results array to build a summary.
Call POST /v1/external/rag/query with a meeting_code and a natural-language query, then read total_results and the ranked results array.
Grounded answer assembly
When an agent must cite sources, it retrieves passages with their similarity scores and composes an answer anchored to the transcript. This keeps generated answers traceable to the meeting content that supports them.
Send a query for a meeting_code via POST /v1/external/rag/query and use the returned passages and similarity scores to compose a cited answer.
Key Endpoints
1 endpoints — the bindstack rag query api runs retrieval-augmented queries against a meeting's transcript.
METHOD
PATH
DESCRIPTION
POST
/v1/external/rag/query
Run a retrieval-augmented query against a meeting transcript
POST
/v1/external/rag/query
Run a retrieval-augmented query against a meeting transcript
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
The Bindstack RAG query endpoint declares no credential in its spec, so there is nothing to authenticate by hand. Through Jentic you install once, import Bindstack from the API Directory, and your agent calls the query endpoint with a meeting_code and query.
Permission scoping
Bindstack carries the meeting_code in the request body, so a rule bounds which operations your agent may call rather than which meeting. With one query operation on the surface, you allow that single read operation and nothing else.
Credential isolation
This endpoint requires no credential in its OpenAPI spec, so there is nothing to hold. If Bindstack later adds authentication, your own Jentic One instance keeps the secret encrypted and injects it at execution time, never in the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search a meeting transcript', and Jentic returns the Bindstack query operation with its input schema so the agent calls it with the right meeting_code and query.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Bindstack RAG Query API through Jentic.
Is there a Bindstack MCP server?
You don't need an MCP server to give your agent Bindstack. Jentic connects it directly from the API Directory: import it and your agent calls the retrieval-augmented query operation. That keeps your agent's context free of an extra server's tool definitions.
What authentication does the Bindstack RAG Query API use?
The query endpoint does not declare any authentication in its OpenAPI spec. If your deployment requires a key, Jentic keeps it encrypted in your own instance and injects it at call time, so it never reaches the agent's context.
Can I search a meeting transcript with the Bindstack RAG Query API?
Yes. POST /v1/external/rag/query takes a meeting_code and a query and returns the ranked results array with each passage's similarity score, plus the meeting_title and total_results for the match.
How do I query a meeting transcript through Jentic?
Search Jentic for 'query a meeting transcript', load the input schema, and execute POST /v1/external/rag/query with a meeting_code and query. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Bindstack RAG Query API?
Yes. Bindstack carries the meeting_code in the request body, so a rule bounds which operations your agent may call rather than which meeting. With a single query operation, you allow that one read operation and nothing else, and every call it makes is logged.
GET STARTED