Create with Show
Show helps teams turn a brief into a blog, a one-pager or an HTML presentation. The human app at https://show.jetskibay.com requires your team's Cloudflare Access login. Choose a format, write a brief with audience and outcome, provide source material, start generation and follow the job. Review the artifact before sharing it. The existing Show workspace keeps its team integrations.
Independent service
The public developer service at https://content.jetskibay.com accepts API keys. Use its playground to request a key by email. Keys have an expiry and generation allowance; see GET /v1/keys/current for your balance. Keep keys server-side. No Vault projects, images, search or writes are exposed by this service. Use your brief, uploaded files or public research instead.
POST /v1/posts, /v1/pages or /v1/decks with Authorization: Bearer YOUR_CONTENT_API_KEY and a JSON body:
{"brief":"Explain our pilot to leadership. We tested with 12 participants; 9 completed onboarding. Ask for approval for a second pilot. Do not invent revenue figures."}
The response is HTTP 202 with requestId, statusUrl and pollAfterMs. GET the statusUrl with the same key, waiting at least pollAfterMs between calls. Stop on succeeded, failed or cancelled. Generation consumes allowance; polling and downloads do not. Server failures refund the generation request. Invalid generation requests can consume allowance.
Successful blogs return a public blog.jetskibay.com URL, pages a public page.jetskibay.com URL. Presentations return an authenticated downloadUrl for standalone HTML, not PPTX. Download with your key and save the returned bytes as .html. Generation is asynchronous and can fail; a queued job is not a completed artifact.
Authenticated MCP
Connect an OAuth-capable Streamable HTTP client to https://content.jetskibay.com/mcp and sign in through Auth0. The Worker advertises protected-resource metadata at /.well-known/oauth-protected-resource/mcp. Your Auth0 user ID must be on the Worker's allowlist. Protocol revision: 2026-07-28. Discover tools with tools/list. Operations are create_blog, create_one_pager, create_presentation and get_job. Creation returns a queued job with pollTool: get_job; call get_job with {"requestId":"..."}. A successful presentation job provides an OAuth-protected downloadUrl; fetch it with the same access token. The direct MCP has a separate 10-generation-per-24-hour allowance per Auth0 user. Polling and downloads are free; server failures refund a charge.
MCP creation accepts brief (1–40,000 characters), optional skillIds (at most five), files (at most ten, 20 MB total), research.webSearch and research.urlCaptures (at most three), mode, entityId, idempotencyKey and options. Blog/page options include targetWords (250–5000); presentation options include targetSlides (3–30), aspectRatio (16:9 or 4:3), speakerNotes. All support audience, tone, goal and density; tools/list declares their exact enums. Unknown MCP fields are rejected.
Use create by default. Pages accept update; blogs and presentations accept rewrite. Both follow-up modes require entityId from a succeeded job owned by the same Auth0 user (or REST API account). Poll the original job to record the generated entity before updating it. Reuse idempotencyKey only when retrying the same request; retries count toward generation allowance.
Jetskibay gateway
Catalogue registration and execution configuration are separate. The existing aggregate gateway uses the key-authenticated compatibility route https://content.jetskibay.com/api/mcp with a dedicated Content API key in SHOW_MCP_TOKEN. Set SHOW_MCP_URL to that exact URL. Gateway clients use their gateway credential; it is never forwarded upstream. Operations there are show__create_blog, show__create_one_pager, show__create_presentation and show__get_job.
The gateway uses one upstream API-key account: its users share that account's job visibility, limits and expiry. Renew the upstream key before expiry. Direct OAuth MCP users and REST API accounts each retain their own ownership boundary. Public manifests cannot change credential routing.
Data and limits
Context packs and supplied files are stored in Cloudflare R2; job/account metadata is stored in D1; generation runs in the existing communication services and their configured model providers. Public blog/page output is intentionally published. Do not include private information in a public artifact. Generated content needs factual and editorial review. No retention or deletion guarantee is introduced by this release.
Published by Jetski Bay.