For Agents
Programmatically create transcription, list transcriptions. Covers 5 operations with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Meet Xara AI 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fxylox.co%2Fxylox" | shStep 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%2Fxylox.co%2Fxylox" | 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.
What an agent can do with Meet Xara AI API.
Create transcription
List transcriptions
Get transcription
Generate summary
GET STARTED
Use for: I need to transcription, I want to transcriptions, Search for transcription, Find all generate summary
Not supported: Does not handle payments, communications, or crm - use for ai and machine learning only.
Meet Xara AI API for intelligent meeting assistance and communication automation. AI-powered meeting transcription, summarization, and action item extraction. The API exposes 5 endpoints secured with apiKey authentication.
Extract action items
Patterns agents use Meet Xara AI API for, with concrete tasks.
★ AI and Machine Learning Operations
Use the Meet Xara AI API to perform ai ml operations programmatically. The API provides 5 endpoints covering core functionality including create transcription, list transcriptions, get transcription.
Call POST /transcriptions to create transcription
Automated Transcriptions Management
Automate transcriptions operations by combining multiple Meet Xara AI API endpoints. Agents can list transcriptions and then get transcription in a single workflow.
Call GET /transcriptions to list transcriptions, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Meet Xara AI API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'create transcription', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — meet xara ai api for intelligent meeting assistance and communication automation.
METHOD
PATH
DESCRIPTION
/transcriptions
Create transcription
/transcriptions
List transcriptions
/transcriptions/{transcription_id}
Get transcription
/summaries
Generate summary
/transcriptions/{transcription_id}/action-items
Extract action items
/transcriptions
Create transcription
/transcriptions
List transcriptions
/transcriptions/{transcription_id}
Get transcription
/summaries
Generate summary
/transcriptions/{transcription_id}/action-items
Extract action items
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Meet Xara AI by hand means sending the X-API-Key header on ai-api.xylox.co, polling transcription jobs to completion, and handling retries yourself. Through Jentic you install once, import Meet Xara AI from the API Directory, store the key once, and your agent calls it.
Permission scoping
Meet Xara AI puts the transcription id in the URL path (/transcriptions/{transcription_id}), so a rule can pin your agent to one transcription: it can read that transcription and its action items and nothing else. You choose the operations it may call, so creating new transcriptions or summaries is not included unless you add it.
Credential isolation
Your Meet Xara AI key 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 'transcribe a meeting' or 'get action items', and Jentic returns the matching Meet Xara AI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Meet Xara AI API through Jentic.
What authentication does the Meet Xara AI API use?
The Meet Xara AI API uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create transcription with the Meet Xara AI API?
Yes. Use the POST /transcriptions endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Meet Xara AI API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create transcription through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create transcription'. Jentic returns the matching Meet Xara AI API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Meet Xara AI API have?
The Meet Xara AI API exposes 5 endpoints covering transcriptions, summaries, action items operations.
Can I limit what my agent is allowed to do with the Meet Xara AI API?
Yes. Because you self-host Jentic One, your own rules decide which Meet Xara AI operations and credentials the agent may use. Since the transcription id sits in the URL path (/transcriptions/{transcription_id}), you can pin the agent to a single transcription so it only reads that transcription and its action items and nothing else. Operations like creating transcriptions (POST /transcriptions) or generating summaries (POST /summaries) are excluded unless you explicitly grant them.