https://pin.ariacompute.com) under the /v1 prefix.
Training capabilities
PIN supports a range of training types and export formats.GET /v1/capabilities returns the catalog available to your account:
Jobs and workflow
A training job’s lifecycle spans datasets, checkpoints, and models:- Datasets — pulled from the catalog or created; see Dataset catalog.
- Jobs — submit fine-tuning / LoRA / RL jobs; see Create a job. Hot-intervene on hyperparameters or cancel while running; see Intervene.
- Checkpoints — intermediate artifacts written during training, listable and mergeable; see Checkpoints.
- Models — model records produced by training, downloadable, mergeable, acceptable, or reloadable; see Models.
- Exports — convert output to the target on-device format; see Export.
Cloud entrypoint
The PIN API base URL ishttps://pin.ariacompute.com; all /v1/* routes require a Bearer API key in Authorization (except public routes /health, /version, /v1/auth/login, /v1/auth/register). Node-agent callbacks under /v1/agent/* additionally require X-Agent-Secret equal to the server AGENT_REGISTER_SECRET. Successful responses use { "code": 0, "data": …, "message": "" }.
GPU nodes and agents
Training runs on GPU nodes, which node agents onboard to the control plane through register, heartbeat, acquire, and metrics reporting; see GPU nodes. The agent runs training and reuses the weights it holds to reload models, so PIN has no separate inference serving process.How to run
- PIN API introduction — overview of the HTTP endpoints for submitting and monitoring post-training jobs.
- Related: AFM foundation models (training output ships as model bundles), ROUTER decision routing, AGENT cloud agents.