xCloud
create_application
Create an application under this account and return its record, including the id other tools take as `application`. Pass the readable name as `name`. The answer's `label`, that name with a unique key, is the readable half of both hostnames: production's `<label>` and development's `<label>-dev`, under the platform's domain. Before calling, ask the builder which plan the application starts on: `free`, `standard`, or `pro`. Pass the builder's answer as `plan`, which is required. Do not choose a plan for the builder, since the plan sets what the application costs and what it may use. `read_plan_quotas` answers each plan's price, quantities, and application limit. Where no person can answer and the task names no plan, create nothing and report that the plan is the builder's to choose. This creates the record only: services are declared with `submit_manifest`; a new application has one environment, production, so its first `deploy` serves on production; call `create_environment` first to deploy to development instead.
Remote (network-hosted)
Other tools also called create_application?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"name": {
"type": "string",
"pattern": "^[a-z][a-z0-9-]{0,39}$",
"description": "The application's readable name: a lowercase letter first, then lowercase letters, digits, and hyphens — 1 to 40 characters in all. It becomes the readable half of the application's hostname; the platform adds a unique key."
},
"plan": {
"enum": [
"free",
"standard",
"pro"
],
"type": "string",
"description": "The plan the application starts on: `free`, `standard`, or `pro`. Required: ask the builder which plan and pass the answer, never a value chosen for them. Naming `free` while the account already holds its one live free application refuses `free_application_limit`, and naming a plan whose quantity is unset refuses `plan_quantity_unset`. During our introductory period, naming `standard` or `pro` while the account already holds its one live application on that plan refuses `beta_plan_limit`."
}
}
}