turboslide.com valid

Turboslide

A block document with a validator and a grammar linter; every operation is a named action in one table, reachable from the CLI, MCP, HTTP and the studio window API.

For agents: Browser-based slides editor with named actions reachable via CLI, MCP, HTTP and a window API, so agents can run the same editing operations; no account needed.

slides editorpresentationsbrowser editormcpclispeaker notes

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T13:38:28.459Z. Cached copy · Source on turboslide.com

# Turboslide

> A block document with a validator and a grammar linter; every operation is a named action in one table, reachable from the CLI, MCP, HTTP and the studio window API.

Turboslide keeps a presentation as typed JSON (deck.json plus slides/<id>.json), renders it with one renderer, lints it against the deck grammar, and exports it to PPTX with a verified report, pixel identical in its default mode. There are no coordinates: a slide is a kind, a layout and typed blocks in named slots.

## Discovery

- /api/agent: the manifest (transports, rules, execution rules, action ids, skills, resources, what this instance implements)
- /openapi.json: the OpenAPI 3.1 contract of POST /api/actions/<id>
- /mcp: MCP over streamable HTTP; `turboslide mcp` is the same server over stdio
- /llms-full.txt: this guide with every action and every lint rule
- /docs/agents/skills.md: the four skills (turboslide-create, turboslide-api, turboslide-studio, turboslide-verify), with links to each SKILL.md and its generated reference tables
- /docs/agents/grammar.md: the deck grammar (slide kinds, layouts, blocks, rules)

## Rules

- Every mutating action requires baseRevision and rejects a stale one with 409 and the current document.
- Every write returns the normalized result; re-read from the response, not from memory.
- Unknown fields are rejected with unknown_field and a JSON pointer, except under ext on a slide, a block or an asset.
- An agent write to a slide another author leased is refused with 409 and the holder unless force is set.
- A claim about a deck names the revision; render both themes and lint before claiming a slide is done.

## Calling an action over HTTP

- POST /api/actions/<id>; GET /api/actions/<id> returns the action contract: input and output JSON Schema, transports, milestone and whether this instance implements it.
- Body: One JSON object, the action input exactly as the input schema states it; unknown fields are refused with 400 and code unknown_field plus a JSON pointer.
- Deck: ?deck=<slug> names the deck. A read without it reads the instance default (gt-brand); a write that lands on a deck and names none is refused with 400 and code deck_required (the share and publish actions may name their deck in the input id instead).
- Author: Every write is recorded under the caller's identity: an API key's owner as agent:<tokenId>. x-turboslide-author: agent:<runId> (or ?author=) only labels the run; without a key, a request that names no author writes as agent:http.
- Force: ?force=1 (or x-turboslide-force: 1) writes to a slide another author leased; without it the write is 409 with the holder and the current document.
- Retries: Idempotency-Key: <one value per write, such as a UUID> on a POST of a writing action that takes it (its OpenAPI entry names the header: the slide, block, text, section, deck setting, asset and restore writes) makes it safe to resend after a timeout: send the same key with the same body, and a write that already landed
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=turboslide.com · GET /v1/domain/turboslide.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for turboslide.com:
1. POST https://agentwebmap.com/v1/sites/turboslide.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://turboslide.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/turboslide.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/turboslide.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.