Feature · For developers

Your backend, without running one.

Sign-in, data, payments and bookings over one API and MCP. Your app, your stack.

The first call below needs no account. The site it makes stays online for 72 hours.

RequestPOST /v2/anonymous-sites

curl -sS https://api.pagelemon.com/v2/anonymous-sites \
  -H "Content-Type: application/json" \
  -d '{"files":[{"path":"index.html",
       "content_base64":"PGgxPkhpPC9oMT4="}]}'

Copy it and run it.

Answer201 Created

{
  "site": "…",
  "url": "https://….pagelemon.dev",
  "site_token": "st_…",
  "claim_url": "https://dash.pagelemon.com/claim#…",
  "expires_at": "…"
}

Values shortened.

Your site is live. The claim link keeps it in your workspace.

Skip the plumbing

What you build around an app, and what you ask for instead.

UsuallyRun an auth server and keep sessions safe
With Page LemonSign-in and users are part of the API
UsuallyStand up a database and write the CRUD
With Page LemonLists you add, read and change over REST
UsuallyHost Stripe webhooks and handle every retry
With Page LemonPayments into your own Stripe, already wired
UsuallyKeep a cron job alive for reminders and syncs
With Page LemonAutomations on an event or a schedule

What you get

The backend parts you would build, already running.

One API, one key

Sign-in, data, payments and bookings all live under /v2, described in one OpenAPI document.
Your AI gets the same power

The MCP server calls the same routes, with the same rights and limits.
Nothing to host

No auth server, database or cron box to keep alive.
You confirm the risky bits

Deleting, refunds and people wait for your yes on the Dashboard.

Four ways in

Pick the one that fits. They share the same rights.

REST API and OpenAPI

Every route is in a public OpenAPI document. Send a key, get JSON.

curl https://api.pagelemon.com/v2/sites \
  -H "Authorization: Bearer $PAGELEMON_TOKEN"
# spec: /v2/openapi.json

API reference →

MCP server

Connect Claude Code, Cursor or VS Code. Sign in once, then ask.

claude mcp add --transport http pagelemon \
  https://mcp.pagelemon.com/mcp
# then: "Deploy on PageLemon.com"

MCP server and tools →

Signed webhooks

Send events to your server. Each one is signed, so you can check it.

webhook-id: <stable across retries>
webhook-timestamp: <unix seconds>
webhook-signature: v1,<HMAC-SHA256>

Webhooks guide →

GitHub deploys

Link a branch to a site. Every pull request gets its own preview.

main      → your live site
pull #42  → preview, test data only
CI        → GitHub token, no stored key

API reference →

How it works

A key, a call, a confirm.

Make a key
In the Dashboard, pick what it can reach and what it can do. Or let your AI app sign in.
Two minutes
plak_…
Call the API
Use REST from your code or MCP from your AI. A retry with the same Idempotency-Key never does the work twice.
Any language
Authorization: Bearer …
Confirm the risky bits
Deleting, refunds and people are held until you approve them on the Dashboard. Nothing happens before.
One tap
202 · approve_url