Event Risk
by Event Risk - Next 7 Days in Markets & finance
Scheduled market-moving events for the next 7 days by default (?days= up to 90): US data releases with release times (CPI, jobs, GDP, PCE, PPI), FOMC, ECB and Bank of Japan decisions, Treasury auctions and dated crypto and regulatory milestones, each with importance 1-3 and official source. Use before any trade or scheduled action to know what is on the calendar. From official schedules, refreshed daily. JSON, no API key. $0.005 per call. Blockchain IQ.
https://www.blockchainiq.co/api/x402/v1/event-risk- Price
- $0.005
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 469 ms
- 1.0 s slowest 5%
- Last check
- Passed
- 58 min ago, next any minute now
Reliability
How to call it
GET https://www.blockchainiq.co/api/x402/v1/event-risk
Each call costs $0.005 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://www.blockchainiq.co/api/x402/v1/event-risk?days=7&minImportance=2Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
days | integer | No | Window length in days Default: 7. |
minImportance | integer | No | Lowest importance to include One of: 1, 2, 3. Default: 1. |
Example response
The provider's example. We can't check it without paying.
{
"count": 1,
"data": {
"days": 7,
"events": [
{
"category": "Macro",
"date": "2026-10-14",
"firm": true,
"id": "fred:10:2026-10-14",
"importance": 3,
"region": "US",
"source": "FRED",
"sourceUrl": "https://fred.stlouisfed.org/releases/calendar",
"time": "08:30",
"title": "Consumer Price Index (CPI)"
}
],
"from": "2026-10-10",
"highImportance": 1
},
"disclaimer": "Market data and analysis, not investment advice.",
"source": "Blockchain IQ",
"terms": "https://www.blockchainiq.co/terms"
}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.005.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://www.blockchainiq.co/api/x402/v1/event-risk?days=7&minImportance=2'
# 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://www.blockchainiq.co/api/x402/v1/event-risk?days=7&minImportance=2' \
| 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.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
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.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.blockchainiq.co%2Fapi%2Fx402%2Fv1%2Fevent-risk
const res = await pay("https://www.blockchainiq.co/api/x402/v1/event-risk?days=7&minImportance=2");
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.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://www.blockchainiq.co/api/x402/v1/event-risk?days=7&minImportance=2")
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 |
|---|---|---|---|---|
| 58 min ago | Passed | 402 | 534 ms | $0.005 |
| 5 h ago | Passed | 402 | 1.0 s | $0.005 |
| 9 h ago | Passed | 402 | 466 ms | $0.005 |
| 14 h ago | Passed | 402 | 462 ms | $0.005 |
| 18 h ago | Passed | 402 | 271 ms | $0.005 |
Show 10 older checks
| 22 h ago | Passed | 402 | 275 ms | $0.005 |
| 26 h ago | Passed | 402 | 309 ms | $0.005 |
| 30 h ago | Passed | 402 | 287 ms | $0.005 |
| 34 h ago | Passed | 402 | 264 ms | $0.005 |
| 38 h ago | Passed | 402 | 659 ms | $0.005 |
| 42 h ago | Passed | 402 | 314 ms | $0.005 |
| 46 h ago | Passed | 402 | 1.1 s | $0.005 |
| 2 days ago | Passed | 402 | 479 ms | $0.005 |
| 2 days ago | Passed | 402 | 679 ms | $0.005 |
| 2 days ago | Passed | 402 | 469 ms | $0.005 |