← Home/

Getting Started with HELVA CLOUD

Fast onboarding for builders and developers who want to start a workflow, explore the API, or prepare an MVP stack.

Docs status: active draft • Last docs sync: 2026-02-24

Page Summary

Quick Answer

Start by identifying your goal (MVP, API integration, AI workflow, or internal tools), then use the docs paths on this page to set up authentication, test a first request pattern, and move into workflow-specific guides.

Who this is for

  • - Builders
  • - Founders
  • - Developers
  • - Coding assistants generating starter code

What you can do here

  • - Choose the right start path by goal
  • - Prepare environment variables and credentials
  • - Test a first request pattern
  • - Move to API, workflow, or integration docs

Code examples on this page

  • - cURL: Yes
  • - JavaScript/TypeScript: Yes
  • - Python: Yes
  • - JSON request/response: Yes
  • - Config snippets: Yes
  • - Status labels: Planned, Active draft

Related docs

Last updated
2026-02-24

How do I get started with HELVA CLOUD?

  1. 1. Decide your primary goal: founder MVP, developer integration, AI workflow, or internal tool delivery.
  2. 2. Review Core Concepts for platform terminology and workflow model.
  3. 3. Configure credentials and environment variables (see Authentication).
  4. 4. Test a first request pattern in cURL, JavaScript/TypeScript, or Python.
  5. 5. Continue with a task guide in Workflows.

Recommended start paths by goal

  • - Founder MVP: start with Workflows, then Examples, then Pricing.
  • - Developer integration: start with Authentication, API Reference, and Errors.
  • - AI workflow: start with LLM Usage Guide, Workflows, and Integrations.
  • - Internal tool delivery: start with Workflows, API Reference, and Performance.
Environment setup (starter placeholder)
.envPlanned
HELVA_CLOUD_BASE_URL=https://helva.cloud
HELVA_API_KEY=hc_your_api_key_here
HELVA_PROJECT_ID=proj_your_project_id

# Integration examples (optional)
SUPABASE_URL=https://your-project.supabase.co
SUPABASE_ANON_KEY=your_supabase_key
First request pattern (cURL placeholder)
bashPlanned
curl -X GET "$HELVA_CLOUD_BASE_URL/api/v1/projects/$HELVA_PROJECT_ID" \
  -H "Authorization: Bearer $HELVA_API_KEY" \
  -H "Accept: application/json"
First request pattern (TypeScript placeholder)
tsPlanned
const res = await fetch(
  `${process.env.HELVA_CLOUD_BASE_URL}/api/v1/projects/${process.env.HELVA_PROJECT_ID}`,
  {
    headers: {
      Authorization: `Bearer ${process.env.HELVA_API_KEY}`,
      Accept: "application/json",
    },
  }
);

if (!res.ok) {
  throw new Error(`HELVA CLOUD request failed: ${res.status}`);
}

const data = await res.json();
console.log(data);
First request pattern (Python placeholder)
pythonPlanned
import os
import requests

url = f"{os.environ['HELVA_CLOUD_BASE_URL']}/api/v1/projects/{os.environ['HELVA_PROJECT_ID']}"
headers = {
    "Authorization": f"Bearer {os.environ['HELVA_API_KEY']}",
    "Accept": "application/json",
}

response = requests.get(url, headers=headers, timeout=30)
response.raise_for_status()
print(response.json())

What is available now vs planned?

  • - Current site: public landing page and private app launcher pattern.
  • - Current repo capability: OpenClaw usage ingestion endpoint pattern and usage dashboard.
  • - Planned docs expansion: public API reference, integrations, SDKs, rate limits, errors, pricing, and performance pages.