78trust / 100
Resolution Verdict
by SYNTHORA in Markets & finance
x402 APIPassing, checked 4 h ago
Decision verdict for prediction markets: probability, direction and multi-source evidence with declared sources. $0.05 USDC x402 Base.
POST
https://api.hergertsynthora.com/v1/resolution-verdict- Price
- $0.05
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 284 ms
- 382 ms slowest 5%
- Last check
- Passed
- 4 h ago, next any minute now
Reliability
All checks passedSome failedAll failedNot checked
How to call it
POST https://api.hergertsynthora.com/v1/resolution-verdict
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.
POST https://api.hergertsynthora.com/v1/resolution-verdict
content-type: application/json
{
"slug": "strait-of-hormuz-traffic-returns-to-normal-by-december-31"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
input | string | No | Decision verdict for prediction markets: probability, direction and multi-source evidence with declared sources. $0.05 USDC x402 Base. |
Example response
The provider's example. We can't check it without paying.
{
"niche": "resolution_verdict",
"ok": true,
"receipt": {
"alg": "ed25519"
},
"result": {}
}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 -X POST 'https://api.hergertsynthora.com/v1/resolution-verdict' \
-H 'content-type: application/json' \
--data-raw '{"slug":"strait-of-hormuz-traffic-returns-to-normal-by-december-31"}'
# 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 - -X POST 'https://api.hergertsynthora.com/v1/resolution-verdict' \
-H 'content-type: application/json' \
--data-raw '{"slug":"strait-of-hormuz-traffic-returns-to-normal-by-december-31"}' \
| 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%2Fapi.hergertsynthora.com%2Fv1%2Fresolution-verdict&method=POST
const res = await pay("https://api.hergertsynthora.com/v1/resolution-verdict", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"slug": "strait-of-hormuz-traffic-returns-to-normal-by-december-31"
}),
});
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.post(
"https://api.hergertsynthora.com/v1/resolution-verdict",
json={
"slug": "strait-of-hormuz-traffic-returns-to-normal-by-december-31",
},
)
print(res.status_code, res.text)Security scan
1 finding
- Payment address changed recently in payment
Payment address changed from 0xEf879BFD6C4AccB8F795136de90246e1EC245e06 to 0x6D9F318463168fF637b50E5b9a21392e97c7c167
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 4 h ago | Passed | 402 | 254 ms | $0.05 |
| 9 h ago | Passed | 402 | 335 ms | $0.05 |
| 13 h ago | Passed | 402 | 234 ms | $0.05 |
| 17 h ago | Passed | 402 | 382 ms | $0.05 |
| 21 h ago | Passed | 402 | 322 ms | $0.05 |
Show 10 older checks
| 25 h ago | Passed | 402 | 161 ms | $0.05 |
| 29 h ago | Passed | 402 | 292 ms | $0.05 |
| 33 h ago | Passed | 402 | 335 ms | $0.05 |
| 37 h ago | Passed | 402 | 283 ms | $0.05 |
| 41 h ago | Passed | 402 | 300 ms | $0.05 |
| 45 h ago | Passed | 402 | 417 ms | $0.05 |
| 2 days ago | Passed | 402 | 322 ms | $0.05 |
| 2 days ago | Passed | 402 | 188 ms | $0.05 |
| 2 days ago | Passed | 402 | 225 ms | $0.05 |
| 2 days ago | Passed | 402 | 233 ms | $0.05 |
History
| 12 Oct 2026 | Payment address changed from 0xEf879BFD6C4AccB8F795136de90246e1EC245e06 to 0x6D9F318463168fF637b50E5b9a21392e97c7c167 |