Build and publish a Krate app
build_appBuilds a real app the person keeps: one small file that runs natively on Windows, macOS and Linux and opens from a link in any browser, phones included. A Krate app keeps its own data on the device and works offline; with the person's permission it can print to a printer they pick with no print dialog, talk to serial and USB devices, read and write Excel files, serve other devices on the local network, and use the camera, microphone and location. Compiles the app's files (Cargo.toml, src/lib.rs, manifest.toml and any assets), checks it uses only Krate's API and runs it once, then publishes it unlisted to the signed-in person's Krate account with its link. Answers a build id at once; a build takes a few minutes. Needs the person to sign in to Krate.
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>",
"files": "<files>"
},
"name": "build_app"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The app's name, as a person would say it | |
| files | Yes | Every file of the app, with paths relative to the app folder |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fix | No | How to fix it, in the check's own words | |
| link | No | The app's own link; it opens the newest version | |
| name | No | ||
| stage | No | Where Krate's check stopped, on a failure | |
| app_id | No | ||
| detail | No | What went wrong, in the check's own words | |
| status | Yes | ||
| message | Yes | ||
| build_id | Yes | ||
| browser_link | No | Opens the app in a browser on any device, nothing to install |