你好。

猫猫魔女的魔法基地 ✦ Steven 的自建小宇宙

为日常与灵感准备的一组小工具。基于自己搭的基建上 · 运行情况见状态页

已解锁

11/ 27

登录后解锁 16 个

公开

另有 3 个混合

需登录

登录后使用

管理员 · 服务间

管理员 3 · 服务间 2

魔女的道具

要登录

对外开放

谁都能逛

魔药架

纯 API · 给程序用的

简历数据 api.lishuyu.app/resume/「关于我」页面背后的简历 API — 机器可读，读公开。公开时间服务 api.lishuyu.app/time全平台最小的服务 — 只报 UTC 时间，端到端自检探针。公开评论后台 api.lishuyu.app/comments博客的评论区 — 匿名可发，LLM 先发后审，回复走邮件。公开文件存储 API api.lishuyu.app/files文件柜背后的引擎 — 匿名上传、分片、P2P 直传。混合魔法画卷 pages.shuyuli.com丢一份 HTML 进来，秒变可分享的公开单页 — 沙箱隔离，每页 10MB。混合键值存储 api.lishuyu.app/kv按用户隔离的 KV 小抽屉，支持 TTL 自动过期。对象存储 api.lishuyu.app/ossR2 后端的对象仓库 — presigned 直传，公开对象可直链。日志汇聚 api.lishuyu.app/logs全平台日志都汇到这一个 sink，30 天自动清扫。密钥保管箱 api.lishuyu.app/secretsAES-256-GCM 静态加密的 secrets 存取。消息总线 api.lishuyu.app/message服务往频道里丢消息，看板和 bot 轮询取走。推送中心 api.lishuyu.app/notify按紧急度决定走 bark、邮件还是墨水屏。服务间发信服务 api.lishuyu.app/email平台的发信员 — 事务邮件经 Resend 出门。服务间公众号中继 api.lishuyu.app/wechat微信公众号发布代理 — 让博客同步永远从白名单 IP 出门。管理员

基地设施

平台层

LLM / agent navigation — how to explore this platform

Fabric v2 preview — current runtime

One Node.js Host owns Cordis plugins. Start with the following runtime endpoints. Control routes require a configured management bearer credential with the control scope; a browser login or ordinary user token does not grant runtime administration. GET https://api.lishuyu.app/ opens the management UI. This homepage's build/configuration guide is available at /agents.md.

method	path	auth	purpose
GET	`https://api.lishuyu.app/health`	none	runtime liveness and version
GET	`https://api.lishuyu.app/v2/control/plugins`	control	installed plugin generations, phases and active work
GET	`https://api.lishuyu.app/v2/control/jobs`	control	persisted jobs
GET	`https://api.lishuyu.app/v2/control/failures`	control	captured failures
GET	`https://api.lishuyu.app/v2/control/logs`	control	diagnostics and dropped-log count

Invoke installed services through POST https://api.lishuyu.app/v2/call/{service}/{operation} with the operation's JSON input and an authorized bearer credential. Consult the service's docs/index.md and contracts for inputs and permissions. Restart or rollback uses POST /v2/control/restart or POST /v2/control/rollback, a JSON body containing pluginId and expectedGeneration, and an Idempotency-Key header; HTTP 202 means queued, not completed. GitHub updates use POST /v1/webhooks/{bindingId} with the configured source binding, GitHub delivery ID and HMAC signature. Do not substitute a browser session for webhook authentication.

Legacy reference — not a v2 API contract

The following directory describes the previous deployment. These addresses and behavioral claims require service-by-service migration verification. The old Registry discovery/MCP and deploy endpoints are not provided by the v2 runtime merely because their origins are configured here.

This page is the human directory of the lishuyu.app platform. The machine directory is the Service Registry: start at GET https://registry.lishuyu.app/llm.txt (public, plain text) for the full how-to.

method	path	auth	purpose
`GET`	`https://registry.lishuyu.app/llm.txt`	none	agents guide — auth flow, service catalog, conventions
`GET`	`https://registry.lishuyu.app/api/services/discover/{capability}`	bearer	find the service providing a capability
`POST`	`https://registry.lishuyu.app/mcp/mcp`	bearer	MCP endpoint (streamable-http) for the registry
`GET`	`https://api.lishuyu.app/resume/`	none	full machine-readable résumé JSON (note the trailing slash — required)
`GET`	`https://api.lishuyu.app/time/now`	none	current UTC time (ISO-8601) — platform liveness probe; `GET /time/` is a usage page
`GET/POST`	`https://api.lishuyu.app/comments/posts/{slug}`	none	read / post blog comments (anonymous allowed, LLM-moderated)
`GET`	`https://api.lishuyu.app/files/public`	none	public files listing (file storage; anonymous upload via `POST /files/upload`)
`GET/PUT/DELETE`	`https://api.lishuyu.app/kv/{key}`	bearer	per-principal key-value store with optional TTL
`GET/POST`	`https://api.lishuyu.app/logs/`	bearer	platform log sink — write one/batch, query back
`GET/POST/DELETE`	`https://api.lishuyu.app/oss/{bucket}/{key}`	bearer	object storage on R2 (public objects download without auth)
`GET/PUT/DELETE`	`https://api.lishuyu.app/secrets/{key}`	bearer	encrypted (AES-256-GCM) secrets store, per-principal namespace
`POST/GET`	`https://api.lishuyu.app/message/messages`	bearer	message bus — publish to a channel / poll unread
`POST`	`https://api.lishuyu.app/notify/send`	m2m/admin	push fan-out — routes to bark / email / e-ink display by urgency
`POST`	`https://api.lishuyu.app/email/send`	m2m/admin	outbound transactional email (Resend/SMTP)
`POST`	`https://api.lishuyu.app/wechat/draft`	admin	WeChat Official Account publishing relay
`GET`	`https://mail.lishuyu.app/api/emails`	admin	catch-all inbox for *@lishuyu.app — list/read mail; AI auto-replies via an edge worker; send goes through emailservice
`POST`	`https://pages.shuyuli.com/api/pages`	bearer	publish a self-contained HTML page (≤10MB, body `{html, title?}`; works anonymously too — anon pages live under /anon/, expire in 30 days, managed via the returned one-time claim_token) — returns a public sandbox-CSP URL `pages.shuyuli.com/{owner}/{page_id}`; manage via GET/PUT/DELETE `/api/pages/{id}` (admin SPA goes through the `api.lishuyu.app/pages/api/*` gateway bridge)
`POST`	`https://api.lishuyu.app/deploy/api/deployments`	admin	manual deploy / rollback of a managed service
`GET`	`https://api.lishuyu.app/{svc}/health`	none	liveness for every path-mounted service (kv, logs, oss, secrets, message, notify, email, wechat, files, comments, time, resume)

Authenticate with a bearer token issued by auth.lishuyu.app. Path-mounted services under api.lishuyu.app/<service>/ require the trailing slash. The Live2D mascot on this page is decorative today; it is planned to become the platform-wide agent chat entry (TODO).