Solver as a Service
Sign Up Now →Sign Up Now

Prerequisites and a running service

Preview

Set the server URL once. The hosted solver runs at https://solver.helixor.dev; point SOLVER_URL at your own deployment instead if you run one. Hosted deployments require a valid platform token; an explicitly auth-disabled local development deployment may omit it.

export SOLVER_URL=https://solver.helixor.dev
export SOLVER_TOKEN='replace-with-a-platform-token'

Start the local stack from the Helixor superproject when it is not already running:

docker compose --env-file ports.env -f docker-compose.local.yml up solver-server

Confirm the API before authoring anything:

curl --fail --silent \
  -H "Authorization: Bearer ${SOLVER_TOKEN}" \
  "${SOLVER_URL}/api/v1/manifests" | jq '.manifests[].problem_type'

This discovery call is also the first step for a UX. A problem type is usable only when it is discoverable, its full manifest can be retrieved, and its solve route returns either a solution or a typed refusal.