canonical: https://jentic.com/apis/xylox.co/xylox

# Xylox Meet Xara AI API

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.

## For AI agents

Programmatically create transcription, list transcriptions. Covers 5 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for ai and machine learning only.

## Capabilities

- Create transcription
- List transcriptions
- Get transcription
- Generate summary
- Extract action items

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create transcription', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/transcriptions` | Create transcription |
| GET | `/transcriptions` | List transcriptions |
| GET | `/transcriptions/{transcription_id}` | Get transcription |
| POST | `/summaries` | Generate summary |
| GET | `/transcriptions/{transcription_id}/action-items` | Extract action items |

## Key resources

- **Transcriptions** — Audio transcription
- **Summaries** — Meeting summarization
- **Action Items** — Action item extraction

## AI readiness

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.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 94 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/xylox.co/xylox/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Openai** — Alternative ai ml API
- **Anthropic** — Alternative ai ml API
- **Cohere** — Complementary ai ml API
- **Huggingface** — Complementary ai ml API

## FAQ

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