Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SYNQ Video, 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%2Fsynq.fm%2Fsynq-video" | 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%2Fsynq.fm%2Fsynq-video" | 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 SYNQ Video API.
Create a new video, optionally setting some metadata fields.
Return details about a video.
Perform a JavaScript query to return video objects matching any desired criteria
Update a video's metadata.
Monitor SYNQ Video operational status and events
GET STARTED
Patterns agents use SYNQ Video API for, with concrete tasks.
★ Media and Content Operations
Use the SYNQ Video to perform media operations programmatically. The API provides 7 endpoints covering core functionality including create a new video, optionally setting some metadata fields., return details about a video., perform a javascript query to return video objects matching any desired criteria.
Call POST /video/create to create a new video, optionally setting some metadata fields.
Automated video Management
Automate video operations by combining multiple SYNQ Video endpoints. Agents can return details about a video. and then perform a javascript query to return video objects matching any desired criteria in a single workflow.
Call POST /video/details to return details about a video., then verify the result
AI Agent Integration via Jentic
AI agents discover and call SYNQ Video 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 none tokens manually.
Search Jentic for 'create a new video, optionally setting some metadata fields.', load the operation schema, and execute with Jentic-managed credentials
7 endpoints — * [sign up for a developer api key!](https://www.
METHOD
PATH
DESCRIPTION
/video/create
Create a new video, optionally setting some metadata fields.
/video/details
Return details about a video.
/video/query
Perform a JavaScript query to return video objects matching any desired criteria
/video/stream
Returns urls for streaming.
/video/update
Update a video's metadata.
/video/upload
Return parameters needed for uploading a video file.
/video/uploader
Return embeddable url to an uploader widget
/video/create
Create a new video, optionally setting some metadata fields.
/video/details
Return details about a video.
/video/query
Perform a JavaScript query to return video objects matching any desired criteria
/video/stream
Returns urls for streaming.
/video/update
Update a video's metadata.
/video/upload
Return parameters needed for uploading a video file.
/video/uploader
Return embeddable url to an uploader widget
What agents get from Jentic-routed access to this vendor.
Setup
Wiring SYNQ Video by hand means managing the API key each call to the api.synq.fm host expects and shaping the create, upload, and query requests yourself. Through Jentic you install once, import SYNQ Video from the API Directory, store the credential once, and your agent calls it.
Permission scoping
SYNQ Video carries the video id and metadata in the request body rather than the URL path, so scope the agent to the operations it needs, such as creating a video or querying details. You choose that allowed set, so an operation you do not add, like updating a video, stays out of reach.
Credential isolation
Your SYNQ Video credential 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 'create a video' or 'query video details', and Jentic returns the matching SYNQ Video 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 SYNQ Video API through Jentic.
What authentication does the SYNQ Video use?
The SYNQ Video uses no authentication. 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 a new video, optionally setting some metadata fields. with the SYNQ Video?
Yes. Use the POST /video/create endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SYNQ Video?
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 a new video, optionally setting some metadata fields. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new video, optionally setting some metadata fields.'. Jentic returns the matching SYNQ Video operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SYNQ Video have?
The SYNQ Video exposes 7 endpoints covering video operations.
Can I limit what my agent is allowed to do with the SYNQ Video API?
Yes. Jentic One is self-hosted by you, so your own rules decide which SYNQ Video operations and credentials the agent may use. You add only the endpoints you want it to reach, such as POST /video/create to create a video or POST /video/query to query details, and leave out anything else. If you never add an operation like POST /video/update, updating a video's metadata stays out of the agent's reach.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically create a new video, optionally setting some metadata fields., return details about a video.. Covers 7 operations.
Use for: I need to a new video, optionally setting some metadata fields., I want to return details about a video., Search for perform a javascript query to return video objects matching any desired criteria, Find all returns urls for streaming.
Not supported: Does not handle payments, communications, or crm - use for media and content only.
* [Sign up for a developer API key!](https://www.synq.fm/register) * [SYNQ API Guide](/). The API exposes 7 endpoints.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
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>