Moveworks

​

Prerequisites

• Data API credentials, minted by a Moveworks superadmin (Moveworks Setup → Credentials). API key and OAuth2 client-credentials are both offered there; the importer takes the key and sends it as Authorization: Bearer <key> (override the header/scheme if your deployment differs).
• An AgentX project API key (self-host: Settings → API access).

​

CLI: scheduled sync

export MOVEWORKS_API_KEY=...            # Data API credential
export AGENTX_API_KEY=agtx_local_...    # AgentX project key
export AGENTX_API_BASE_URL=http://localhost:4700/api/v1   # self-host engine

agentx-moveworks sync --since 7d        # first backfill (Data API retains 30 days)
agentx-moveworks sync                   # cron this - continues from the cursor

• Pattern/built-in checks (PII, empty response, tool failure, active patterns) and trace-scoped online evaluators run on every imported trace automatically, same as any live traffic - no flag needed (--monitor is kept for compatibility).
• --judge-sessions judges every imported session with each enabled session-scoped evaluator (Session Baseline Judge included) after the sync. Needed for backfills: the engine’s automatic session sweep only looks at the last 24 hours of activity, so older imported conversations would otherwise never get a session verdict. The requests carry ifStale=true, so a session the sweep (or a previous run) already scored is skipped, never judged twice. Each judgment is a real LLM call - budget accordingly on large backfills.
• --evaluate-against <dataset_or_config_id> grades each new imported interaction’s recorded input/output against that grading config’s criteria - see Evaluating Moveworks agents below.

​

Python API

from datetime import datetime, timedelta, timezone
from agentx.integrations.moveworks import MoveworksDataAPIClient, MoveworksImporter

client = MoveworksDataAPIClient(api_key="mw-data-api-key")
importer = MoveworksImporter(
    client,
    agentx_api_key="agtx_local_...",
    agentx_base_url="http://localhost:4700/api/v1",
)
report = importer.sync(since=datetime.now(timezone.utc) - timedelta(days=1))
print(report)  # conversations/interactions/ingested/failed counts

​

Evaluating Moveworks agents

• --evaluate-against <id> grades each imported interaction against a grading config during the sync (one judge call per new interaction - the engine’s span dedupe means re-syncing a window never re-bills). Each verdict is recorded as a real one-result evaluation run, so ratings and justifications show up under Evaluate → Runs, and the report prints the average:
  agentx-moveworks sync --since 7d --evaluate-against <grading_config_id>
  # MoveworksSyncReport(..., traces_evaluated=142 (avg 7.3/10), eval_skipped_deduped=0, ...)
  
• The same thing per trace from code: client.tracer.evaluate_trace(trace_id, dataset_id).
• Datasets from production: any synced trace or conversation converts to a golden dataset case (multi-turn included) - the regression suite for grading future synced traffic, or the benchmark for evaluating a candidate replacement.
• Model portability: replay a synced interaction’s input against other models (client.monitor.run_model_portability(trace_id, [...])) for a cost/quality comparison.
• If your deployment exposes any inbound HTTP entry point, the http_endpoint adapter closes the loop with real dataset runs.

​

Behavior and limits

• Idempotent: every trace carries a deterministic span_id (mw:<interaction_id>) and the engine skips spans it has already ingested, so re-syncing a window never duplicates.
• Historical timestamps are honored: traces land in AgentX dated when the conversation happened, not when it was imported, so the Overview windows, cost chart buckets, and session timelines attribute correctly.
• Near-real-time, not live: the Data API follows a ~24-hour freshness SLA and retains 30 days - an hourly or daily sync is the honest cadence.
• No token counts: Moveworks does not export usage, so these traces contribute nothing to the LLM cost chart.
• No fabricated failures: plugin calls carry served/used flags, not success/failure - the importer records those flags verbatim and never marks a tool call failed, so Moveworks traffic cannot generate false tool-failure signals.
• Deployment-tolerant field mapping: Data API field names vary between deployments and API versions; the importer reads each field from a list of known candidates and skips only records with no parseable timestamp (counted in the report as skipped_no_time).