project_create
Create a new project / app / website / site — initialize a project with a subdomain to start building and hosting it. This is the first step for any new app: a web app, API, backend, landing page, SaaS, or full-stack site.
The project starts with the same starter somewhere init writes — a React + TypeScript app with sign-up, sign-in and sign-out, styled views and design tokens (src/styles/tokens.css) — deployed as its first release; when data.starter.status is deployed it is live at https://{subdomain}.somewhere.site. The call waits up to 120 seconds for that deploy. starter.status is deployed, preview, failed (the deploy was refused; starter.error says why) or unknown (no answer in time, or an answer without a release). For failed and unknown, starter.recovery lists the checks to run and the exact project_deploy call (or the equivalent somewhere init command) that ships the same starter.
If a project_create response is lost, the project may exist: look for it with project_get or project_list (by subdomain) before creating again. Repeating the call returns SUBDOMAIN_TAKEN, and a new name makes a second project. data.starter lists the deployed files and returns the starter's agent_contract (its AGENTS.md), readme (the file map) and skills index; deploys do not publish those files, so they arrive here. project_patch edits the starter. starter: "auth,private-data" adds per-user notes backed by db/schema.ts; starter: "none" creates an empty project.
New projects use declared data: tables and access rules live in db/schema.ts, deployed as raw source. Pages use the generated somewhere:data client for normal data, and a function only for a write the grant cannot express: docs({ topic: 'declared-data', section: 'declare-a-table-and-use-it' }), then docs({ topic: 'recipe-signed-in-app' }) for a public form that files a row for an owner. The subdomain must be unique platform-wide and cannot use reserved names (api, admin, www, etc.). Projects and deploys are unlimited on all tiers.
Example:
{ "name": "Acme Dashboard", "subdomain": "acme-dash", "description": "Internal team dashboard" }
// Returns: { "data": { "id": "…", "url": "https://acme-dash.somewhere.site", "starter": { "status": "deployed", … } } }Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>"
},
"name": "project_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Display name for the project | |
| starter | No | Starter modules, as for `somewhere init --features`: "auth" (default), "auth,private-data", "auth,agent", or "none" for an empty project. | |
| template | No | Start from a platform template instead of the starter, for example "links" (a links page). GET /v1/templates lists them. Creates and publishes the app in one call; repeating it with the same name returns the existing app. | |
| subdomain | No | Optional subdomain — defaults to slugified name. Must be lowercase letters, digits, and hyphens. | |
| starter_ui | No | Starter UI: "styled" (default; views plus design tokens) or "headless" (the same pages without CSS). | |
| description | No | Optional human-readable description |