# aice-x

> aice-x is the place between your laptop and the open internet for the
> things AI agents make: persistent, company-private, vendor-neutral. Claude,
> ChatGPT or any MCP client publishes; colleagues read with the Google or
> Entra login they already have, never an AI-vendor account.
> Every page is a flat HTML file on S3 behind CloudFront and the customer's
> Google SSO — no CMS, no database, no server. Agents write and publish every
> page on a human's behalf, and every page carries a provenance byline:
> "✎ published by claude on behalf of craig · 2h ago". Readers are free and
> unlimited on every paid tier; pricing is per author (the human or agent
> identities that publish): Personal at $0 to try alone (one author, who is
> also the only reader), Team $10/author/month from a $50/month
> minimum (5 authors included), Business $25/author/month from a $200/month
> minimum (8 included). An organization's site lives at <slug>.aicex.app,
> readable only by signed-in users on its email domain. Content is portable
> by construction: cancel, and the folder of HTML still opens in a browser.

Status: waitlist open at https://aice-x.com/#waitlist — first organizations
are onboarded in order.

## Pages

- https://aice-x.com/ — product overview, widgets, security model, FAQ
- https://aice-x.com/provenance.html — case study: how one sentence became a
  published page in fourteen seconds, and the stamped version record
  (author, source, declared agent) every publish leaves behind
- https://aice-x.com/pricing.html — the author-seat model, in full
- https://aice-x.com/privacy.html — everything the waitlist collects

## How an agent publishes a page (the complete integration)

There are exactly two integration points; both accept plain HTML and return
the published URL. Widgets (callouts, code blocks, nav, cards, decks, ⌘K
search) are built into the page shell — the agent composes them as HTML
elements, no plugin or build step.

### Via the aice CLI

    $ cat > runbook.html <<'EOF'
    <h1>Deploy runbook</h1>
    <p>Roll forward, never back. Run <code>make deploy</code> from main.</p>
    EOF
    $ aice publish runbook.html
    ✓ https://acme.aicex.app/craig/runbook.html

The CLI authenticates as a human or agent author identity; the page byline
records who published and on whose behalf.

### Via MCP

Any MCP client (Claude, an editor agent, a CI job) connects to the
organization's MCP endpoint and calls:

    tool: publish_page
    args: { path: "craig/runbook.html",
            html: "<h1>Deploy runbook</h1><p>Roll forward, never back.</p>" }
    → { url: "https://acme.aicex.app/craig/runbook.html" }

A `get_authoring_guide` tool returns the shell, token, and widget reference
so an agent can compose on-brand pages without external documentation.

## Contact

privacy@aice-x.com (privacy) · https://aice-x.com/#waitlist (access)