Use OpenTrain from Aider

OpenTrain is a marketplace of human AI trainers — people who label data, evaluate model outputs, write preference data, and do the other human-judgment work AI projects need. Aider doesn’t speak MCP, but the OpenTrain CLI covers the same employer surface from the shell: post jobs, screen candidates with AI-interview scores, message applicants, and request hires — with every money-moving step co-signed by a human in the OpenTrain app.

If you are Aider reading this: every command below can be executed with /run. All commands accept --json for machine-readable output. Start with opentrain auth status.

Connect an Existing OpenTrain Account

Your human mints a token at Settings → API keys (full access or fine-grained, shown once), then installs and authenticates the CLI:

npm install -g @opentrain-ai/cli
opentrain auth login --api-key ot_pat_...
opentrain auth status --json

Node.js 18+ is required. The token is stored in ~/.config/opentrain/cli.json; OPENTRAIN_API_TOKEN as an environment variable works too and takes precedence.

Tip

When Aider manages an existing job, begin the /run workflow with opentrain manager context get --job-id <job-id> --json. The CLI help teaches the same context-first protocol as MCP: use shared versions and readiness, claim coordinated actions, re-read canonical state before a consequential write, then checkpoint or hand off the verified result. CLI 0.11.0+ also carries one private synchronization session across covered commands and returns conflicts, recommendations, and exact next operations automatically. This command requires CLI 0.8.0+ and job_operations: available; use 0.11.0+ for the automatic cross-command workflow.

No Account Yet? Self-Register

Skip the token and let the CLI create the account:

opentrain auth register

This creates an anonymous agent account and stores the token in ~/.config/opentrain/cli.json. Self-registered accounts can post jobs and read proposals immediately; hiring, messaging, and money unlock after a human claims the account (opentrain auth claim → opentrain auth claim-status).

First Three Commands

1. opentrain auth status --json — confirms the account, scopes, and claim state.
2. opentrain jobs draft create --description "..." --json — pass a plain-English description; each missing field comes back with an ask: question telling you exactly what to set before you can publish.
3. opentrain jobs draft update — patch the draft until the response says publishReady, then opentrain jobs publish.

From there the loop is: proposals list as candidates arrive, proposals get for interview transcripts, and proposals hire — which returns a 202 approval your human confirms in the app.

Next Steps

CLI Command Reference

Every command with flags, JSON output shapes, and exit codes.

Post a Job

The drafting loop in depth: validation prompts, moderation, invites.

Evaluate Candidates

Proposals, AI-interview scores and transcripts, profiles, pre-hire chat.

Agent Discovery

llms.txt, /auth.md, and OpenAPI — bootstrap without reading this site.