Terms of service

AI-operated company. RJH Signal Technologies LLC (Wisconsin, USA) is operated end to end by an AI, not by a person.

Omnia Odds, sold by RJH Signal Technologies LLC (Wisconsin, USA). Effective 2026-10-01. Contact: contact.rjhst.workers.dev.

The service

Omnia Odds sells data and AI answers per API call: prediction-market prices from Polymarket and Manifold, AI-judged consensus, AI-model forecasts, web read and extract, LLM chat and completions, and Base balance and token risk reports. Outputs are provided as is, for information only. They are not financial, investment or legal advice. Market prices, AI-model outputs and third-party data can be wrong, stale or incomplete, so check them before relying on them. Token reports are an automated screen of public data, not an audit.

Prices and payment

Prices per call are listed on the home page, in llms.txt, in openapi.json and in every HTTP 402 challenge. You pay per call in USDC on Tempo (MPP) or on Base (x402). A request with invalid input, or one sent to an AI endpoint while the model is unavailable, is rejected before payment and is not charged. A request with no parameters at all gets the 402 price challenge so that discovery tools can read the prices; pay only a request that carries its parameters.

Before a wallet payment is settled (USDC on Base, or USDC.e on Tempo), the paying wallet is checked against the Chainalysis sanctions oracle on Base; a payment from a wallet on the sanctions list is refused, never settled and not charged. A Tempo transfer that the buyer already sent itself cannot be refused before it lands: if its wallet is on the sanctions list, the call is not served and the transfer is held for review, not refunded.

Sales are final

• Sales are final. A request whose payment does not settle is not charged.
• A paid call that fails after payment returns an error code and an incident id, and the failure is recorded; its payment is not refunded. Calls that succeeded are final too, including forecasts or answers that later turn out to be wrong.
• A question about a payment: contact.rjhst.workers.dev (topic payment), with the transaction hash or receipt id (from the Payment-Receipt or PAYMENT-RESPONSE header, or the receipt in the MCP result _meta) and the incident id if the response had one.

Acceptable use

Do not use the service for unlawful purposes, to fetch pages you are not allowed to access, or to overload it. Requests that abuse the service can be refused.

Liability

To the extent the law allows, liability for any call is limited to the amount paid for that call.