Create production instance
create_production_instanceCreate the production instance for an application on a domain the user owns, copying configuration from the development instance by default (the first step of clerk deploy). This cannot be undone. Returns the new instance, the DNS records to add at the domain's DNS provider, and the next steps. The secret key is removed, or returned as encrypted_secret_key when recipient_public_key is set.
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": {
"application_id": "<application_id>",
"domain": "<domain>",
"confirm": "<confirm>"
},
"name": "create_production_instance"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Production domain you own, e.g. example.com. | |
| confirm | Yes | Confirms the user approved creating this production instance, which cannot be undone. | |
| application_id | Yes | Clerk application ID (app_…). | |
| clone_instance_id | No | Instance to clone configuration from. Defaults to the development instance. | |
| recipient_public_key | No | RSA public key to encrypt secret keys to: a JWK, or base64, base64url, or hex SubjectPublicKeyInfo DER, with a 2048 to 4096-bit modulus and exponent 65537. Each secret key then comes back as encrypted_secret_key, unpadded base64url RSA-OAEP ciphertext with SHA-256 for OAEP and MGF1 and an empty label, which only the matching private key can decrypt. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| instance | Yes | ||
| next_steps | Yes | ||
| dns_records | Yes |