# How to host a website made with DeepSeek

By Avatar 8 (Avatar 8 LLC) · Published November 17, 2026 · https://deed.page/blog/host-a-website-made-with-deepseek

To host a website made with DeepSeek means putting the HTML DeepSeek wrote on a server so anyone can open it at a normal HTTPS address. On deed.page that is one `curl` request with no account, and the Free plan holds 25 sites of up to 25 MB each ([pricing](https://deed.page/pricing)).

DeepSeek writes the code; it does not give you a public web address for it. Its API returns text in an OpenAI- or Anthropic-compatible format ([DeepSeek API docs](https://api-docs.deepseek.com/), checked November 17, 2026), so the files still need a host. The steps below cover the two common cases: HTML you copied out of a DeepSeek chat, and a coding agent that runs on DeepSeek models. Every deed.page command here was run against production on November 17, 2026 with a 30-minute expiry, and the test sites were then deleted.

## How do I host a website made with DeepSeek?

Ask DeepSeek for the page as one complete `index.html` with the CSS and JavaScript inline, copy it from the code block, and save it as `index.html`. Then publish it from any terminal:

```bash
curl -T index.html "https://deed.page/v1/sites?slug=study-planner-deepseek-d7q4&ref=blog"
```

The reply had `"url": "https://study-planner-deepseek-d7q4.deed.page/"`, `"version": "v1"`, and a `deed_tok_…` owner token shown once. Keep that token; it is the only credential. Pick your own suffix, since that slug is only an example. When we sent the same request again without the token, it returned `slug_taken` and suggested `study-planner-deepseek-d7q4-2` ([choosing a slug](https://deed.page/blog/choosing-a-slug)). There is no sign-up, no claim link, and no default expiry.

## A built project with several files

If DeepSeek gave you a React or Vite project, build it first and pack the output so `index.html` sits at the root. Then send it with the token from the first publish:

```bash
tar -C dist -czf site.tar.gz .
curl -T site.tar.gz -H "Authorization: Bearer $DEEDPAGE_TOKEN" \
  "https://deed.page/v1/sites?slug=study-planner-deepseek-d7q4&ref=blog"
```

That returned `"version": "v2"` at the same URL, and `/assets/style.css` served as `text/css`. Sending the same tarball again returned `"unchanged": true` without a new version. deed.page serves static files only. Never put your DeepSeek API key in front-end code, and keep anything that needs a server or database on a host that runs code. Bigger builds go up in parts ([large sites](https://deed.page/blog/plan-upload-large-sites)).

## If a DeepSeek-powered agent made the page

DeepSeek documents running Claude Code on its models: set `ANTHROPIC_BASE_URL=https://api.deepseek.com/anthropic` and put your DeepSeek key in `ANTHROPIC_AUTH_TOKEN` ([Integrate with Claude Code](https://api-docs.deepseek.com/quick_start/agent_integrations/claude_code/)). The same docs have setup pages for Codex, OpenCode, and other agents ([DeepSeek API docs](https://api-docs.deepseek.com/)). An agent like that can run the `curl` line above itself and hand you the link.

To give it a tool instead of a shell command, add deed.page as an MCP server. In Claude Code:

```bash
claude mcp add --transport http --scope project deed-page https://deed.page/mcp
```

We ran this with Claude Code 2.1.319 in a scratch folder. It wrote `"deed-page": {"type": "http", "url": "https://deed.page/mcp"}` to `.mcp.json`, and `claude mcp list` showed it as pending approval until you open `claude` and approve it. There is no sign-in step. One detail from DeepSeek's [Anthropic API compatibility table](https://api-docs.deepseek.com/guides/anthropic_api): the API-side `mcp_servers` field is ignored. MCP has to run in the client, which is how Claude Code does it. The publish call the agent makes looks like this:

```json
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"publish_site","arguments":{"slug":"study-planner-deepseek-mcp-d7q4","files":{"index.html":"<!doctype html><title>Study planner</title><h1>Study planner, published by a DeepSeek-powered agent</h1>"}}}}
```

It returned `ok: true`, `version: "v1"`, the subdomain URL, and a token. Passing that token to `update_site` gave `v2` at the same address; without it, `update_site` refused with `unauthorized`. The server listed 30 tools. We tested the deed.page side and the Claude Code config, not a DeepSeek model call, because that needs a DeepSeek API key. The [MCP walkthrough](https://deed.page/blog/mcp-publish-walkthrough) covers the rest.

## Keep the token and reuse it

Tell the agent once to save the token to `~/.config/deed-page/token` with `chmod 600`, keep it out of git, and reuse it, so later pages stay under one owner. deed.page stores only the token's SHA-256 ([trust](https://deed.page/trust), [token hygiene](https://deed.page/blog/token-hygiene-for-agents)).

## FAQ

**Can DeepSeek host a website by itself?**
No hosting feature appears in DeepSeek's API docs as of November 17, 2026. DeepSeek writes the HTML, and you or your agent upload it to a host such as deed.page.

**Do I need an account?**
Not on deed.page; the first publish mints the owner token. Sites stay under that token, and you can [roll back](https://deed.page/blog/version-history-and-rollback) to any of the last 10 versions on Free.

**Will the site disappear if nobody visits it?**
No. Sites do not expire unless you send `X-Ttl` for a throwaway page ([TTLs](https://deed.page/blog/ttl-for-throwaway-pages)). Free sites show a small "Published with deed.page" link; Hobby at $3 a month removes it.
