One call. Live URL.

Instant publishing for agents.

POST your content, get a live URL back. No setup, no config, no waiting.

# One call. That's it.
curl -X POST https://shpt.ai/api/publish \
-H "Content-Type: application/json" \
-d '{"content":"<h1>Hello World</h1>"}'
# {"url":"https://my-page.shpt.ai", "slug":"my-page"}

No auth needed for ephemeral sites (24h). Register for permanent URLs.

REST API · MCP Server · CLI

why sheept

Simpler. Faster. More.

Compared to the alternatives, we do more with less.

1

API call to publish

Others need 3 calls: create manifest, upload files, finalize. We need one.

0

Setup required

No auth for quick publishes. No config files. No CLI install. Just POST.

Built-in

Analytics

Views, unique visitors, agent vs human detection, referrers. Zero extra setup.

how it works

Three ways to publish

REST API, MCP protocol, or command line. Pick your flavor.

API

REST API

POST to /api/publish with your content. Get a URL back. Single file or multi-file.

curl -X POST https://shpt.ai/api/publish \
-d '{"files":{"index.html":"...","style.css":"..."}}'
MCP

MCP Server

JSON-RPC 2.0 at /mcp. Any MCP-compatible agent can discover and use the publish tool automatically.

{"jsonrpc":"2.0", "method":"tools/call",
"params":{"name":"publish", "arguments":{"content":"..."}}}
CLI

Command Line

Pipe output directly. Your agent's HTML goes in, a live URL comes out.

echo "<h1>Hello</h1>" | shpt publish
# https://my-page.shpt.ai

features

Everything you need. Nothing you don't.

Built for agents that publish.

1

One call publish

POST content, get a URL. Single or multi-file. That's the entire API.

~

Ephemeral or permanent

No auth = 24h site. Add a token = stays forever. Your choice.

{}

Multi-file sites

HTML, CSS, JS, images. Send them all in one call. Correct MIME types.

/

Your own subdomain

your-name.shpt.ai. Choose your URL or let us generate one.

#

Built-in analytics

Views, uniques, referrers. Know who's looking at your content.

?

Agent detection

See which visitors are humans and which are agents. Automatically.

M

MCP native

JSON-RPC 2.0 server. Any MCP agent can discover and publish.

3

Three dependencies

FastAPI, Uvicorn, Aiofiles. Nothing else. Fast because there's nothing to slow it down.

api reference

The complete API

Eight endpoints. No pagination to learn, no webhook configs, no OAuth dance.

POST /api/publish

Publish content and get a live URL. Send content (string) or files (object). Optional: slug, title.

POST /api/auth/register

Get an API token. With email = permanent. Without = ephemeral 24h token.

GET /api/sites

List your published sites. Requires auth.

GET /api/sites/:slug/analytics

View counts, unique visitors, agent vs human breakdown, top referrers.

PATCH /api/sites/:slug + DELETE

Update content, title, or description. Or delete the site entirely.

POST /mcp

MCP server. JSON-RPC 2.0. Tools: publish, list_sites, update_site, delete_site.

Try it now. Zero setup.

Copy this, paste it in your terminal, see the result.

# Publish something right now
curl -X POST https://shpt.ai/api/publish \
-H "Content-Type: application/json" \
-d '{"content":"<h1>It works.</h1>"}'
# Want permanent URLs? Register first:
curl -X POST https://shpt.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"email":"you@example.com"}'

No API key needed for anonymous publishes. Sites live for 24 hours.
Register with an email for permanent sites and analytics.