Pm Sentiment
by clinkagent.com in Markets & finance
Prediction markets AND X/Twitter sentiment on the same question, one call. Headline Polymarket + Kalshi probability, a live X search built from your question, an AI read of whether the crowd on X leans YES or NO on that same market, and a computed aligned/diverges/no_clear_read against the market price. Event risk, news context, crowd-vs-market divergence, research grounding. ?q=<question or topic>. 404 free if no market matches on either platform.
https://clinkagent.com/pm/sentiment- Price
- $0.05
- per call in USDC
- Uptime
- 88.5%
- last 30 days
- Response time
- 334 ms
- 539 ms slowest 5%
- Last check
- Failed
- 2 h ago, next in 23 h
Reliability
Latest check failed 2 h ago: Expected HTTP 402, got 410
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://clinkagent.com/pm/sentiment
Each call costs $0.05 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://clinkagent.com/pm/sentiment?q=fed+rate+cut+septemberParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes |
Example response
The provider's example. We can't check it without paying.
{
"agreement": "aligned",
"market": {
"gap_pts": 1,
"kalshi": {
"probability": 0.04
},
"polymarket": {
"probability": 0.05
}
},
"query": "fed rate cut september",
"summary": "Markets price \"...\" at 5%. X chatter (18 recent posts) leans NO — aligned with the market.",
"x": {
"driving_accounts": [
"@example"
],
"key_themes": [
"rate hold"
],
"lean": "no",
"tweet_count": 18
}
}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.05.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://clinkagent.com/pm/sentiment?q=fed+rate+cut+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://clinkagent.com/pm/sentiment?q=fed+rate+cut+september' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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.05 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.05" });
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.05 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fclinkagent.com%2Fpm%2Fsentiment
const res = await pay("https://clinkagent.com/pm/sentiment?q=fed+rate+cut+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.05 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.05"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://clinkagent.com/pm/sentiment?q=fed+rate+cut+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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Expected HTTP 402, got 410 | 410 | 398 ms | - |
| 7 h ago | Expected HTTP 402, got 410 | 410 | 551 ms | - |
| 11 h ago | Expected HTTP 402, got 410 | 410 | 302 ms | - |
| 16 h ago | Expected HTTP 402, got 410 | 410 | 319 ms | - |
| 19 h ago | Expected HTTP 402, got 410 | 410 | 429 ms | - |
Show 10 older checks
| 21 h ago | Expected HTTP 402, got 410 | 410 | 289 ms | - |
| 24 h ago | Passed | 402 | 357 ms | $0.05 |
| 28 h ago | Passed | 402 | 497 ms | $0.05 |
| 31 h ago | Passed | 402 | 374 ms | $0.05 |
| 34 h ago | Passed | 402 | 334 ms | $0.05 |
| 37 h ago | Passed | 402 | 409 ms | $0.05 |
| 42 h ago | Passed | 402 | 418 ms | $0.05 |
| 47 h ago | Passed | 402 | 404 ms | $0.05 |
| 2 days ago | Passed | 402 | 278 ms | $0.05 |
| 2 days ago | Passed | 402 | 402 ms | $0.05 |