# Monexus Terminal Thread Context API

> Monexus Terminal Thread Context API is a paid API for AI agents from terminal.themonexus.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Returns full contextualized thread data for a given seed thread ID, including related items, sources, entities, summary, and timespan

## Facts

- Endpoint: POST https://terminal.themonexus.com/api/v1/thread/4d108257640e8caa7225a6968f5902eb23714cb4/context
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/monexus-terminal-thread-context-api-a12c6244
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zVD3ToaI8W59NPaXshzXi

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 monexus-terminal-thread-context-api-a12c6244 -d '<json body>'
```

Example prompt: Can you pull the full context brief for thread ID 4d108257640e8caa7225a6968f5902eb23714cb4 from Monexus Terminal — I need the related items, sources, entities, summary, and timespan all in one go.

## When to prefer this

Use this endpoint when you have a specific thread seed ID and need the full contextual brief — related items, entities, sources, summary, and timespan — rather than browsing the latest wire feed or fetching a single article by slug. It is the right choice when reconstructing discussion context or enriching a thread with surrounding intelligence from the Monexus Terminal platform.

## Known failure modes

- Invalid or unknown thread ID returns 404 or empty result
- Malformed POST body returns 400 bad request
- Thread ID exists but has no context data yet returns empty context fields
- Payment failure via x402 protocol returns 402 Payment Required
- Rate limiting or quota exceeded returns 429 Too Many Requests

## How this service works

Monexus Terminal API — Full context brief: /api/v1/thread/{id}/context.

## Output

A JSON object containing the thread's contextualized data: related wire items linked to the seed thread, source references, named entities extracted from the discussion, a summary of the thread, and a timespan indicating the temporal range of the discussion.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/monexus-terminal-thread-context-api-a12c6244/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from terminal.themonexus.com](https://www.zero.xyz/host/terminal.themonexus.com/llms.txt)