cristina.cc

What It Is

Cristina positions itself as a “team wiki for HTML artifacts generated by AI Agents.” It addresses a specific pain point: prototypes, reports, and dashboards produced by Agents often end up scattered across chat tools, without stable URLs or a searchable team archive. Users can paste HTML, upload files, or have an Agent publish via API. The system then returns a permanent URL that team members can access, search, categorize, and comment on.

Core Features

Cristina supports three content types: HTML, Markdown, and plain text. HTML is rendered inside a sandboxed iframe, with the product claiming to preserve charts, styles, scripts, and similar elements; Markdown is rendered using marked.js. It offers folders, a recent activity feed, permanent slugs, full-text search, and the ability to place numbered comment markers directly on rendered pages. Comments support threaded replies and resolved status. This is useful for report reviews, discussing page variants, and collecting feedback on data dashboards.

API and Agent Friendliness

The API is a highlight of the product. POST /api/artifacts lets users submit title, html, description, contentType, and folderSlug, and returns a permanent URL. PATCH can update an artifact in place without changing its URL, which is suitable for weekly reports, status pages, and recurring dashboards. GET can retrieve artifacts and comments, making it easier for Agents to incorporate team feedback. Authentication uses a workspace-scoped Bearer API Key. The documentation includes curl examples, request/response structures, and /llms.txt, and is generally well put together. However, we did not find details on error codes, rate limits, Webhooks, permissions, or SDKs.

Pricing and Deployment

The current copy only states “no card · 25 artifacts free,” and the terms of service also specify a limit of 25 artifacts for free workspaces. If paid plans are introduced in the future, users will be notified by email. There is no information on paid pricing, payment methods, SLA, or enterprise plans. We also did not see any open-source or self-hosting options, so Cristina looks more like an early-stage SaaS tool.

Pros, Cons, and Who It’s For

Cristina’s strengths are its narrow and clear positioning, simple onboarding, Agent-friendly API for automated archiving, and comments that are directly tied to the context of rendered content. Its weaknesses are the lack of information around enterprise-grade capabilities, including SSO, audit logs, permissions, data residency, self-hosting, and support channels. The free quota is also fairly small, and URL permanence depends on the artifact continuing to exist and the workspace remaining active. It is best suited for small teams that frequently use Claude or other Agents to generate HTML reports, prototypes, and evaluation pages.

Access from China

The crawled text does not provide information about access from mainland China, ICP filing, CDN, payment methods, or related details, so the access status can only be marked as unknown. If a team requires stability or compliant deployment in a domestic Chinese network environment, it may also consider Notion, Confluence, GitBook, or alternatives such as object storage plus a static site, or a self-built internal Wiki.