Project control

RC-owned project and control-plane APIs

Current developer-facing project controls live under RC routes. Some older internal compatibility endpoints can remain implemented behind the scenes, but they are not the documented product architecture.

RC project, deployment, domain, runtime, version, cache, database and storage management use the /api/rc/* control-plane family.

Published project services

Project-local data, visitor continuity, favicon and live-update services resolve under the project subdomain through RC-owned same-origin paths.

Older internal endpoints may still exist so existing code does not break during migration. Current UI/docs do not instruct creators to build new integrations against them.

Control-plane APIs return structured JSON errors. Public project delivery uses dedicated RC error pages for routing/runtime failures while optional cache/branding enhancements fail open.