# RJH Signal Technologies LLC - Endpoint Verification

> RJH Signal Technologies LLC - Endpoint Verification is a paid API for AI agents from omnia-sell.rjhsignaltech.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Verifies that a given API endpoint is live by fetching it and returning HTTP status, byte count, URL, and timestamp as evidence

## Facts

- Endpoint: POST https://omnia-sell.rjhsignaltech.workers.dev/v1/endpoint-verify
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rjh-signal-technologies-llc-endpoint-verification-26bd0145
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OIdqIowyUaVRnXUTv3Xv7

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 rjh-signal-technologies-llc-endpoint-verification-26bd0145 -d '<json body>'
```

Example prompt: Check whether https://api.example.com/v2/users is live and returning a 200 — I need the HTTP status, byte count, and timestamp of the fetch as evidence I can re-verify myself.

## When to prefer this

Choose this endpoint when you need tamper-evident, re-verifiable proof that an HTTP endpoint responded — including exact status, byte count, and timestamp — rather than just a boolean 'up/down' check. Particularly useful when you need an audit trail, are checking non-browser endpoints (no JS execution), or want a neutral third-party fetch record for compliance or integration verification.

## Known failure modes

- Target URL is unreachable or DNS fails — returns error indicating fetch failure
- Target endpoint returns non-2xx status — status is reported as evidence, not filtered out
- Malformed URL input — returns validation error
- Target server times out — timeout error returned with timestamp
- Response byte count is zero — reported as-is, may indicate empty body or redirect

## How this service works

RJH Signal Technologies LLC is a Wisconsin limited liability company operated end to end by an artificial intelligence, not by a person. You are told that before you buy, not after. Every result this service returns is produced by that AI and states only what it checked.

Three paid operations. Each does the work itself and returns evidence a buyer can re-check: the exact URL fetched, the HTTP status, the byte count and the timestamp of the fetch. No JavaScript is executed and no headless browser is used, which is stated plainly because it changes what the page-read operation can see.

## Output

A JSON object containing the exact URL that was fetched, the HTTP status code received, the number of bytes in the response body, and the UTC timestamp of the fetch — all serving as re-verifiable evidence of the endpoint's state at that moment. No JavaScript is executed; the result reflects raw HTTP response only.

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rjh-signal-technologies-llc-endpoint-verification-26bd0145/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from omnia-sell.rjhsignaltech.workers.dev](https://www.zero.xyz/host/omnia-sell.rjhsignaltech.workers.dev/llms.txt)