Pagelive for AI agents
Give your agent a place to publish — and know who opens it
When your agent builds an HTML proposal, dashboard, or report, Pagelive turns it into a branded, tracked, access-controlled link in one call — over MCP or a plain REST request. No deploy, no export.
Free to start · any HTTP client.
In one call
HTML in, a tracked URL out
agent → publish_page {
"html": "<!doctype html>…",
"title": "Q3 Board Update"
}
→ { "url": "https://pagelive.site/p/k3n8",
"noindex": true }
# later
agent → get_page_stats { slug }
→ 3 opens · 2 unique · 2m 41s · 🇩🇪 🇺🇸Two ways to connect
MCP for chat agents · REST for everything else
Same endpoint, same tools. Pick the one that fits how your agent runs.
Hosted MCP connector
For conversational agents (Claude & any MCP client). Add the URL, sign in once with OAuth, and the tools appear.
{
"mcpServers": {
"pagelive": {
"url": "https://app.pagelive.io/api/mcp"
}
}
}REST / JSON-RPC + API key
For server-side agents, scripts, and frameworks. POST JSON-RPC to the same endpoint with a Bearer key — any HTTP client, normal User-Agent.
POST https://app.pagelive.io/api/mcp
Authorization: Bearer pl_…
Content-Type: application/jsonQuickstart
Publish a page in one call
Get a key from the dashboard, then POST publish_page. The response is your live URL.
curl -s https://app.pagelive.io/api/mcp \
-H "Authorization: Bearer pl_YOURKEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"publish_page","arguments":{
"html":"<!doctype html><h1>Hello</h1>",
"title":"Demo"}}}'
# → { "url": "https://pagelive.site/p/ab12cd34" }Full tool schemas + a runnable example: /llms-full.txt
The tools
Six tools your agent can call
publish_page Publish HTML as a live, branded, noindex link. Returns the URL. Optional password, custom domain, custom slug, team workspace.
update_page Re-publish to the SAME link — the URL never changes, a version is saved.
list_pages List the pages in the workspace — titles, slugs, links, view counts.
get_page_stats Pull opens, unique viewers, dwell time, countries, referrers.
list_workspaces The workspaces the key can publish into (personal + teams).
list_domains Connected custom domains to publish on (paid).
list_form_submissions Read replies submitted through a <form data-pagelive> on the page — publish a proposal with a reply form, then read the answers.
Why a Pagelive link
More than a public paste
A throwaway public link leaks to Google and tells you nothing. Every Pagelive link is branded, private by default, and tracked.
A real URL in one call
AI-built HTML becomes a live, branded link — on pagelive.site or your own domain. No deploy, no repo, no export.
Tracking built in
Opens, unique viewers, dwell time, geo, referrers — and real-time "who opened it" alerts. Your agent can pull the numbers with get_page_stats.
Replies come back to you
Include a plain <form data-pagelive> in the HTML — no endpoint, no key. Submissions are captured, the owner is emailed, and your agent reads them with list_form_submissions.
Access control
Password, email gate, or an allow-list of specific people — set at publish time. Noindex by default, so nothing leaks to Google.
Safe by default
Published HTML is scanned; obvious phishing is rejected. Pages serve from an isolated content plane, walled off from app + billing.
Drop-in skill
Teach your agent to publish
Paste this into your agent’s system prompt or skill definition. With the MCP connector or an API key wired up, it’ll publish whenever sharing is the goal.
You can publish HTML as a live, tracked, shareable link with Pagelive.
When the user wants to share a page, proposal, deck, dashboard, or report,
call publish_page with { html, title }. It returns a URL (noindex by default).
Add a password for confidential work. Use update_page to revise the same link,
and get_page_stats to see who opened it. For proposals, include a
<form data-pagelive> reply form in the HTML — read the responses later
with list_form_submissions.Agents browsing the web can read /llms.txt to discover and use Pagelive on their own.
FAQ
Do I need the MCP connector, or can I just hit the API? +
Either. Conversational agents (Claude, etc.) use the hosted MCP connector at https://app.pagelive.io/api/mcp with OAuth. Server-side agents and scripts call the same endpoint as plain JSON-RPC with an API key (Authorization: Bearer pl_…). Same tools, same result.
What HTTP client should my agent use? +
Any of them — requests, httpx, fetch, axios, okhttp, Go’s net/http, curl. Send your client’s normal User-Agent and a Bearer API key. No browser required.
Where do I get an API key? +
In the Pagelive dashboard under API & MCP. Keys are scoped to one workspace, shown once, and revocable.
Is published content public? +
No — every page is noindex by default, so search engines are told not to list it. Add a password, an email gate, or an allow-list for confidential work. Content is scanned and obvious phishing is rejected.
Is there an agent-readable spec? +
Yes — /llms.txt (a concise map) and /llms-full.txt (tool schemas + a runnable example), at the site root.
Let your agent publish its next page as a tracked link.
Free to start · MCP or REST · noindex by default.