# med.halowerk.com Clinical Trial Status Monitor

> med.halowerk.com Clinical Trial Status Monitor is a paid API for AI agents from med.halowerk.com, paid per call via x402, $0.006/call, status unknown (last checked 2026-09-14).

Monitors registered clinical trials for changes over time by storing a baseline snapshot on first call and reporting diffs in status, enrollment, dates, sites, and results on subsequent calls using a session token.

## Facts

- Endpoint: POST https://med.halowerk.com/v1/trial-status-monitor
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/med-halowerk-com-clinical-trial-status-monitor-6aaa32f9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BqTP2T1F9A0OSgjUzEt-E

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability med-halowerk-com-clinical-trial-status-monitor-6aaa32f9 -d '<json body>'
```

Example prompt: Start monitoring clinical trial NCT04280705 for me — I want to know when its recruitment status, enrollment target, completion dates, site count, or results posting changes from the current state.

## When to prefer this

Choose this endpoint when you need stateful, ongoing monitoring of a clinical trial registry entry over time rather than a one-time lookup. It is purpose-built for detecting incremental changes across specific fields (status, enrollment, dates, sites, results) without re-processing the full record manually. Prefer it over a plain trial-lookup endpoint when your workflow requires drift detection, alerts on change, or audit trails of registry evolution.

## Known failure modes

- Invalid or unrecognized trial identifier returns an error indicating the trial was not found in the registry
- Expired or invalid session token causes the endpoint to reject the comparison request and require a new baseline call
- Trial registry source temporarily unavailable results in a service error
- No changes detected returns an empty diff with confirmation that state matches the stored snapshot
- Malformed request body returns a validation error

## How this service works

A monitor with memory over registered trials. The first call stores a snapshot and returns the baseline explicitly marked as such rather than reporting everything as new. Each later call with the returned token compares the current registry state and reports the differences: recruitment status, enrolment target, primary and overall completion dates, the number of sites, and whether results have been posted.

## Output

On first call: a baseline snapshot of the trial's current registry state (recruitment status, enrolment target, primary and overall completion dates, site count, results posting status) explicitly marked as a baseline, plus a session token for future comparisons. On subsequent calls with the token: a structured diff report listing only fields that changed between the stored snapshot and the current registry state.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "nct_ids": {
   "type": "array",
   "items": {
    "type": "string",
    "maxLength": 20,
    "minLength": 5
   },
   "maxItems": 25,
   "minItems": 1
  },
  "snapshot_token": {
   "type": "string",
   "maxLength": 80
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/med-halowerk-com-clinical-trial-status-monitor-6aaa32f9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from med.halowerk.com](https://www.zero.xyz/host/med.halowerk.com/llms.txt)