canonical: https://jentic.com/apis/synclabs.so/synclabs-so

# Synclabs So Synchronize API

Synchronize API allows you to lipsync a video to any audio in any language. The API exposes 19 endpoints secured with apiKey authentication.

## For AI agents

Programmatically voicescontroller_voicecost. Covers 19 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for media and content only.

## Capabilities

- VoicesController_voiceCost
- Manage media data programmatically
- Integrate Synchronize API into automated workflows
- Query and filter Synchronize API records by parameters
- Monitor Synchronize API operational status and events

## Use cases

### Media and Content Operations

Use the Synchronize API to perform media operations programmatically. The API provides 19 endpoints covering core functionality including voicescontroller_voicecost.

Example prompt: Call GET `/voices/cost` to voicescontroller_voicecost

### Data Retrieval and Monitoring

Query Synchronize API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Synchronize API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Synchronize 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 'voicescontroller_voicecost', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/voices/cost` | VoicesController_voiceCost |

## Key resources

- **voices** — Operations related to voices
- **video** — Operations related to video
- **lipsync** — Operations related to lipsync
- **translate** — Operations related to translate
- **speak** — Operations related to speak

## 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:** 37 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 46 / 100
  - Developer Experience & Jentic Compatibility: 44 / 100
  - AI-Readiness & Agent Experience: 17 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/synclabs.so/synclabs-so/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 the Synchronize API by hand means sending the x-api-key header to the api.synclabs.so host and shaping the requests for its media operations yourself. Through Jentic you install once, import the Synchronize API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Synchronize API takes its inputs in the request body and parameters rather than a resource path, so scope the agent to the operations it needs, such as fetching the cost for a voice. You choose that allowed set, so any operation you do not add stays out of reach.
- **Credential handling:** Your Synchronize API 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 'get the cost of a voice', and Jentic returns the matching Synchronize operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

### What authentication does the Synchronize API use?

The Synchronize 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 voicescontroller_voicecost with the Synchronize API?

Yes. Use the GET `/voices/cost` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Synchronize 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 voicescontroller_voicecost through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'voicescontroller_voicecost'. Jentic returns the matching Synchronize API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Synchronize API have?

The Synchronize API exposes 19 endpoints covering voices, video, lipsync operations.

### Can I limit what my agent is allowed to do with the Synchronize API?

Yes. Because you run Jentic One yourself, your own rules decide which Synchronize API operations and credentials the agent may use, and any operation you do not add stays out of reach. The Synchronize API takes its inputs in the request body and parameters rather than a resource path, so you scope the agent to just the operations it needs, such as GET `/voices/cost` to fetch the cost for a voice while leaving lipsync, video, translate, or speak operations unavailable. The stored API key is injected only when the agent calls an operation you have allowed.