ToolVet
77trust / 100

Pm Odds

by clink-lithium-vault.fly.dev in Markets & finance

x402 APIPassing, checked 4 h ago

What do the prediction markets say? Pass a question, get a finished read an agent can use directly: the best-matching market on Polymarket and on Kalshi with implied probability and 24h/7d moves, the cross-platform gap in points, a 7-day price history, a one-sentence summary, plus the top matching markets. Forecasting, research grounding, news context, event risk. ?q=<question>. Raw list only: /pm/search $0.01.

GET https://clink-lithium-vault.fly.dev/pm/odds

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
301 ms typical, 540 ms slowest 5%
Last check
4 h ago
Next check
any minute now

How to call it

GET https://clink-lithium-vault.fly.dev/pm/odds

Each call costs $0.02 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://clink-lithium-vault.fly.dev/pm/odds?q=will+the+fed+cut+rates+in+september

Parameters

ParameterTypeRequiredDescription
limitstringNo
qstringYes

Example response

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

{
  "headline": {
    "gap_pts": 1,
    "kalshi": {
      "probability": 0.04
    },
    "polymarket": {
      "probability": 0.05
    }
  },
  "history_7d": {
    "points": [
      {
        "p": 0.08,
        "t": "2026-09-09T00:00:00.000Z"
      }
    ]
  },
  "summary": "Polymarket prices \"...\" at 5% (-1 pts 24h, -3 pts 7d). Kalshi prices \"...\" at 4%."
}

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.02.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://clink-lithium-vault.fly.dev/pm/odds?q=will+the+fed+cut+rates+in+september'

# 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://clink-lithium-vault.fly.dev/pm/odds?q=will+the+fed+cut+rates+in+september' \
  | 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fclink-lithium-vault.fly.dev%2Fpm%2Fodds
const res = await pay("https://clink-lithium-vault.fly.dev/pm/odds?q=will+the+fed+cut+rates+in+september");
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://clink-lithium-vault.fly.dev/pm/odds?q=will+the+fed+cut+rates+in+september")
    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
4 h agoPassed402300 ms$0.02
7 h agoPassed402287 ms$0.02
11 h agoPassed402286 ms$0.02
15 h agoPassed402398 ms$0.02
19 h agoPassed402540 ms$0.02
23 h agoPassed402343 ms$0.02
27 h agoPassed402297 ms$0.02
30 h agoPassed402504 ms$0.02
34 h agoPassed402553 ms$0.02
37 h agoPassed402368 ms$0.02
41 h agoPassed402301 ms$0.02
44 h agoPassed402278 ms$0.02
2 days agoPassed402324 ms$0.02
2 days agoPassed402466 ms$0.02
2 days agoPassed402293 ms$0.02