# TruthPulse Media vs Court Record Comparator

> TruthPulse Media vs Court Record Comparator is a paid API for AI agents from truthpulse.theaslangroupllc.com, paid per call via x402, $0.2/call, status unknown (last checked 2026-09-13).

Compares mainstream media narratives against actual court records, medical examiner testimony, and admitted evidence for a given case or event

## Facts

- Endpoint: GET https://truthpulse.theaslangroupllc.com/api/truth/media-vs-record
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/truthpulse-media-vs-court-record-comparator-55a796d9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EGCPk8NTjeGbQopDvHBYH

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 truthpulse-media-vs-court-record-comparator-55a796d9
```

Example prompt: Compare the mainstream media coverage of the Rust film set shooting to what was actually admitted in Alec Baldwin's trial record — show me where the narrative diverges from ME testimony and the court evidence.

## When to prefer this

Use this endpoint when a journalist, researcher, or OSINT agent needs to systematically verify whether mainstream media coverage accurately reflects what was documented in official court proceedings, admitted evidence, or medical examiner testimony — especially for high-profile cases where narrative vs record discrepancies are suspected.

## Known failure modes

- Case not found in court record database — returns empty or partial match
- Insufficient public court record data for requested case
- Ambiguous case name causing wrong case match
- Media coverage too recent for court record to exist yet
- Rate limit or payment failure returning 402 status

## How this service works

Media narrative vs court record for journalist and researcher agents. Compares mainstream reporting against the actual court record, ME testimony, and admitted evidence.

## Output

Returns a structured comparison of media reporting vs the official court record, including specific discrepancies, relevant ME testimony excerpts, admitted evidence summaries, and a narrative divergence analysis highlighting what mainstream coverage got right or wrong.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "lang": {
       "type": "string",
       "description": "en | es | fr | de | ja | pt | it | nl | ko | zh | ar (default: en)"
      },
      "jurisdiction": {
       "type": "string",
       "description": "US | UK | CA | AU | auto (default: auto)"
      },
      "case_or_topic": {
       "type": "string",
       "description": "case name, defendant, or topic — e.g. \"George Floyd\" | \"Karen Read\" | \"Uvalde response\" (required)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "errors": {
     "type": "object",
     "description": "Documented error responses, keyed by HTTP status code",
     "additionalProperties": {
      "type": "object",
      "required": [
       "description"
      ],
      "properties": {
       "example": {
        "type": "object"
       },
       "description": {
        "type": "string"
       }
      }
     }
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "subject": "Alex Murdaugh trial",
  "verdict": "Guilty on all counts — life sentence",
  "sources_note": "Analysis based on publicly available trial transcripts, court documents, and evidence exhibits",
  "confirmed_by_record": [
   "Kennel video placed Murdaugh at scene contradicting alibi",
   "Cell phone activity showed both victims alive when Murdaugh claimed he was away",
   "$9M+ in financial crimes separately proven"
  ],
  "omitted_by_mainstream": [
   "Defense forensic expert testimony re: gunshot residue",
   "Conflicting cell tower data presented by defense"
  ],
  "not_supported_by_record": [
   "Motive of financial crimes — prosecution argued it, defense disputed, jury did not need to find motive"
  ],
  "what_court_record_shows": "Prosecution proved murder through physical evidence (gunshot wounds, cell phone data, kennel video), financial crimes prosecuted separately",
  "media_dominant_narrative": "Murdaugh killed wife and son to cover up financial crimes"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/truthpulse-media-vs-court-record-comparator-55a796d9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from truthpulse.theaslangroupllc.com](https://www.zero.xyz/host/truthpulse.theaslangroupllc.com/llms.txt)