vrr/spawn
2
0
Fork 0
mirror of https://github.com/OpenRouterTeam/spawn.git synced 2026-05-04 14:50:17 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8
spawn/netcup
History
A 4b76b3422c
refactor: reduce complexity in execScript and netcup pick functions (#449) 
Extract error handling from execScript() into dedicated helpers
(reportDownloadError, reportScriptFailure, getScriptFailureGuidance),
reducing the function from 52 to 15 lines and making error guidance
directly testable.

Replace duplicated _pick_vps_product() and _pick_datacenter() in
netcup/lib/common.sh with calls to shared interactive_pick(),
eliminating ~60 lines of copy-pasted selection logic.

Net reduction: 42 lines (-98/+56).

Agent: complexity-hunter

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-02-11 05:56:48 -08:00
..
lib refactor: reduce complexity in execScript and netcup pick functions (#449) 2026-02-11 05:56:48 -08:00
aider.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
claude.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
codex.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
continue.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
gemini.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
goose.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
interpreter.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
nanoclaw.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
openclaw.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
README.md feat: Add Netcup cloud provider support (#407) 2026-02-11 01:34:59 -08:00

README.md

Netcup Cloud

Netcup VPS cloud via REST API. Netcup

Agents

Claude Code

bash <(curl -fsSL https://openrouter.ai/lab/spawn/netcup/claude.sh)

Aider

bash <(curl -fsSL https://openrouter.ai/lab/spawn/netcup/aider.sh)

Goose

bash <(curl -fsSL https://openrouter.ai/lab/spawn/netcup/goose.sh)

Non-Interactive Mode

NETCUP_SERVER_NAME=dev-mk1 \
NETCUP_CUSTOMER_NUMBER=12345 \
NETCUP_API_KEY=your-api-key \
NETCUP_API_PASSWORD=your-api-password \
OPENROUTER_API_KEY=sk-or-v1-xxxxx \
  bash <(curl -fsSL https://openrouter.ai/lab/spawn/netcup/claude.sh)

Authentication

Netcup uses session-based REST API authentication with three credentials:

  1. NETCUP_CUSTOMER_NUMBER - Your customer number
  2. NETCUP_API_KEY - API key from SCP
  3. NETCUP_API_PASSWORD - API password from SCP

Get your credentials:

The scripts will:

  1. Check for credentials in environment variables
  2. Check ~/.config/spawn/netcup.json
  3. Prompt for credentials if not found
  4. Save credentials to config file for reuse

Pricing

Budget VPS provider starting at approximately €3.86/month for entry-level VPS plans. Netcup offers flexible pricing with hourly billing or annual contracts.

API

Netcup's REST API launched in October 2025. It uses session-based authentication (login to get session ID, then use session ID for API calls). The API replaces the legacy SOAP web service (discontinued May 1, 2026).

API documentation is available in the Server Control Panel → REST API Docs.