16trust / 100

Event Odds

by CryptoPulse in Onchain & crypto

x402 APIFailing, checked 2 h ago

Real-money implied probabilities for macro and sports events from Hyperliquid HIP-4 outcome markets. Answers "what odds does the market put on a Fed rate cut this month", "who is favored to win the World Cup", "what is the implied probability of this event". Every live question with its outcomes and Yes-side implied probability, straight from on-chain order mids — money-backed odds, not polls and not a model. Deterministic, no LLM.

GET
https://cryptopulse.theaslangroupllc.com/api/event-odds
Price
$0.03
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
2 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 2 h ago: Amount "0.03" is not in atomic token units

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://cryptopulse.theaslangroupllc.com/api/event-odds

Each call costs $0.03 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://cryptopulse.theaslangroupllc.com/api/event-odds?q=fed

Parameters

ParameterTypeRequiredDescription
qstringNooptional substring filter on the question name, e.g. fed, world cup

Example response

The provider's example. We can't check it without paying.

{
  "deterministic": true,
  "questions": [
    {
      "name": "July Fed funds decision",
      "outcomes": [
        {
          "implied_probability": 0.76,
          "name": "No change"
        },
        {
          "implied_probability": 0.24,
          "name": "Decrease"
        }
      ]
    }
  ]
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.03.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://cryptopulse.theaslangroupllc.com/api/event-odds?q=fed'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://cryptopulse.theaslangroupllc.com/api/event-odds?q=fed' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.03 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.03" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.03 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fcryptopulse.theaslangroupllc.com%2Fapi%2Fevent-odds
const res = await pay("https://cryptopulse.theaslangroupllc.com/api/event-odds?q=fed");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.03 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.03"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://cryptopulse.theaslangroupllc.com/api/event-odds?q=fed")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
2 h agoAmount "0.03" is not in atomic token units402270 ms$0.03
6 h agoAmount "0.03" is not in atomic token units402257 ms$0.03
12 h agoAmount "0.03" is not in atomic token units402495 ms$0.03
17 h agoAmount "0.03" is not in atomic token units402265 ms$0.03
23 h agoAmount "0.03" is not in atomic token units402221 ms$0.03
Show 10 older checks
29 h agoAmount "0.03" is not in atomic token units402209 ms$0.03
34 h agoAmount "0.03" is not in atomic token units402210 ms$0.03
40 h agoAmount "0.03" is not in atomic token units4021.2 s$0.03
46 h agoAmount "0.03" is not in atomic token units402285 ms$0.03
2 days agoAmount "0.03" is not in atomic token units4021.9 s$0.03
2 days agoAmount "0.03" is not in atomic token units402309 ms$0.03
3 days agoAmount "0.03" is not in atomic token units4021.1 s$0.03
3 days agoAmount "0.03" is not in atomic token units402489 ms$0.03
3 days agoAmount "0.03" is not in atomic token units402226 ms$0.03
3 days agoAmount "0.03" is not in atomic token units402420 ms$0.03