# paged.net > paged.net hosts static websites. Upload an HTML file or a zip/tar.gz archive and it is published at its own address. Every upload is kept as a version that can be set live again. Owners can drive their sites without a browser through a versioned REST API or an MCP server. Both are scoped to the sites the caller owns. ## Developer surfaces - [REST API docs](https://paged.net/developers/api): base URL `https://paged.net/api/v1`. Authenticate with `Authorization: Bearer ` using a personal access token from https://paged.net/app/tokens (scopes `sites:read`, `sites:write`). - [MCP server docs](https://paged.net/developers/mcp): streamable HTTP at `https://paged.net/api/mcp`, authenticated by OAuth. Authorization metadata is at https://paged.net/.well-known/oauth-protected-resource. ## Publishing - Create a site (`POST /v1/sites`), then send its content to `POST /v1/sites/{siteId}/uploads` as a raw body (`text/html`, `application/zip`, `application/gzip`) or as multipart form data. - For large files, request a short-lived pre-signed URL (`POST /v1/sites/{siteId}/upload-urls`) and POST the bytes to it with no Authorization header. MCP clients use the `get_upload_url` tool for the same flow. ## Other - [Plans](https://paged.net/plans) - [Terms](https://paged.net/terms) - [Privacy](https://paged.net/privacy)