slideforge-dev Generate API

The generate API from slideforge-dev — 3 operation(s) for generate.

Operations 7

POST /v1/generate Removed — the Generate (creative codegen) engine is gone #
POST /v1/iterate Removed — the iterate SKU is gone #
GET /v1/themes Removed — the legacy theme layer is gone, use /v1/brands #
PUT /v1/themes Removed — the legacy theme layer is gone, use /v1/brands #
POST /v1/themes Removed — the legacy theme layer is gone, use /v1/brands #
DELETE /v1/themes Removed — the legacy theme layer is gone, use /v1/brands #
PATCH /v1/themes Removed — the legacy theme layer is gone, use /v1/brands #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/slideforge-dev:slideforge-dev-generate-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

slideforge-dev-generate-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: SlideForge Generate API
  description: 'Agent-first PowerPoint generation. Send structured slide intents (a `form` plus typed fields) or a brief; get back a real, editable `.pptx`. The draw path is deterministic — no model renders your slide, so supplied numbers and text come out verbatim. Every response carries `status`, `fidelity` and `warnings` so an automated caller can tell whether the output is usable. $0.05 per slide; an unusable slide is not billed. Authenticate with a SlideForge API key (`Authorization: Bearer sf_live_…` or `X-API-Key`) — new accounts include 60 free slides, no credit card: https://slideforge.dev/sign-up'
  version: 5.356.0
servers:
- url: https://api.slideforge.dev
security:
- bearerAuth: []
- apiKeyAuth: []
tags:
- name: Generate
paths:
  /v1/generate:
    post:
      tags:
      - Generate
      summary: Removed — the Generate (creative codegen) engine is gone
      description: Gone (410). The Generate engine was removed per ADR 2026-06-12. Send a structured intent via the MCP create_slide tool or POST /v1/render/auto, or run your own python-pptx code via POST /v1/render (mode=code). Every render is $0.05.
      operationId: generate_slide_v1_generate_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '410':
          description: Generate engine removed
  /v1/iterate:
    post:
      tags:
      - Generate
      summary: Removed — the iterate SKU is gone
      description: 'Gone (410). Iterating is re-sending the modified intent: every render is $0.05, and an identical input is free.'
      operationId: iterate_slide_v1_iterate_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '410':
          description: Iterate removed
  /v1/themes:
    get:
      tags:
      - Generate
      summary: Removed — the legacy theme layer is gone, use /v1/brands
      description: Gone (410). The legacy theme layer (`/v1/themes*`, `theme_json`) was replaced by brand kits per spec 37. List and manage kits via /v1/brands; `theme_id` on every render call keeps its name and accepts a built-in id or a brand slug (`slug@N` pins a version).
      operationId: themes_gone
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '410':
          description: Legacy theme layer removed
    put:
      tags:
      - Generate
      summary: Removed — the legacy theme layer is gone, use /v1/brands
      description: Gone (410). The legacy theme layer (`/v1/themes*`, `theme_json`) was replaced by brand kits per spec 37. List and manage kits via /v1/brands; `theme_id` on every render call keeps its name and accepts a built-in id or a brand slug (`slug@N` pins a version).
      operationId: putV1Themes
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '410':
          description: Legacy theme layer removed
      x-operation-id-source: normalized
      x-operation-id-original: themes_gone
    post:
      tags:
      - Generate
      summary: Removed — the legacy theme layer is gone, use /v1/brands
      description: Gone (410). The legacy theme layer (`/v1/themes*`, `theme_json`) was replaced by brand kits per spec 37. List and manage kits via /v1/brands; `theme_id` on every render call keeps its name and accepts a built-in id or a brand slug (`slug@N` pins a version).
      operationId: postV1Themes
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '410':
          description: Legacy theme layer removed
      x-operation-id-source: normalized
      x-operation-id-original: themes_gone
    delete:
      tags:
      - Generate
      summary: Removed — the legacy theme layer is gone, use /v1/brands
      description: Gone (410). The legacy theme layer (`/v1/themes*`, `theme_json`) was replaced by brand kits per spec 37. List and manage kits via /v1/brands; `theme_id` on every render call keeps its name and accepts a built-in id or a brand slug (`slug@N` pins a version).
      operationId: deleteV1Themes
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '410':
          description: Legacy theme layer removed
      x-operation-id-source: normalized
      x-operation-id-original: themes_gone
    patch:
      tags:
      - Generate
      summary: Removed — the legacy theme layer is gone, use /v1/brands
      description: Gone (410). The legacy theme layer (`/v1/themes*`, `theme_json`) was replaced by brand kits per spec 37. List and manage kits via /v1/brands; `theme_id` on every render call keeps its name and accepts a built-in id or a brand slug (`slug@N` pins a version).
      operationId: patchV1Themes
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '410':
          description: Legacy theme layer removed
      x-operation-id-source: normalized
      x-operation-id-original: themes_gone
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: 'SlideForge API key: `Authorization: Bearer sf_live_…`. Create one at https://slideforge.dev/console/keys'
    apiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
      description: Same key, header form — for clients that cannot set Authorization.