AI Deploy Proxy
ai_deploy_proxyDeploys an app's AI backend: spec-driven subscription mode or legacy credits proxy, storing keys in server-side secrets and requiring human approval for live changes.
Instructions
Deploy the AI backend: the full spec-driven backend in subscription mode, or the legacy ai-proxy in credits mode (live, needs human approval).
Use when: the app has an AI feature. AI keys go only to server-side secrets. For explicit dry-run planning use backend_deploy. Returns: {ok, deployed: [...]} or an approval_required refusal.
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": {
"app_dir": "<app_dir>",
"project_ref": "<project_ref>"
},
"name": "ai_deploy_proxy"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| app_dir | Yes | Absolute path to the app project directory (contains app.spec.json), e.g. /Users/me/Apps/MyApp. | |
| approval_id | No | Approval id from a previous approval_required refusal; omit on the first call. The human approves out-of-band with `appfactory approve <id>`, then call again with the same arguments and this id. | |
| daily_limit | No | Per-user daily request cap for the legacy ai-proxy (default 20). | |
| project_ref | Yes | Supabase project ref to deploy to. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||