Invite-only agent gateway

Give your agent a safe way to ask a human.

One work order across REST, MCP, CLI, the portal, and Cliviti—with deterministic acknowledgement, human gates, and evidence-backed technical delivery.

<60 secpilot acknowledgement target
≤15 minpilot triage target in staffed hours
2 humansfor production approval

The delivery path

From machine request to human-verified outcome.

  1. Receive

    A durable work order and triage deadline are returned without pretending the requested deadline is confirmed.

  2. Scope & quote

    A human produces fixed scope, acceptance criteria, ETA, and price. A human customer approves and pays.

  3. Dispatch

    Cliviti reserves capacity and a PU dispatcher approves an eligible assignee. Only then is delivery confirmed.

  4. QA preview

    Work runs in isolation and returns a protected preview with tests, scans, commit SHA, and rollback evidence.

  5. Approved release

    Production requires customer approval and a distinct PU release manager, both bound to the exact build.

Technical work only

Review, debugging, testing, hardening, and deployment support.

V1 is built for the work around an AI or vibe-code build that still needs judgement: reproducing failures, tightening security, checking dependencies, producing evidence, and handing off a release.

Technical review and architecture checks

Bug reproduction and repair

Automated and exploratory testing

Security and dependency hardening

Preview verification and release handoff

Consent-based technical liaison

Authority by design

The agent gets progress—not power over people.

What an agent can see

  • Opaque work-order and repository-grant references
  • Status, public events, deadlines, and action-required codes
  • Quote amount and a human-only approval URL
  • Preview URL, commit SHA, and evidence status

What an agent never sees

  • Worker identity, payroll, private calendar, email, or phone
  • Payment-provider, GitHub App, Cliviti, or Vercel credentials
  • Quote, assignment, payout, or production-approval authority
  • Unconsented human-to-human contact details

One contract

REST is canonical. MCP and CLI stay thin.

POST /v1/work-orders

REST

Stable JSON, explicit scopes, idempotency, problem details, and cursor events.

request_human_task

MCP

The same operation and authority expressed as six focused tools.

pu work create --file

CLI

Keychain-backed human login, stable JSON, and followable JSONL events.

Deadlines without theatre

Requested first. Confirmed after capacity.

requestedDeadline is the agent’s request. triageBy is calculated at intake. confirmedDeliveryAt remains null until Cliviti reserves capacity and a PU dispatcher approves the assignee.

Staffed triage: Monday–Saturday, 09:00–21:00 IST.

Pilot access

Connect an agent. Keep every consequential decision human.

We onboard one organization at a time, test the contract in a credential-isolated sandbox, and leave production off until the approval and rollback drill passes.

Human-in-the-Loop Gateway for AI Agents | Programmers' Union