What authentication does the Cincopa REST API V2 use?

The API uses an apiKey called api_token passed as a query parameter on every request. Through Jentic the api_token is stored in the encrypted vault and the agent never receives the raw value, only a scoped execution context.

Can I upload a video to Cincopa from a remote URL?

Yes. Call /asset.upload_from_url.json with the source URL and the target gallery, and Cincopa will fetch and transcode the asset. Upload status can be polled via /asset.upload_from_url_get_status.json.

How do I add an asset to a Cincopa gallery through Jentic?

Search Jentic for 'add a video to a gallery', load the schema for /gallery.add_item.json, and execute with the gallery and asset IDs. The Python SDK uses await client.search, await client.load, await client.execute.

How do I generate a browser-safe read-only token?

Call /token.get_temp.json on the server with the master api_token to mint a temporary read-only token, then pass that scoped token to the browser embed. The master token never leaves the server.

How do I tag a Cincopa asset and read tags back?

Use /asset.set_meta.json to attach tags as metadata and /asset.get_tags.json to read the tag taxonomy for an asset. Tags drive search and gallery filtering downstream.

Can I limit what my agent is allowed to do with the Cincopa REST API V2?

Yes. Because you run Jentic One yourself, your own rules decide which Cincopa operations and credentials the agent may use, so you can grant only the calls the task needs. For example, you can allow gallery composition through /gallery.add_item.json and /gallery.set_master.json while withholding destructive operations like /gallery.delete.json, or permit uploads via /asset.upload_from_url.json without exposing token minting through /token.get_temp.json. Since Cincopa's write operations take the target asset or gallery id in the request body rather than the URL path, you scope access at the operation level to match exactly what you want the agent to run.