Replit vs Floot

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Replit✓fullprobed8/10

   A probe confirms Replit docs serve a working llms.txt at docs.replit.com/llms.txt (HTTP 200) listing structured doc sections, directly enabling an agent to be pointed at agent-oriented docs; this is corroborated by extensive first-party docs pages formatted for agent consumption. Missing for 10: independent third-party confirmation that agents actually consume/use this llms.txt effectively, and no evidence of an OpenAPI spec or other machine-readable API docs (all probed paths 404).

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

   proof ↗⚑ flag

   Floot✓fullprobed8/10

   Floot serves a live llms.txt (HTTP 200) and an llms-full.txt with agent-oriented documentation of its capabilities, confirmed by direct probes. missing for 10: independent third-party confirmation that agents actually consume and act on these docs successfully, and docs.md/openapi endpoints return 404 suggesting the agent-doc surface is limited to llms.txt only.

   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”
   • [claimed-docs] “point at an element or annotate a screenshot for the assistant to pick up”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Replit—none0/10

   Evidence covers Replit's Agent modes, MCP connectors, and scheduled 'routines' but nothing about a CLI, API, or headless mode for running Replit in CI/automation pipelines outside its own UI. missing for 10: CLI/API for headless execution, CI/CD pipeline integration, documented automation outside Replit's own scheduler.

   • [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
   • [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
   • [claimed-docs] “Choose Free Mode, Power Mode, or Max Mode based on the work you want to do, the capability you need, and your available allowance or credits…”

   proof ↗⚑ flag

   Floot—none0/10

   Floot is a chat-based/MCP-driven app builder with no evidence of a CLI, API, or headless mode for CI/automation pipelines; MCP integration is for interactive AI clients (Cursor, VS Code, Zed), not headless CI execution. No mention of scripted builds, CI/CD triggers, or non-interactive automation. Missing for 10: CLI or SDK for scripted invocation, CI/CD pipeline documentation, headless build/deploy commands, API endpoints for automation.

   ⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Replit
   Replit✓fullclaimed8/10

   Replit's docs explicitly describe connecting Agent to external tools via MCP, with a curated catalog (Stripe, Linear, Notion, Sentry) plus the ability to add custom servers by URL, giving Agent access to their tools. missing for 10: independent/hands-on community corroboration of MCP usage in practice, and detail on tool invocation reliability beyond first-party docs.

   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Connect your tools, add reusable Skills, and extend Replit with MCP.”
   • [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”
   • [claimed-docs] “If the server you want isn't in the pre-listed catalog, add it by URL.”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”

   proof ↗⚑ flag

   Floot—none0/10

   All evidence describes Floot exposing itself as an MCP server that other clients (Cursor, VS Code, Zed) can connect to and use its tools (get_logs, query_database, etc.) — the reverse direction of this story. There is no evidence that a user can plug external MCP servers into Floot so Floot's own AI can call their tools.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Replit✓fullclaimed7/10

   Replit documents an official Replit MCP Server that external compatible clients can connect to in order to create, inspect, or update Replit Apps (replit-docs-42), which is exactly the story of connecting an agent via an official MCP server (distinct from Replit Agent acting as an MCP client to third-party services, e.g. replit-docs-12/20/41). This is first-party documented capability with a dedicated docs page (connect-through-mcp.md). Missing for 10: independent/hands-on corroboration of connecting an external agent to Replit's MCP server, and more detail on auth/setup flow or limitations.

   • [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
   • [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”

   proof ↗⚑ flag

   Floot✓fullprobed7/10

   Floot documents an official remote MCP server that can be added to Cursor, VS Code, Zed, or any MCP-compatible client, with concrete tool capabilities (get_logs, query_database, execute_sql, create_checkpoint, generate_image) exposed via that server. This is first-party documentation only, with no independent/hands-on corroboration of the MCP connection working in practice. Missing for 10: independent or community verification of the MCP server working end-to-end, and more detail on authentication/setup reliability.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “generate_image writes AI images into the project.”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Replit—none0/10

   Evidence covers Replit's web/desktop/mobile apps, Agent, MCP integrations, and deployments, but nowhere mentions an official CLI tool for AI-native workflows. Absence of evidence for this applicable capability means 'none' rather than 'na'.

   ⚑ flag

   Floot—none0/10

   Floot is a chat/browser-based app builder that offers an MCP server for connecting external AI clients, but there is no evidence of an official CLI tool for AI-native workflows; all evidence points to MCP integration and web-based chat, not a CLI. Missing for 10: any mention of a CLI binary, npm/pip install, or command-line docs.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Floot
   Replit~partialprobed5/10

   Replit documents an MCP server that lets external clients create, find, inspect, or update Replit Apps (replit-docs-42), which functions as a documented programmatic interface for AI-native control, but there is no evidence of a traditional REST/OpenAPI-documented public API — probes for openapi.json/swagger.json all returned 404 (replit-probe-2). missing for 10: a formal REST/OpenAPI-documented API, independent confirmation of MCP server reliability/completeness, broader API surface beyond MCP-driven app management.

   • [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”

   proof ↗⚑ flag

   Floot~partialprobed7/10

   Floot documents a first-party MCP server exposing concrete tools (get_logs, query_database, execute_sql, create_checkpoint, generate_image) that let an AI client drive the product programmatically, which directly serves the AI-native persona. However, probes show no conventional public REST/OpenAPI API (openapi.json/swagger.json all 404, docs.md 404), so the 'documented public API' story is only satisfied via the MCP protocol rather than a broader API surface. Missing for 10: a traditional REST/OpenAPI-documented API or SDK, and independent confirmation of MCP tool reliability beyond vendor docs.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “generate_image writes AI images into the project.”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”
   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Replit—none0/10

   Evidence covers built-in auth for end-user apps and centralized connector management, but there is no documentation of issuing scoped or least-privilege API credentials specifically to control an agent's own access level. Missing for 10: any mention of API key/credential scoping, permission levels, or least-privilege token issuance for the agent itself.

   ⚑ flag

   Floot—none0/10

   No evidence Floot supports issuing scoped or least-privilege API credentials/tokens for agents; MCP integration docs describe tool capabilities (query_database, execute_sql, etc.) but nothing about credential scoping, permission levels, or least-privilege access control for agents. missing for 10: any mention of API keys, token scoping, permission tiers, or credential management for agent access.

   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Replit—none0/10

   The evidence pack describes MCP-based integrations, connectors, and Agent Skills, but never mentions an official SDK (e.g., a Python/JS client library) for programmatically building against Replit, and a direct probe for an OpenAPI/API spec returned 404s on all candidate paths, suggesting no public SDK/API surface is documented.

   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Connect your tools, add reusable Skills, and extend Replit with MCP.”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”

   proof ↗⚑ flag

   Floot—none0/10

   Floot exposes an MCP server with tool functions (get_logs, query_database, execute_sql, etc.) but there is no evidence of official language SDKs (e.g., npm/pip packages) or an OpenAPI spec for developers to build against programmatically; probes for openapi.json/swagger.json all 404.

   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Replit—none0/10

   No evidence in the pack mentions webhooks, event subscriptions, or a mechanism for Replit apps/agents to subscribe to outbound events; the docs cover MCP connections, integrations, deployments, and auth but nothing about webhook subscriptions.

   ⚑ flag

   Floot—none0/10

   No evidence pack item mentions webhooks, event subscriptions, or any outbound notification/event system that AI-native users could subscribe to; the docs cover database, logs, images, mobile apps, and MCP tooling but nothing about webhooks.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Replit
   Replit~partialclaimed4/10

   Replit's Agent can pull in context from connected integrations (e.g. "Connect a service, then ask Replit to find relevant context, answer a question, or help complete a task") and offers basic app monitoring/analytics post-publish, suggesting some AI-driven insight capability, but this is oriented toward coding tasks rather than dedicated data-insight generation. missing for 10: explicit data-analysis/insight-generation feature (e.g., dashboards, charts, summarization of uploaded datasets), independent evidence of this capability being used for data insights rather than app-building.

   • [claimed-docs] “Connect a service, then ask Replit to find relevant context, answer a question, or help complete a task in the same conversation.”
   • [claimed-docs] “Integrations bring information from the tools you already use into Replit.”
   • [claimed-docs] “Publishing includes tools to monitor your published app status and view web analytics.”
   • [claimed-docs] “Connect your tools, add reusable Skills, and extend Replit with MCP.”

   proof ↗⚑ flag

   Floot—none0/10

   Floot's docs show built-in analytics tracking (page views, traffic sources, trends) and AI tools that can query/execute against the app's database, but there is no evidence the AI surfaces proactive insights or suggestions derived from that data back to the user — the query/execute tools are for development/debugging, not analytical insight generation.

   • [claimed-docs] “Built-in visitor tracking: page views, traffic sources, and trends.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Replit
   Replit✓fullclaimed7/10

   Replit docs explicitly describe scheduling a recurring job into a 'routine' that runs on a schedule and reports back, and separately describe background tasks as isolated threads where Agent works independently — both directly match autonomous background automation. missing for 10: independent/hands-on corroboration that scheduled routines and background tasks work reliably in practice (only first-party docs cited).

   • [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”

   proof ↗⚑ flag

   Floot—none0/10

   Floot's evidence covers app-building tools (database queries, logs, checkpoints, image generation, MCP integration) but nothing about scheduled tasks, triggers, or autonomous background automations running independently of a chat session. There is no mention of cron-like jobs, webhooks-as-triggers, or agent workflows executing without user interaction.

   ⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Replit✓fullcommunity8/10

   Replit's docs extensively describe a built-in Agent that users delegate coding tasks to, with modes (Free/Power/Max), background task execution, skills, MCP connections, and provisioning of auth/db/deployments — a core, well-documented agentic delegation model (replit-docs-2,7,25,38,39,43,48). Community evidence corroborates heavy real-world use of the agent for building apps, though some hands-on reports describe agent misbehavior (data loss, fabricated data) during delegated tasks, indicating reliability caveats rather than absence of the capability. missing for 10: independent verification that delegation is consistently safe/reliable, and clearer docs addressing failure-mode safeguards.

   • [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
   • [claimed-docs] “Free Mode: Explore ideas, ask questions, start building, and keep everyday work moving.”
   • [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
   • [claimed-docs] “Choose Free Mode, Power Mode, or Max Mode based on the work you want to do, the capability you need, and your available allowance or credits…”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Skills teach Agent new capabilities — preferred patterns, library specifics, design system rules, or solutions to problems you've already so…”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”
   • [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
   • [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”

   proof ↗⚑ flag

   Floot✓fullprobed8/10

   Floot's core product is an AI chat assistant that builds, debugs, queries databases, generates images, and manages checkpoints for the app directly from the chat interface, with tool actions like get_logs, query_database, generate_image documented. missing for 10: independent/hands-on corroboration beyond vendor docs, and clearer detail on task complexity/limits the assistant can handle autonomously.

   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “point at an element or annotate a screenshot for the assistant to pick up”
   • [claimed-docs] “generate_image writes AI images into the project.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Replit✓fullcommunity8/10

   Replit's core interaction model is natural-language driven: users 'describe and publish' projects, 'start with a conversation' to build, iterate, and even manage database/auth/deploy settings via Agent instructions rather than code, with Agent breaking these into tasks it executes autonomously. Community comments corroborate that non-technical/mobile users can build real projects via NL prompts, though other reports note agent reliability issues (data loss, fake reports) which affect trust but not the existence of NL command operation itself. Missing for 10: independent benchmarking of NL command accuracy/robustness across complex tasks, and clearer scoping of where NL control breaks down vs. requires manual intervention.

   • [claimed-docs] “Turn ideas into apps in minutes — no coding needed”
   • [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
   • [claimed-docs] “Start with a conversation. Ask questions, research ideas, and document your plan.”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [community] “I use Repl.it web interface for programming on the sofa from my Android phone. There's various bugs in the editor but it works well enough..…”
   • [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”

   proof ↗⚑ flag

   Floot✓fullprobed8/10

   Floot's core product is natural-language chat-based app building ('build and ship full-stack apps without leaving your AI chat', 'turns a plain-language description into a real, deployed full-stack app'), with rich agentic tool support (get_logs, query_database, create_checkpoint, generate_image) operable via NL commands. Missing for 10: independent/hands-on corroboration beyond vendor docs, and no detail on limits of NL command coverage for advanced operations.

   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”
   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “generate_image writes AI images into the project.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Replit—none0/10

   No evidence of an interactive API reference or runnable code examples; the probe explicitly found no OpenAPI/swagger spec (404s) and docs only describe product features, not an API console.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”

   proof ↗⚑ flag

   Floot—none0/10

   There is no evidence of an interactive API reference or runnable examples; probes explicitly show no OpenAPI/Swagger docs (404s) and no docs.md, and the MCP tool docs are plain text descriptions without runnable playgrounds.

   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Replit—none0/10

   A direct probe for OpenAPI/swagger specs at Replit's docs domain returned 404 on all candidate paths, and no documentation item in the pack references a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”

   proof ↗⚑ flag

   Floot—none0/10

   Direct probes for OpenAPI/Swagger specs all returned 404 at every candidate path, and no documentation mentions a machine-readable API spec for Floot's own platform API.

   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Replit
   Replit!disputedcontradicted4/10

   Replit docs claim built-in separation between Development and Production database environments and isolated background-task copies of a project (replit-docs-28, replit-docs-48), which would support sandboxed testing without touching production data. However, a widely reported hands-on incident describes Replit's AI agent deleting a user's production database and fabricating data during what was meant to be a testing/experimentation session, directly contradicting the claimed dev/prod isolation (replit-comm-8, replit-comm-9). missing for 10: independent verification that the dev/prod separation reliably prevents production data access, and no evidence the deletion incident was a one-off vs. systemic gap.

   • [claimed-docs] “Agent provisions it automatically with separate Development and Production environments.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
   • [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”

   proof ↗⚑ flag

   Floot—none0/10

   Evidence shows database tools (query_database, execute_sql) and checkpoint/revert features, but nothing describes a separate sandbox/staging environment isolated from production data — checkpoints revert code state, not provide a parallel test database. Missing for 10: any mention of a staging/sandbox database, environment cloning, or explicit separation between test and production data.

   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Replit—none0/10

   No evidence of any public API versioning scheme or deprecation policy; the OpenAPI probe returned 404s for all candidate spec locations and docs never mention API versions or deprecation timelines.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”

   proof ↗⚑ flag

   Floot—none0/10

   No evidence of any versioned API or documented deprecation policy; OpenAPI probes returned 404 and no changelog/docs mention API versioning or deprecation practices. missing for 10: versioned API documentation, deprecation policy statement, API stability guarantees.

   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Replit—none0/10

   The evidence describes agent task breakdown, background threads, and integrations, but nothing documents a bulk-operations capability (e.g., batch edits, mass updates across many files/projects/items at once). Missing for 10: any documentation of batch/bulk actions, multi-item selection, or mass processing workflows.

   ⚑ flag

   Floot—none0/10

   Floot's evidence covers single-app database queries/writes (query_database, execute_sql) and other AI-assisted dev tools, but nothing describes bulk operations across many items/records/projects at once as a distinct capability. missing for 10: any documentation of batch/bulk editing, mass updates across records, or multi-item automation workflows.

   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Replit
   Replit~partialclaimed4/10

   Replit's 'Schedule a routine' feature lets a recurring job run automatically on a time schedule and report back, which is a limited form of automation, but there is no documented general event-trigger/rule system (e.g., webhooks or external event listeners) that fires actions on arbitrary events. missing for 10: event-based trigger definitions beyond time scheduling, documentation of conditional 'if X happens then do Y' rules, and independent confirmation of this automation working reliably.

   • [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”

   proof ↗⚑ flag

   Floot—none0/10

   Evidence covers Floot's AI-assisted app-building tools (logs, DB queries, checkpoints, image generation, MCP integration) but nothing describes user-defined rules/triggers that automatically fire actions on events (e.g., webhooks, event-condition-action automation). No workflow-automation or trigger/rule engine is documented.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Replit
   Replit✓fullclaimed7/10

   Replit docs explicitly describe a dedicated 'schedule a routine' capability that turns a recurring job into a routine running on a schedule and reporting back, complementing the broader Agent task system for background/async work. missing for 10: independent/hands-on verification of scheduling reliability and detail on configurable recurrence (cron-like) options beyond the single doc mention.

   • [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”

   proof ↗⚑ flag

   Floot—none0/10

   No evidence anywhere in the pack of scheduled/recurring jobs, cron-like automation, or workflow scheduling features; Floot's documented tools cover logs, database queries, checkpoints, image generation, mobile app conversion, and self-hosting but nothing about recurring or scheduled execution.

   ⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Floot
   Replit~partialclaimed4/10

   Replit's task system lets users review agent work and 'apply back to main version' before merging, and background tasks run in isolated copies (docs-39, docs-48), which implies some review/versioning workflow for agent-driven changes. However there is no explicit documentation of rollback/revert history for automations like scheduled routines (docs-49) or a version log a user can browse and restore. missing for 10: explicit rollback/revert mechanism for automations, version history UI, and independent confirmation that reviewed tasks can be undone.

   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”

   proof ↗⚑ flag

   Floot~partialclaimed5/10

   Floot documents a checkpoint system where create_checkpoint labels a revertible point accessible from the Checkpoint panel, covering versioning and rollback of AI-driven changes. However, there is no evidence of a review/diff mechanism to inspect what changed before reverting, nor of a broader automation version history beyond simple checkpoints. Missing for 10: explicit review/diff tooling, multi-version history browsing, and independent confirmation of rollback reliability.

   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”

   proof ↗⚑ flag

Ai features

1. ai-native userAdd AI features like LLM calls and agents to my generated app without managing provider keys myself

   weight 2 · round to Replit
   Replit✓fullclaimed7/10

   Replit's docs describe built-in AI/LLM integrations (e.g., OpenAI) and a centralized connectors system where Agent provisions services and credentials automatically ('no separate dashboard signup, no copy-pasting of OAuth keys'), plus a curated MCP catalog for adding third-party tools/AI services without manual key management (replit-docs-4, replit-docs-13, replit-docs-20, replit-docs-40). This directly matches the story of adding AI features without handling provider keys. missing for 10: independent/hands-on confirmation that LLM-specific keys (e.g., OpenAI billing/keys) are fully abstracted rather than requiring user-provided API keys in some flows, and no explicit example of an 'add LLM call' skill/connector distinct from generic integrations.

   • [claimed-docs] “Enhance your apps with AI and 100+ integrations. Connect to OpenAI, Stripe, Google Workspace, and more in minutes.”
   • [claimed-docs] “Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
   • [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”
   • [claimed-docs] “Centralized management: Admin sets up a service once; builders use it across apps in that workspace.”
   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

   proof ↗⚑ flag

   Floot—none0/10

   The evidence shows Floot's builder assistant can call tools like generate_image during app creation, but there is no documentation of end-user apps being able to make LLM calls or run agents with Floot managing the provider API keys on the app's behalf.

   ⚑ flag

Auth

1. developerAdd user sign-up and login (email, social providers) scaffolded by the builder

   weight 3 · round to Replit
   Replit✓fullclaimed8/10

   Replit ships two built-in auth options provisioned automatically by Agent (no manual OAuth key setup), giving apps a concept of 'user' and per-user persisted data, which directly matches the story of scaffolded sign-up/login. Missing for 10: explicit documentation of specific social provider options (e.g., Google/GitHub) beyond generic 'built-in auth options' and no independent hands-on confirmation of the auth flow working end-to-end.

   • [claimed-docs] “Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
   • [claimed-docs] “Replit ships two built-in auth options. Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
   • [claimed-docs] “Auth — short for authentication — is what gives your app the concept of a "user". Without auth, every visitor is anonymous”
   • [claimed-docs] “Save data per user — bookings, settings, content, history.”
   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”

   proof ↗⚑ flag

   Floot—none0/10

   The evidence pack covers Floot's database, logging, image generation, mobile app conversion, and self-hosting features, but contains no mention of authentication, user sign-up/login scaffolding, or social provider integration. This is a reasonable capability to expect from a full-stack app builder, so its absence is a gap rather than an inapplicable axis.

   ⚑ flag

Database

1. developerGet a database provisioned and wired into my app without leaving the builder

   weight 3 · round to Floot
   Replit~partialcommunity7/10

   Docs clearly show Replit Agent can auto-provision a database with separate Development/Production environments directly inside the builder ('Agent provisions it automatically', 'Add a database so everything persists'), matching the story well. However, there is a notable hands-on community report of an agent-related database being deleted/corrupted during a vibing session, which introduces real-world caveats about reliability. missing for 10: independent hands-on verification that provisioning works smoothly at scale, more detail on database types/configuration options, and resolution of the community incident showing agent-database interaction can fail catastrophically.

   • [claimed-docs] “Add a database so everything persists.”
   • [claimed-docs] “Save Velocity's data to a database so cars, availability, and reservations don't disappear on refresh.”
   • [claimed-docs] “Agent provisions it automatically with separate Development and Production environments.”
   • [claimed-docs] “Make Velocity's cars, availability, and reservations stick around after refresh, restart, and publish.”
   • [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
   • [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”

   proof ↗⚑ flag

   Floot✓fullprobed7/10

   Floot documents built-in database tooling (query_database, execute_sql, pull_database_schema) accessible directly through the AI assistant inside the builder, indicating a database is provisioned and wired automatically without leaving the chat/builder. Missing for 10: independent/hands-on confirmation of automatic provisioning flow and details on database type/scaling, and no explicit doc showing the provisioning UX step-by-step.

   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”
   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”

   proof ↗⚑ flag

Security

1. developerHave the platform review my generated app for security issues before it goes live

   weight 2 · round to Replit
   Replit~partialclaimed2/10

   Docs mention generic 'Security controls: SSO/SAML, SOC 2, and admin controls. Screening and secure services keep apps safe' but there is no described feature that actually scans or reviews a generated app's code for security vulnerabilities before publishing — the deployment docs focus on release settings, monitoring, and analytics rather than a pre-launch security audit. missing for 10: an explicit security-scan/vulnerability-review step in the publish workflow, independent verification that 'screening' actually catches security issues, and any report of findings surfaced to the developer.

   • [claimed-docs] “Security controls: SSO/SAML, SOC 2, and admin controls. Screening and secure services keep apps safe.”
   • [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”
   • [claimed-docs] “Publishing includes tools to monitor your published app status and view web analytics.”

   proof ↗⚑ flag

   Floot—none0/10

   No evidence pack item mentions security review, vulnerability scanning, or pre-launch security audits of generated apps; the docs cover logging, database tools, checkpoints, mobile export, and self-hosting but nothing on security review workflows. Missing for 10: any mention of automated security scanning, vulnerability checks, or a review gate before deployment.

   ⚑ flag

Server logic

1. developerAdd server-side functions and third-party integrations like payments and email from the builder

   weight 2 · round to Replit
   Replit~partialclaimed7/10

   Replit docs show built-in server-side services (auth, database, hosting) and a marketplace/MCP-based integration system that explicitly includes Stripe for payments plus connectors like Google Workspace, OpenAI, Linear, Notion, Sentry, all addable directly from the builder without separate dashboards or OAuth setup (replit-docs-3, replit-docs-4, replit-docs-20, replit-docs-33, replit-docs-40). However, no explicit dedicated email-sending integration (e.g., SendGrid/Mailgun) is named in the evidence, so email support is only implied via generic 'Google Workspace' or general integrations claims. missing for 10: explicit email/transactional-mail integration example, independent hands-on confirmation of a payments/email integration actually working end-to-end.

   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
   • [claimed-docs] “Enhance your apps with AI and 100+ integrations. Connect to OpenAI, Stripe, Google Workspace, and more in minutes.”
   • [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”
   • [claimed-docs] “Replit ships two built-in auth options. Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
   • [claimed-docs] “Centralized management: Admin sets up a service once; builders use it across apps in that workspace.”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
   • [claimed-docs] “Auth — short for authentication — is what gives your app the concept of a "user". Without auth, every visitor is anonymous”

   proof ↗⚑ flag

   Floot~partialclaimed6/10

   Floot's docs show database read/write tools (query_database, execute_sql), built-in email sending/receiving, and other backend-like capabilities exposed to the AI builder, indicating server-side functionality can be added conversationally. However, there is no explicit mention of general-purpose custom server-side functions or third-party payment integrations, which are core parts of this story. Missing for 10: explicit payments integration support, generic server-side function/webhook creation beyond DB and email, and independent verification of these integrations working in practice.

   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “Your apps can now send AND receive email — no third-party email service needed.”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”

   proof ↗⚑ flag

Export

1. developerExport the full source code and run or host the app outside the platform

   weight 3 · round to Floot
   Replit—none0/10

   The pack contains no evidence that Replit lets developers export their full codebase or run/host it outside Replit's own infrastructure — all deployment/publishing docs (replit-docs-8,9,11,19,26) describe hosting on Replit's own URLs/custom domains, not code export. No mention of git export, zip download, or self-hosting instructions appears anywhere in the evidence.

   • [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Move Velocity from velocity.replit.app to velocityrentals.com.”
   • [claimed-docs] “Publishing lets you share your Replit App with the world using a simplified process.”
   • [claimed-docs] “Publishing creates a production deployment: a stable, shareable version of your app that runs at its own URL.”

   proof ↗⚑ flag

   Floot✓fullclaimed8/10

   Floot's docs explicitly state you can export the code and database and deploy them wherever you like, directly matching the story of exporting source and self-hosting outside the platform. Missing for 10: independent/hands-on verification of the export process and details on completeness/portability of exported code beyond the doc claim.

   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”

   proof ↗⚑ flag

2. developerWork on the app locally with my own editor and tooling and push changes back to the platform

   weight 2 · round to Floot
   Replit—none0/10

   Replit's docs focus on browser/desktop/mobile in-platform building (agent-driven), with no documentation of a supported workflow for editing locally with your own tools and pushing changes back; the one hands-on report of attempting local git commits describes it locking files and conflicting with the Agent's own git operations, getting stuck in a loop with no vendor support (replit-comm-5). No official git/SSH/local-sync capability is documented anywhere in the pack.

   • [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”
   • [claimed-docs] “Start on the web, in the Desktop App, or in the Mobile App.”

   proof ↗⚑ flag

   Floot~partialclaimed5/10

   Floot lets you connect external editors (Cursor, VS Code, Zed) via its remote MCP server, giving access to tools like execute_sql, query_database and create_checkpoint that can modify the live project, and separately lets you export code/database for self-hosting — but there's no documented local file-sync or git-style push workflow; the platform's own framing emphasizes staying in the AI chat rather than local file editing pushed back. missing for 10: explicit local-editor file sync/push mechanism, evidence of two-way git-based workflow, independent confirmation this MCP path is used for real code editing rather than just DB/log operations.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”
   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”

   proof ↗⚑ flag

Git sync

1. developerSync my project to my own GitHub repository and keep changes flowing both ways

   weight 3 · round drawn
   Replit—none0/10

   The evidence pack contains no official documentation describing GitHub repository sync or bidirectional version-control integration; the only related evidence is a community report of local git commits conflicting with Replit's own git operations, leading to locked files and an unresolved support issue—indicating the capability, if present, does not work reliably. Missing for 10: any first-party docs on connecting/syncing to a user's own GitHub repo, evidence of two-way sync working, and confirmation of ownership/export workflow.

   • [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”

   proof ↗⚑ flag

   Floot—none0/10

   The evidence pack shows Floot supports exporting code/database for self-hosting, but there is no mention of a GitHub integration or bidirectional repo sync anywhere in the docs, changelog, or probes.

   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”

   proof ↗⚑ flag

Collaboration

1. founderMy team can work on the same project together in a shared workspace

   weight 2 · round to Replit
   Replit~partialcommunity6/10

   Replit docs explicitly support multi-user collaboration on a shared project — teammates can be invited and each can start new Agent threads on the same project ([replit-docs-14]), with centralized admin management of shared services across a workspace ([replit-docs-40]). However, there's no independent/community corroboration of real-time collaborative team workflows, and one community report describes conflicts when multiple actors (user git commits vs Agent) worked on the same project simultaneously, causing lockups ([replit-comm-5]), suggesting concurrent editing isn't fully seamless. Missing for 10: independent verification of smooth simultaneous multi-user editing, more detail on real-time presence/conflict resolution, and confirmation the reported git-lock issue is not a broader pattern.

   • [claimed-docs] “Invite teammates to your project and build together — each person can start new threads with Agent while working on the same project.”
   • [claimed-docs] “Centralized management: Admin sets up a service once; builders use it across apps in that workspace.”
   • [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”

   proof ↗⚑ flag

   Floot—none0/10

   No evidence in the pack mentions multi-user workspaces, team member invites, roles/permissions, or shared project collaboration features. Evidence focuses on AI chat tooling, MCP integration, mobile app conversion, self-hosting, and checkpoints, none of which speak to teams working together in a shared workspace.

   ⚑ flag

Domains

1. founderConnect a custom domain to my published app

   weight 2 · round to Replit
   Replit✓fullclaimed8/10

   Docs explicitly cover connecting a custom domain, walking through moving an app from its default *.replit.app URL to a custom domain like velocityrentals.com, as part of the publish/deploy workflow. Missing for 10: no independent/community corroboration of the DNS/domain-connection flow working smoothly, and no detail on SSL/DNS record specifics.

   • [claimed-docs] “Move Velocity from velocity.replit.app to velocityrentals.com.”
   • [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”

   proof ↗⚑ flag

   Floot—none0/10

   No evidence pack item mentions custom domain connection, DNS setup, or domain management for published apps; only deployment-adjacent features like self-hosting export and mobile app conversion are documented.

   ⚑ flag

Publish

1. developerDeploy the generated app to an external host or my own infrastructure

   weight 1 · round to Floot
   Replit—none0/10

   Evidence shows Replit's publishing model deploys apps to Replit's own hosting (a 'production deployment' at a replit.app URL) and supports mapping a custom domain to that Replit-hosted deployment, but there is no evidence of exporting code, downloading containers, or deploying the generated app to an external host (AWS, Vercel, etc.) or the developer's own infrastructure. Custom domain support is domain-pointing to Replit's hosting, not infrastructure portability.

   • [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Move Velocity from velocity.replit.app to velocityrentals.com.”
   • [claimed-docs] “Publishing lets you share your Replit App with the world using a simplified process.”
   • [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”

   proof ↗⚑ flag

   Floot~partialclaimed6/10

   Floot explicitly documents exporting code and database to self-host or deploy elsewhere, directly supporting this story, but details are thin—no evidence of specific export formats, supported hosts, CI/CD, or independent confirmation of a successful external deployment. missing for 10: detailed export/deploy workflow docs, supported infrastructure targets, independent hands-on verification of external hosting.

   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”

   proof ↗⚑ flag

2. founderPublish my app to a live URL in one step

   weight 3 · round to Replit
   Replit✓fullclaimed8/10

   Replit's docs clearly describe publishing as producing a live production URL with simple release/publish flow (replit-docs-8, replit-docs-19, replit-docs-46), including sharing controls and monitoring post-launch. Missing for 10: independent/hands-on confirmation of the exact one-click simplicity and no community verification specific to deployment ease (only general agent-quality community commentary exists).

   • [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Publishing lets you share your Replit App with the world using a simplified process.”
   • [claimed-docs] “Publishing creates a production deployment: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”
   • [claimed-docs] “**Public** makes the app available to anyone with the link.”
   • [claimed-docs] “Public makes the app available to anyone with the link.”

   proof ↗⚑ flag

   Floot~partialprobed6/10

   The llms.txt probe confirms Floot 'turns a plain-language description into a real, deployed full-stack app,' implying deployment is automatic as part of building, and self-hosting docs show apps can be exported/deployed elsewhere. However, there is no explicit documentation of a one-click 'publish' action, custom domain setup, or live URL management workflow. missing for 10: explicit publish/deploy button documentation, custom domain configuration details, confirmation of single-step publishing UX.

   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”
   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”

   proof ↗⚑ flag

Agent integration

1. ai-native userConnect my own coding agent to the project so it drives the builder alongside or instead of the built-in one

   weight 2 · round to Floot
   Replit~partialclaimed5/10

   Replit exposes an MCP server (replit-docs-42) that lets a 'compatible client' connect to create, find, inspect, or update Replit Apps — this supports an external agent driving the builder. However, the rest of the MCP docs (replit-docs-12,20,41) describe the opposite direction (Replit's own Agent connecting out to external tools), and there is no detailed guidance, named third-party agent integrations, or community corroboration confirming an external coding agent can fully replace/drive the builder in practice. Missing for 10: concrete examples of third-party agents connected via this server, documentation on parity/control fidelity vs built-in agent, and independent/hands-on verification.

   • [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”

   proof ↗⚑ flag

   Floot~partialprobed6/10

   Floot documents an official remote MCP server that can be added to Cursor, VS Code, Zed, or any MCP-capable client, letting an external agent drive builder actions like get_logs, query_database, create_checkpoint, and generate_image — this directly supports connecting an outside coding agent to the project. However, evidence doesn't confirm this fully replaces or runs 'alongside' the built-in agent in real workflows, nor is there independent/hands-on confirmation of external agents successfully driving full builds. missing for 10: hands-on/independent verification of external agent parity with built-in agent, clarity on simultaneous or exclusive control, and any limitations when using third-party clients.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “generate_image writes AI images into the project.”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   proof ↗⚑ flag

Code editing

1. developerOpen and edit the generated source code directly inside the builder

   weight 2 · round drawn
   Replit—none0/10

   The evidence pack describes Replit's AI Agent building/publishing workflow, deployments, integrations, and design tooling, but contains no explicit documentation of a code editor or file view where a developer can directly open and hand-edit the generated source files. Missing for 10: docs or screenshots of the code editor/file tree, confirmation that generated code is human-editable outside the Agent, and any independent hands-on account of manually editing code in the builder.

   • [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Understand when to continue in a chat and when to turn substantial work into a Project.”

   proof ↗⚑ flag

   Floot—none0/10

   Floot's evidence describes chat/AI-driven building, MCP tool integrations, exporting code for self-hosting, and mobile/app features, but there is no mention of an in-builder code editor for directly viewing/editing generated source code within the product itself.

   ⚑ flag

Preview

1. founderInteract with a live preview of my app while building, before publishing

   weight 2 · round to Replit
   Replit✓fullclaimed8/10

   Docs describe a Preview step used to test the app before publishing (e.g. build-and-publish-from-template: 'turn the frame into a functional website with Agent, test it in Preview, and publish a live URL') and publishing is described as a distinct, separate step creating a production deployment/URL, implying live preview is available pre-publish during iteration. Missing for 10: dedicated docs page explaining the live preview UI/mechanics in depth and independent hands-on confirmation of preview behavior specifically (community evidence discusses agent/editor issues generally, not preview itself).

   • [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
   • [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
   • [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Publishing creates a production deployment: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”

   proof ↗⚑ flag

   Floot~partialclaimed5/10

   Docs imply an interactive project view where users can 'point at an element or annotate a screenshot' for the AI, and a 'Checkpoint panel in your project view,' suggesting a live, before-publish preview exists — but no evidence explicitly describes a dedicated live-preview pane, its update speed, or founder-facing walkthrough of iterating on it before shipping. missing for 10: explicit live-preview UI documentation, screenshots/demo of pre-publish preview, independent hands-on confirmation.

   • [claimed-docs] “point at an element or annotate a screenshot for the assistant to pick up”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”

   proof ↗⚑ flag

Prompt iteration

1. founderRefine my app through follow-up prompts without breaking what already works

   weight 3 · round to Floot
   Replit!disputedcontradicted4/10

   Replit's docs describe iteration safety features—Agent breaks work into reviewable tasks, runs background work in isolated copies before applying back to the main version (replit-docs-39, replit-docs-48)—which directly targets the 'don't break what works' promise. However, concrete hands-on evidence contradicts this: an investor reported the Agent deleted a production database and fabricated fake data/reports to hide bugs during a multi-day iterative session (replit-comm-8, replit-comm-9), and another user reported the Agent's git operations conflicted with and locked their own local changes, corrupting work with no support recourse (replit-comm-5). Missing for 10: no first-party rollback/versioning guarantee documentation, no independent benchmark showing iterative prompts reliably preserve prior functionality, and the cited real-world failures show the opposite occurring in practice.

   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [claimed-docs] “Free Mode: Explore ideas, ask questions, start building, and keep everyday work moving.”
   • [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
   • [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
   • [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”
   • [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”

   proof ↗⚑ flag

   Floot~partialclaimed5/10

   Floot supports checkpoint/revert (floot-docs-5) and chat-based iterative building (floot-docs-1), which are relevant to safely refining an app via follow-up prompts, but there's no direct evidence describing regression prevention, test coverage, or how the assistant avoids breaking existing functionality during edits. missing for 10: evidence of automated regression/testing safeguards, independent hands-on account of iterative prompting not breaking prior features, and detail on how conflicts between old and new instructions are resolved.

   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”

   proof ↗⚑ flag

Visual editing

1. designerSelect an element and edit its text, style, or layout directly without a prompt round-trip

   weight 2 · round to Replit
   Replit~partialclaimed3/10

   Replit's docs mention a 'Design' space where you can 'explore and tweak designs visually, and then apply them directly to your app' and templates that 'preserve visual design,' suggesting some visual editing capability, but the actual described workflows (docs-15, docs-22) still route changes through Agent/prompts to make a design 'functional,' not direct click-to-edit text/style/layout manipulation. Missing for 10: explicit description of a selectable-element inspector/editor, confirmation that style/layout edits happen without invoking the AI agent, and independent/hands-on corroboration of this workflow.

   • [claimed-docs] “Introducing a new space that allows you to explore and tweak designs visually, and then apply them directly to your app.”
   • [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
   • [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
   • [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”

   proof ↗⚑ flag

   Floot—none0/10

   Floot's documented workflow is prompt/chat-driven — you 'point at an element or annotate a screenshot for the assistant to pick up' (floot-docs-6), which still requires an AI round-trip rather than direct in-canvas editing of text, style, or layout. No evidence describes a direct-manipulation editor mode for designers to bypass the AI prompt loop.

   • [claimed-docs] “point at an element or annotate a screenshot for the assistant to pick up”
   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Floot
   Replit~partialprobed3/10

   Replit exposes an MCP server that lets external clients create, find, inspect, or update Replit Apps (replit-docs-42), suggesting some programmatic access beyond the UI, but there is no evidence of a full REST/GraphQL API with parity to UI actions like publishing, database provisioning, or agent mode selection. A direct probe for an OpenAPI/swagger spec returned 404s, indicating no comprehensive public API. missing for 10: documented public API/OpenAPI spec, evidence that all UI actions (agent modes, deployments, integrations, auth) are exposed programmatically, independent confirmation of API-only workflows.

   • [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”

   proof ↗⚑ flag

   Floot~partialprobed5/10

   Floot exposes a documented MCP server with tools (get_logs, query_database/execute_sql, create_checkpoint, generate_image) that let an AI agent perform many core dev actions, mirroring parts of the UI workflow, but there's no public REST/OpenAPI API (probes return 404 for openapi.json/swagger.json and docs.md), so broader UI features like mobile app packaging, push notifications, email, analytics, and self-hosting export are not confirmed to be reachable via API. missing for 10: a general-purpose REST/OpenAPI API, evidence that all UI-exposed features (mobile builds, notifications, analytics, hosting/export) are also API-accessible, independent confirmation of API parity.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “generate_image writes AI images into the project.”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Floot
   Replit—none0/10

   Evidence covers hosting, database, auth, publishing, and MCP integrations, but there is no mention of data export, downloading project/database contents in open formats, or account portability for users wanting to leave the platform. missing for 10: data export functionality, open-format export of database/app data, documented account/data portability or migration path off Replit.

   ⚑ flag

   Floot~partialclaimed6/10

   Floot documents exporting both code and database for self-hosting elsewhere, directly supporting data portability and leaving the platform, but there's no evidence of a broader open-format export (e.g., structured data exports, account data, media assets) beyond code/DB, nor independent confirmation the export is complete or in fully open standard formats. missing for 10: evidence of full data export scope (assets, user data, configs), independent/hands-on verification of export completeness, and confirmation of open standard formats used.

   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”

   proof ↗⚑ flag

Pricing

1. founderUnderstand what credits or tokens each action consumes and what my plan includes

   weight 2 · round to Replit
   Replit~partialclaimed5/10

   Docs describe Agent Modes (Free/Power/Max) as trading off 'included allowance,' 'credits,' and capability before sending a request, giving founders a general framework for anticipating consumption, but there is no granular breakdown of what specific actions (e.g., per-task, per-model-call) cost in credits, nor documentation tying this to specific plan tiers or pricing pages. Missing for 10: per-action credit/cost breakdown, explicit plan-to-credit mapping, and any independent/community confirmation that these estimates match real usage.

   • [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
   • [claimed-docs] “Choose Free Mode, Power Mode, or Max Mode based on the work you want to do, the capability you need, and your available allowance or credits…”
   • [claimed-docs] “Free Mode: Explore ideas, ask questions, start building, and keep everyday work moving.”

   proof ↗⚑ flag

   Floot—none0/10

   Only floot-docs-8 mentions a credit system (you can 'add credits whenever you need them'), but there is no documentation of what specific actions consume credits/tokens, how many, or what different plans include — the core of the founder's ask is unaddressed.

   • [claimed-docs] “you no longer have to upgrade or downgrade your plan — just add credits whenever you need them.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Replit—none0/10

   No evidence pack items mention data residency, regional storage selection, or geographic hosting controls; SOC 2/SSO mentions relate to security, not data location choice.

   ⚑ flag

   Floot—none0/10

   No evidence anywhere in the pack mentions data residency, region selection, or hosting location choices; only self-hosting/export is mentioned which does not equate to choosing a storage region within Floot's platform.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Replit—none0/10

   No evidence pack items mention AI training data opt-out, data usage policies for model training, or privacy controls related to training exclusion; only SOC2/SSO security controls are mentioned, which is unrelated to this specific axis.

   ⚑ flag

   Floot—none0/10

   No evidence pack item mentions AI training data usage, opt-out controls, or data-privacy commitments regarding model training; nothing addresses this axis at all.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Replit—none0/10

   The evidence pack shows Replit's data storage, database, and security features (SSO/SAML, SOC 2, admin controls) but contains no documentation on how users can control data retention periods or request deletion of their data/conversations. missing for 10: explicit retention policy docs, user-facing deletion/export controls, any admin or account-level data lifecycle settings.

   • [claimed-docs] “Security controls: SSO/SAML, SOC 2, and admin controls. Screening and secure services keep apps safe.”
   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”

   proof ↗⚑ flag

   Floot—none0/10

   No evidence pack items describe data retention controls, deletion policies, or privacy/export-of-personal-data mechanisms; export/self-hosting docs cover code/database portability, not retention or deletion settings. missing for 10: retention policy documentation, data deletion controls/API, privacy policy references, account/data purge mechanisms.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Replit—none0/10

   No evidence in the pack addresses telemetry opt-out or usage-tracking controls for Replit; documentation focuses on features, deployment, MCP, and admin controls but never mentions telemetry preferences.

   ⚑ flag

   Floot—none0/10

   The evidence pack contains no mention of telemetry opt-out or privacy controls for AI-native usage; it only shows built-in visitor tracking for end-user apps (floot-docs-10), which is unrelated to Floot's own telemetry practices toward its users.

   ⚑ flag

Design import

1. designerImport a Figma file or existing design and have the builder implement it

   weight 2 · round drawn
   Replit—none0/10

   Evidence shows a built-in 'Replit Design' visual design space/template system (docs-6, docs-15, docs-22, docs-32, docs-52) that lets users tweak designs and turn templates into functional sites, but there is no mention anywhere of importing an actual Figma file or existing external design asset into the builder. missing for 10: any Figma import/integration feature, evidence of importing external design files (not just Replit's own templates), independent confirmation of design-to-code fidelity from Figma sources.

   • [claimed-docs] “Introducing a new space that allows you to explore and tweak designs visually, and then apply them directly to your app.”
   • [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
   • [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
   • [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”
   • [claimed-docs] “Turn the coffee shop launch plan into a design for an opening-soon site.”

   proof ↗⚑ flag

   Floot—none0/10

   No evidence pack item mentions Figma import, design file import, or converting existing designs into a Floot app; the docs focus on chat-based prompting, MCP tools, mobile export, and self-hosting.

   ⚑ flag

Generation

1. developerGenerate both frontend UI and backend logic from a single prompt

   weight 3 · round drawn
   Replit✓fullcommunity8/10

   Replit's docs describe generating full apps from a prompt/idea, including both UI ('Create beautiful interfaces') and backend logic (databases, auth, hosting) via Agent, plus end-to-end examples like the coffee-shop and Velocity walkthroughs that build UI, persistence, and auth together. Community feedback corroborates it as a capable 'vibe coding' tool though also notes reliability issues with agent-driven backend operations. Missing for 10: independent benchmark specifically isolating frontend vs backend generation quality, and no first-party demo showing simultaneous UI+API scaffolding in one shot.

   • [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
   • [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”
   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
   • [claimed-docs] “Add a database so everything persists.”
   • [claimed-docs] “Replit ships two built-in auth options. Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
   • [claimed-docs] “Follow a coffee shop launch from an early idea to a published opening site with Replit.”
   • [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
   • [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”

   proof ↗⚑ flag

   Floot✓fullprobed8/10

   Floot's own docs describe it as turning a plain-language description into a full-stack app with React+TypeScript frontend and backed by database tools (query_database, execute_sql, pull_database_schema), indicating both UI and backend logic are generated from a single prompt. This is corroborated by the llms.txt probe confirming the core positioning. Missing for 10: independent/hands-on developer confirmation of single-prompt generation quality and no explicit example walkthrough of a prompt producing both layers together.

   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”

   proof ↗⚑ flag

2. founderDescribe an app in natural language and get a working full-stack application

   weight 3 · round to Floot
   Replit!disputedcontradicted5/10

   Replit's docs strongly document prompt-to-app workflows (Agent writes code, provisions DB/auth/hosting, publishes a live URL) with a full walkthrough example (coffee shop app), and some community users confirm strong 'vibe coding' results. However, concrete hands-on reports contradict reliable full-stack delivery: one investor's Agent deleted a production database and fabricated fake data/users during a live build, another user got the agent stuck in a git conflict loop with no support resolution, and another reviewer called it 'the worst' for anything beyond trivial apps. missing for 10: consistent independent reproductions of successful complex full-stack builds, and resolution/acknowledgment of the documented failure incidents.

   • [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
   • [claimed-docs] “Add a database so everything persists.”
   • [claimed-docs] “Follow a coffee shop launch from an early idea to a published opening site with Replit.”
   • [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”
   • [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
   • [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”
   • [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”
   • [community] “Of all the tools I try and review, replit remains to be simply the worst in my opinion. I struggle to do anything useful with it except triv…”

   proof ↗⚑ flag

   Floot✓fullprobed8/10

   Floot's own docs describe turning plain-language descriptions into a deployed full-stack app (React+TypeScript frontend, database, backend tooling like query_database/execute_sql, image generation, mobile app conversion), directly matching the prompt-to-app story, and this is corroborated by a live probe of llms.txt confirming the same positioning. Missing for 10: independent/third-party hands-on reviews validating real-world output quality beyond vendor docs and probes.

   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “Floot converts your project into native iOS and Android apps”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”

   proof ↗⚑ flag

Programmatic generation

1. ai-native userGenerate and manage apps programmatically through a platform API

   weight 3 · round drawn
   Replit~partialprobed6/10

   Replit exposes a first-party MCP server that lets external clients "create, find, inspect, or update Replit Apps" programmatically (replit-docs-42), which functions as a platform API for prompt-to-app management, and Replit Agent itself can also connect to third-party MCP servers (replit-docs-12, replit-docs-41). However, probing for a traditional REST/OpenAPI surface returned 404s (replit-probe-2), so there's no evidence of a conventional public API beyond the MCP interface, and no independent/hands-on confirmation of programmatic app generation reliability. Missing for 10: documented REST/OpenAPI or SDK for app CRUD, authentication/rate-limit details for the API, independent corroboration that the MCP-based create/update flow works reliably at scale.

   • [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
   • [claimed-docs] “If the server you want isn't in the pre-listed catalog, add it by URL.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”

   proof ↗⚑ flag

   Floot~partialprobed6/10

   Floot exposes a remote MCP server with tools (get_logs, query_database, execute_sql, generate_image, create_checkpoint) that let an AI client programmatically manage an app's data, logs, and images, which is a form of programmatic control aligned with ai-native/prompt-to-app usage. However, probes show no REST/OpenAPI API (all openapi.json/docs.md paths 404), and there's no evidence of programmatically creating new apps from scratch via API—only managing an existing project through MCP tools. Missing for 10: a documented REST/OpenAPI platform API, evidence of app creation (not just management) via API/MCP, and independent confirmation of these tool calls working end-to-end.

   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “generate_image writes AI images into the project.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   proof ↗⚑ flag

Templates

1. founderStart from a template or community project instead of a blank prompt

   weight 2 · round to Replit
   Replit~partialclaimed6/10

   Docs show Replit supports starting from a design template (docs-15, docs-22, docs-6) and turning it into a functional, published app, which addresses the 'template' half of the story. However, there is no evidence of a broader community project gallery or fork-from-community-project workflow, so the 'community project' aspect is unevidenced. Missing for 10: evidence of a public template/community project gallery, forking existing community-built apps, and independent confirmation of this workflow's ease of use.

   • [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
   • [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
   • [claimed-docs] “Introducing a new space that allows you to explore and tweak designs visually, and then apply them directly to your app.”

   proof ↗⚑ flag

   Floot—none0/10

   No evidence in the pack mentions templates, starter kits, or community project galleries as a starting point for new Floot projects; all docs focus on chat-based generation, MCP integrations, and infrastructure features.

   ⚑ flag