pagehive

How it works

Ask your agent. Get a live page.

Your agent signs up, builds the page and publishes it. You claim it with a passkey. From then on your agent keeps it current, and you decide who sees it.

No server · No deploy · No editor

Example

One booking page, start to finish.

A small studio wants online bookings. This is everything that happens, from the first message to the first booking.

  1. 0109:00 · You ask

    Ask for the page

    “A booking page for the studio, with Friday slots.” That is the whole brief.

  2. 0209:02 · Live

    It writes and publishes

    Pages in plain HTML, the slots in a table, one publish. The site gets its own address: studio.pagehive.space.

  3. 0309:05 · You claim it

    Open the link, add a passkey

    The site joins your hive. Your agent keeps its key and only ever hands you the link. Unclaimed sites are deleted after 7 days.

  4. 0414:00 · First booking

    The page answers back

    A visitor books Friday 14:00. The page tells your agent, and your agent updates the slot for the next visitor.

Next weekYou ask for Saturday slots. Your agent publishes a new version, and the old one stays one click away.

Sign up and claim

Start with your agent, or start yourself.

Let your agent sign up and send you a claim link, or create an account first and connect the assistant you already use.

A · Your agent starts

Your agent signs up for you.

It calls POST /v1/signup and gets an API key, shown once, and a claim link. It keeps the key and gives you only the link. You open it, create a passkey or sign in with one you already have, and the site joins your account.

POST /v1/signup
→ api_key.secret   kept by your agent
→ claim_url        sent to you
B · You start

Connect Claude, ChatGPT or Grok.

Sign up with a passkey, Google or GitHub. Find Pagehive in the claude.ai connector directory, or add it as a custom connector in ChatGPT, Grok, Cursor or another OAuth-capable MCP client, then sign in and approve the app.

https://pagehive.io/mcp

Step by step for Claude, ChatGPT, Grok and Cursor

Connected apps

A connected app can publish and edit your account through MCP only. A connected app cannot create sign-in links, claim links, bots, or API keys, and it cannot rotate keys. Its access token works only on /mcp, or on the /mcp/<name> URL it was connected with. You pick which agent an app connects as; Your Hive shows each app on its agent's page, and disconnecting one ends it on its next request.

Plans

Every Hive starts on Free. Basic, Pro and Ultra raise the limits and add custom domains; the pricing page compares them. Your agent can also sign up on its own and hand you a claim link, or join your Hive with an API key you create in Your Hive.

Terminal clients

Claude Code and Claude Desktop use a bearer key. An account key starts with bp_live_, a site key with bp_site_. The command below uses a placeholder, never a real key.

claude mcp add --transport http pagehive https://pagehive.io/mcp --header "Authorization: Bearer bp_live_..."

Draft, then publish

Nothing goes live by accident.

Your agent writes pages in plain HTML and CSS, to a draft. Visitors see nothing until it publishes, and every publish is a version you can go back to.

  • One publish, one version

    A new site stays offline until its first publish. Later publishes keep it online or offline, as it is now.

  • Reviewed before search

    Pagehive reviews every publish. A site stays out of search engines until its first review passes.

Live data

The data changes. The page follows.

Tables and values belong to your account, and your agent fills them. A page reads the public ones in the browser, so it changes without a new publish. Private values stay off the public page.

Private sites

Private until you say so.

Every new site starts private. You choose when that changes, and you can stop your agent from changing it.

  • Private · default

    Only you

    A stranger who opens the address sees that it is not public. You open it from your account.

  • View link

    People you pick

    Share a view link to a private site. Revoke it any time.

  • Public

    Everyone

    Your call. Lock a private site and your agent cannot make it public.

  • Offline

    Nobody, for now

    Pages and view links are hidden, and the site still counts toward your limits. Only you can delete it, by typing its subdomain.

A short example

The whole thing in three calls.

Sign up, write the home page, publish. The same steps are available over MCP.

HTTP

POST /v1/signup
→ api_key.secret   keep this
→ claim_url        give only this to the owner

PUT /v1/sites/:id/pages
{ "path": "/", "title": "Home", "source": "<h1>Studio bookings</h1>" }

POST /v1/sites/:id/publish

MCP

create_site   { "subdomain": "studio" }
put_page      { "path": "/", "source": "<h1>Studio bookings</h1>" }
publish_site

Ask for your first page.

Describe the page you need to your agent, then claim it when the link arrives.

Sign-ups are paused

Pagehive isn't taking new accounts right now. Follow @pagehive_io on X to hear when sign-ups open again.

Follow on X