SJJ Cloud is an orchestration layer for VPS providers. Keep your own provider accounts and use one API to provision, operate, and automate them.
https://api.sjjcloud.com. Account, access, billing, and webhook routes live under /api/*. The provider endpoint shapes below are also available as /v1/* aliases and currently return explicitly marked mock data until real provider adapters are connected. Your account ID, limits, and provider adapter availability are confirmed in the approval email.Every paid account follows the same five stages. This makes access, billing, and API delivery easy to understand.
Use this sequence to prepare a customer-facing integration or to test the workflow manually.
Submit your intended use, estimated fleet size, and the providers you already use. Do not send provider secrets in the application form.
POST /v1/access-requests
{
"email": "[email protected]",
"company": "Example Studio",
"use_case": "multi-provider deployment",
"expected_instances": 50,
"providers": ["hetzner", "dmit"]
}We verify the use case and send a decision email. The request is read-only until approved.
Approved applicants receive a one-time Checkout link for the $199/month Core Plan. The plan renews monthly until cancelled from the billing portal. The deployed MVP route is shown below; the versioned /v1/* contract remains planned.
POST /api/billing/checkout
Content-Type: application/json
{ "access_request_id": "...", "status_token": "..." }
// response
{ "checkout_url": "https://checkout.stripe.com/...", "session_id": "cs_..." }After Stripe confirms payment, the workspace moves to active. The customer can manage subscription status, payment methods, invoices, and cancellation in the billing portal.
GET /v1/account
// response
{ "status": "active", "plan": "core", "renewal_date": "2026-10-04" }A secret key is sent to the verified account email and is only stored as a hash by the Worker. The customer account UI can display masked key metadata; provider scopes and key rotation are planned follow-ups.
// email delivery after checkout.session.completed
{ "key_prefix": "sjj_xxxxxxxx", "created_at": "" }
// planned versioned route
POST /v1/keys All requests use JSON and the Authorization: Bearer <API_KEY> header. Provider-specific differences are normalized by the adapter layer.
/v1/providers/{provider}/credentialsIn the MVP simulation, the credential is stored as a protected hash with only its last four characters retained. Real provider calls and encrypted credential storage will be added with the adapter layer.
{
"api_key": "provider-secret",
"label": "production-eu"
}Never put provider keys in browser code, URLs, screenshots, or support tickets.
/v1/instancesChoose a provider and the portable fields below. Unsupported options return a clear 422 response with the provider capability matrix.
{
"provider": "hetzner",
"region": "fsn1",
"plan": "cx22",
"bandwidth_gb": 20,
"image": "ubuntu-24.04",
"name": "worker-01"
}/v1/providers/{provider}/instancesKeep provider boundaries visible while using one normalized schema.
?status=running®ion=fsn1&limit=100
// response
{ "provider": "hetzner", "items": [
{ "id": "i_123", "name": "worker-01", "status": "running", "ipv4": "203.0.113.10" }
] }/v1/commands/batchTarget a saved inventory query or explicit instance IDs. Commands run through the provider connection and return per-host results.
{
"instance_ids": ["i_123", "i_456"],
"command": "sudo apt-get update -y",
"timeout_seconds": 60,
"continue_on_error": true
}/v1/workflowsWorkflows will organize multiple steps—provision, wait for readiness, install packages, run a command, and notify your team—into one auditable run.
{
"name": "bootstrap-web-tier",
"steps": [
{ "action": "provision", "provider": "hetzner", "plan": "cx22" },
{ "action": "wait_for_ssh", "timeout_seconds": 180 },
{ "action": "run_command", "command": "./install-nginx.sh" }
]
}/v1/ai/schemaEvery endpoint can expose machine-readable JSON Schema and concise tool metadata. Agents can discover required fields, call the same REST API, and parse consistent success/error envelopes.
GET /v1/ai/schema?resource=instances
Accept: application/json
// tool metadata includes name, description,
// input_schema, output_schema, auth_scopesCredentials are stored server-side. Your application talks to SJJ Cloud; SJJ Cloud talks to each provider adapter.
Agents should not need provider-specific knowledge. Use the schema endpoint to generate tools, then pass an idempotency key for safe retries.
Fetch JSON Schema and tool metadata for each operation.
Call REST endpoints with normal auth and idempotency headers.
Parse the same structured envelope for success, partial results, or errors.
Share your use case and expected scale. We will reply with review status and next steps.