Official vendor OpenAPI document · agent-readyMediaContent Deliverybearer, oauth241 EndpointsREST
For Agents
Turn HTML an agent wrote into a narrated, shareable presentation and read any shared presentation back as a transcript. Publish from HTML, build slide by slide, narrate, track progress, and embed via oEmbed across 41 endpoints.
Use for: Publish a presentation from HTML to a shareable link, Read a shared presentation as a text transcript, Narrate the slides of a presentation, Add slides to a presentation I am building
Not supported: Does not host live video calls, record meetings, or design slides visually. Use for publishing and reading narrated HTML presentations only.
The Bisque API turns an HTML file an agent wrote into a narrated presentation on a shareable watch link, and lets an agent read any shared presentation back as a plain-text transcript. It publishes a presentation in one request or builds one incrementally by adding and narrating slides, reports narration and publish progress, and returns an oEmbed card for a watch URL. A public authoring-format spec tells an agent how to write valid presentation HTML before it publishes.
Install Jentic One Beta
Connect the Bisque API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bisque 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.
1
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%2Fbisque.cloud%2Fbisque" | sh2
Step 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%2Fbisque.cloud%2Fbisque" | 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.
Capabilities
What an agent can do with Bisque API.
Publish a presentation from an HTML file to a shareable watch link
Narrate a presentation's slides and track publish progress
Read any shared presentation back as a plain-text transcript
Build a presentation incrementally by adding and narrating slides, then finalize it
Get an oEmbed card for a presentation's watch URL
Fetch the authoring-format spec so an agent writes valid presentation HTML
Use Cases
Patterns agents use Bisque API for, with concrete tasks.
★ Publish an agent-written deck through Jentic
Let an agent turn the HTML it just wrote into a narrated presentation on a shareable link. The agent submits the HTML, Bisque narrates and publishes it, and the status operation reports progress until the watch link is ready. Through Jentic the create operation is discovered by intent and called with its input schema, so publishing fits into the agent's flow.
Publish a presentation from HTML with POST /api/presentations/create, then poll GET /api/presentations/status until it is ready
Read a presentation as a transcript
Give an agent the full text of a presentation it was linked to so it can summarize, quote, or answer questions about it. The context operation returns a presentation as plain text with no credentials needed, and a batch form reads several at once.
Read a shared presentation as text with GET /api/presentations/context
Build a presentation slide by slide
Create a presentation and fill it in over several steps instead of publishing in one shot. The agent opens a live creation, adds slides as it drafts them, narrates each one, and finalizes when the deck is complete, so a long presentation can be assembled progressively.
Create a live presentation with POST /v1/presentations, add slides with PATCH /v1/presentations/{presentationId}, then narrate one with PATCH /v1/presentations/{presentationId}/slides/{slideKey}
Embed a presentation
Surface a published presentation inside another page or chat with a proper preview card. The agent requests the oEmbed card for a watch URL and drops the returned embed markup wherever the deck should appear.
Get an embed card with GET /api/oembed for a presentation's watch URL
Key Endpoints
41 endpoints — the bisque api turns an html file an agent wrote into a narrated presentation on a shareable watch link, and lets an agent read any shared presentation back as a plain-text transcript.
METHOD
PATH
DESCRIPTION
POST
/api/presentations/create
Publish a presentation from HTML
GET
/api/presentations
List your presentations
GET
/api/presentations/context
Read a presentation as text
GET
/api/presentations/status
Narration and publish progress
POST
/v1/presentations
Create a presentation and put its slides up
PATCH
/v1/presentations/{presentationId}
Add slides to a live creation
GET
/api/presentations/spec
Get the authoring format
GET
/api/oembed
oEmbed for a watch URL
POST
/api/presentations/create
Publish a presentation from HTML
GET
/api/presentations
List your presentations
GET
/api/presentations/context
Read a presentation as text
GET
/api/presentations/status
Narration and publish progress
POST
/v1/presentations
Create a presentation and put its slides up
PATCH
/v1/presentations/{presentationId}
Add slides to a live creation
GET
/api/presentations/spec
Get the authoring format
GET
/api/oembed
oEmbed for a watch URL
Jentic AI Readiness Score
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.
B
Bisque API
- AI-Aware (B)66/100
77
Foundational Compliance61
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability75
Security74
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
77
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
10%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
61
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
2%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
43%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
48%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
98%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
45%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
74
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
74%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Bisque by hand means learning its bearer and OAuth2 auth, the HTML authoring format, and the two creation flows for one-shot and incremental publishing. Through Jentic you install once, import Bisque from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Bisque puts the presentation id in the URL path (/v1/presentations/{presentationId}/...), so a rule can pin your agent to building and narrating one presentation. You choose which operations it may call, so publishing new presentations or reading others stays out unless you add them.
Credential isolation
Your Bisque 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 'publish a presentation from HTML' or 'read a presentation as text', and Jentic returns the matching Bisque operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Bisque API through Jentic.
What authentication does the Bisque API use?
The Bisque API authenticates with a bearer token, and it also supports an OAuth2 authorization-code flow, per its OpenAPI spec. Publishing a presentation needs a credential, while reading the authoring format, reading a shared presentation, and oEmbed are public. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time.
Can I read a shared presentation as text with the Bisque API?
Yes. The context operation returns a presentation as plain text with no credentials needed, and a batch form reads up to 20 presentations in one request, so an agent can summarize or quote a deck it was linked to.
Can I limit what my agent is allowed to do with the Bisque API?
Yes. Write a rule that allows only the read operations, so your agent can fetch presentation transcripts and the authoring format but cannot publish or finalize presentations unless you add those operations. Bisque carries the presentation id in the URL path, so building a single presentation can be bounded to that one resource.
What are the rate limits for the Bisque API?
The OpenAPI spec does not specify rate limits. Check the Bisque documentation at https://bisque.cloud for current limits before publishing presentations in bulk.
Is there a Bisque MCP server?
Yes, Bisque offers its own MCP server. You can also connect it directly through Jentic: your agent gets the full 41-endpoint surface without loading another server's tool definitions into its context, your credential is injected at call time by your self-hosted instance instead of living in a config file, and your rules decide which operations the agent may call.
How do I publish a presentation from HTML with the Bisque API through Jentic?
Search Jentic for 'publish a presentation from HTML' and it returns the Bisque create operation with its input schema. Your agent sends the HTML, Bisque narrates and publishes it to a watch link, and the status operation reports progress. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED