Gesamtwert der KI-Bereitschaft
Zusammengefasster Wert aus allen Auditsignalen.
Gesamtwert der KI-Bereitschaft
Zusammengefasster Wert aus allen Auditsignalen.
Gesamtbewertung der KI-Bereitschaft
carbonforge.dev (carbonforge.dev) erreichte im automatisierten technischen Audit 86/100 Punkte bei der KI-Bereitschaft. llms.txt war erreichbar, llms-full.txt hatte keine erreichbare Datei und ai.txt war nicht auffindbar. Die robots.txt-Analyse ergab 11 ausdrücklich erlaubte und 0 blockierte KI-Crawler sowie 1 deklarierte Sitemap. Die Vollständigkeit des Homepage-Markups lag bei 90%; erkannte Schema.org-Typen: Organization, WebSite, SoftwareApplication. Erkannte OpenGraph-Tags: 9. Die Ergebnisse entsprechen den öffentlich erreichbaren Antworten der Website zum Prüfzeitpunkt 2026-10-28T21:22:20.125Z.
Die Prüfung kombiniert maschinenlesbare Dateien, Crawler-Regeln, Sitemaps und Homepage-Markup. llms.txt ist erreichbar und umfasst 1.247 Tokens.
robots.txt ist verfügbar; blockierte KI-Bots: 0. Deklarierte Sitemaps: 1. Schema.org-Typen: Organization, WebSite, SoftwareApplication.
Mobiles Lighthouse-Profil: Performance 100/100, Barrierefreiheit 100/100, SEO 100/100.
Eine mobile Lighthouse-Messung. Die experimentelle Kategorie Agentic Browsing wird separat gezeigt und ersetzt nicht den LLMSMap-Gesamtwert.
Performance
Barrierefreiheit
Best Practices
Technisches SEO
Agentic Browsing
Die mobile Seite wird effizient dargestellt; der größte sichtbare Inhalt erschien nach 0.9 s.
Barrierefreiheit: 100/100, Best Practices: 100/100, technisches SEO: 100/100. Die experimentelle Kategorie Agentic Browsing erreichte 100/100 und wird getrennt vom LLMSMap-Gesamtwert angezeigt.
Erster Inhalt
Hauptinhalt
Layout-Stabilität
Blockierzeit
Visuelle Geschwindigkeit
Maschinenlesbare Dateien, Crawler-Regeln, Discovery und Homepage-Markup.
Vollständige Version wurde nicht gefunden
ai.txt wurde nicht gefunden
1 Sitemap gefunden
Typen: Organization, WebSite, SoftwareApplication
9 OpenGraph-Tags gefunden
Basierend auf der robots.txt-Analyse
Deklarierte Discovery-Routen für Crawler und Agenten.
Auf der Startseite gefundene Metadaten für Social-Media-Vorschauen.
og:typewebsiteog:site_nameCarbon Forgeog:titleCarbon Forge — the record your agents read and writeog:descriptionCode, knowledge and the reason for every change in one sealed record that agents query with a call. Git is rendered from it.og:urlhttps://carbonforge.dev/og:localeen_USog:image:width1200og:image:height630Strukturierte Entitäten und Eigenschaften der Startseite.
name100monkeys AI, Inc.urlhttps://100monkeys.ailogohttps://100monkeys.ai/aegis-logo.pngsameAshttps://github.com/100monkeys-ai, https://www.linkedin.com/company/112423436/, https://x.com/100monkeysai, https://hashnode.com/@100monkeys-ai, https://medium.com/@jeshua_46811publisher100monkeys AI, Inc.descriptionThe sealed record of code and knowledge that agents read and write with a call. Git is rendered from it.# Carbon Forge > Carbon Forge keeps code, files and prose in one record on the server, and people and agents read and write it through the same tools. Agents reach it over MCP; git is rendered from the record for the tools that still speak git. Public workspaces are free, and every account includes one free private workspace. Carbon Forge is built by 100monkeys AI, Inc. on Carbon, the source-control model its docs describe. An agent opens a lane instead of cloning: a lane is a set of patches over the trunk, and every read on it composes the trunk as it stands now with those patches. Carbon Forge never merges text by itself; a patch that no longer applies is reported as a named conflict. A landing is one changeset: every page, atom, code tree and file it names is written in one transaction, or nothing is. Every revision and every changeset is hash-chained, and a revert is a new landing, so history only moves forward. Blame, grep, diff and history run on the server. The docs at https://carbonforge.dev/docs/p/ are rendered in the browser by the app, so this file links each page rather than reproducing it in an llms-full.txt. ## Site - [Carbon Forge](https://carbonforge.dev/): the record your agents read and write - [Pricing](https://carbonforge.dev/pricing): Free, Pro, Team and Enterprise plans - [Security](https://carbonforge.dev/security): a history you can verify - [Specification](https://carbonforge.dev/specification): the Carbon SCM specification - [Carbon Forge and AEGIS](https://carbonforge.dev/aegis) - [Comparisons](https://carbonforge.dev/compare): side by side, every row cited - [Sign in](https://carbonforge.dev/login): a one-time link by email, no passwords - [FAQ](https://carbonforge.dev/faq): short answers on agents sharing one codebase, shared memory, auditing agent changes, MCP for a knowledge base, and git for teams of agents - [Guides](https://carbonforge.dev/guides): step-by-step guides built from the docs - [Land a code change and its documentation in one changeset](https://carbonforge.dev/guides/code-and-docs-in-one-changeset): change code and its page on one lane and land both as one changeset - [Cut a release and push it to GitHub](https://carbonforge.dev/guides/cut-a-release-and-push-to-github): name a release with a cut, read its notes, render it as git and push fast-forward only - [Catch stale docs with governed seams](https://carbonforge.dev/guides/governed-seams-drift-report): declare which pages govern which code and read a drift report before a landing - [Connect Claude Code to Carbon Forge over MCP](https://carbonforge.dev/guides/claude-code-mcp): attach Claude Code with a scoped token so agents read, write and cite one record - [Conecta Claude Code a Carbon Forge por MCP](https://carbonforge.dev/guides/es/claude-code-mcp) (es): the same guide in Spanish - [Conecte o Claude Code ao Carbon Forge via MCP](https://carbonforge.dev/guides/pt/claude-code-mcp) (pt): the same guide in Portuguese - [Claude Code を MCP で Carbon Forge に接続する](https://carbonforge.dev/guides/ja/claude-code-mcp) (ja): the same guide in Japanese - [Connect Cursor, Codex and any MCP client](https://carbonforge.dev/guides/cursor-codex-mcp): one token per client and the exact configuration for each - [Agent sign-up skill](https://carbonforge.dev/skill): a Markdown skill an agent follows to create an instance for its user ## Docs - [Welcome to Carbon](https://carbonforge.dev/docs/p/home): the docs home - [Overview](https://carbonforge.dev/docs/p/overview): what Carbon Forge is and is not - [Source control on the substrate](https://carbonforge.dev/docs/p/features/source-control-on-the-substrate): the problem it solves and the design - [Working in lanes](https://carbonforge.dev/docs/p/guides/lanes) - [Code and files on the substrate](https://carbonforge.dev/docs/p/guides/code-and-files) - [Source control: how it is built and why](https://carbonforge.dev/docs/p/architecture/source-control) - [A shared cortex for LLMs](https://carbonforge.dev/docs/p/features/shared-cortex-for-llms): MCP as a primary product surface - [cortex.ground](https://carbonforge.dev/docs/p/guides/cortex-ground): how an agent orients itself - [MCP tools catalog](https://carbonforge.dev/docs/p/api/mcp-tools-catalog) - [Billing and plans](https://carbonforge.dev/docs/p/guides/billing-and-plans) ## Comparisons - [Carbon Forge vs GitHub](https://carbonforge.dev/compare/github) - [Carbon Forge vs GitLab](https://carbonforge.dev/compare/gitlab) - [Carbon Forge vs Notion](https://carbonforge.dev/compare/notion) - [Carbon Forge vs Obsidian](https://carbonforge.dev/compare/obsidian) - [Carbon Forge and AEGIS vs CI/CD platforms](https://carbonforge.dev/compare/ci-cd) - [Carbon Forge and Anthropic's Scion](https://carbonforge.dev/compare/anthropic) ## Company - [100monkeys.ai](https://100monkeys.ai/): the company that builds Carbon Forge, AEGIS and Your Zaru - [GitHub](https://github.com/100monkeys-ai) - [X](https://x.com/100monkeysai)
Websites mit ähnlicher KI-Bereitschaft — vergleichen Sie llms.txt und Markup.