Documentation
Sign on your computer
With an active membership, open Certificates and choose Developer ID. The Slate CLI keeps the private key in Secret Service or a file readable only by your user.
slate-app key request --name "Example Studio" --out request.slatekeyreqUpload the public request file and confirm with a passkey. Download the chain and use the filename shown on the certificate page.
slate-app key install certificate-1.slatechain
slate-app key list
slate-app build .
slate-app verify "build/Notes.app"Cloud signing
Register the app ID and create a cloud key for it. For a feed or catalog, submit the exact JSON file in message_b64, up to 1 MiB. The example prepares a feed request for the signing API or the MCP sign tool.
python3 - > sign-request.json <<'PYTHON'
import base64, json
from pathlib import Path
feed = Path("feed.json").read_bytes()
print(json.dumps({
"bundle_id": json.loads(feed)["id"],
"kind": "feed",
"message_b64": base64.b64encode(feed).decode("ascii")
}))
PYTHONFor an app or disk, message_b64 holds the 4192-byte Slate signing input and manifest_b64 holds the CBOR manifest, up to 64 KiB. The response contains signature_b64 and chain_b64. Your build tool assembles the signature block locally. For a disk or catalog, select a key whose entire app list is within the connection’s signing scope.
Connect an AI agent
In Claude Code, add the HTTP server and open /mcp to authenticate. In other MCP clients, add the same URL as a remote HTTP server.
claude mcp add --transport http binadit https://developer.binadit.com/mcpReview the client name, callback address and requested scopes. Select apps and an expiry of up to 90 days. Confirm with a passkey. Certificate and revocation requests appear in Pending actions for separate approval.
Connect a build server
Create a build connection for the required apps. Save the one-time secret in your build server’s secret store. Exchange the credentials for a one-hour access token, then send the signing request as JSON.
curl --user "$CLIENT_ID:$CLIENT_SECRET" \
--data 'grant_type=client_credentials' \
https://developer.binadit.com/oauth/token
curl --header "Authorization: Bearer $ACCESS_TOKEN" \
--json @sign-request.json \
https://developer.binadit.com/api/v1/signPersonal keys
Slate Build and Studio can use personal keys for software you make for yourself or share with people you know. Personal signing is free and requires no portal account.
slate-app key personal --name "Example Studio" --out ./personal-keys
slate-app sign "build/Notes.app" \
--key ./personal-keys/personal.key --chain ./personal-keys/personal.chain