Hip4 Alerts Subscribe
by AlphaPipeline HIP-4 Alerts in Markets & finance
[EXPERIMENTAL] Subscribe a webhook to receive push notifications when a HIP-4 outcome's probability jumps past a configurable threshold, or a new market appears - so an agent no longer has to poll hip4-snapshot itself. Polls Hyperliquid every ~5 minutes; not a true real-time feed. GET with query params, not JSON body - secret travels in the URL. See free GET /v1/prediction/hip4-alerts/event-types for the event catalog. Paid in USDC on Base.
https://alphapipeline-eu.onrender.com/v1/prediction/hip4-alerts/subscribe- Price
- $0.02
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 142 ms
- 215 ms slowest 5%
- Last check
- Passed
- 52 min ago, next any minute now
Reliability
How to call it
GET https://alphapipeline-eu.onrender.com/v1/prediction/hip4-alerts/subscribe
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://alphapipeline-eu.onrender.com/v1/prediction/hip4-alerts/subscribe?secret=replace-with-your-own-32-byte-random-secret&underlying=BTC&webhook_url=https%3A%2F%2Fexample.com%2Fwebhooks%2FalphapipelineParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
event_types | array of string | No | Subset of event types to receive (default: all). See GET hip4-alerts/event-types. |
secret | string | Yes | Caller-generated shared secret (>=16 chars) used to HMAC-SHA256 sign each delivery. Not stored anywhere you can retrieve it later - keep your own copy. Travels in the URL query string (GET) - see the endpoint description. |
threshold_pct | number | No | Optional per-subscription override of the prob_jump threshold (0.0-1.0 scale). |
underlying | string | No | Optional filter: only this crypto underlying's markets (e.g. 'BTC'). |
webhook_url | string (uri) | Yes | https:// endpoint to receive signed POST deliveries. Private/loopback IPs are rejected. |
Example response
The provider's example. We can't check it without paying.
{
"created_at": 1790700000,
"event_types": [
"hip4.prob_jump",
"hip4.market_created"
],
"expires_at": 1790786400,
"notice": "EXPERIMENTAL - based on a draft MCP Events spec that has not stabilized. This is 5-minute-interval polling, not a true push feed. Subscriptions are not guaranteed to survive a server restart. Renew by subscribing again before expires_at.",
"status": "active",
"subscription_id": "sub_3f9a7c2e1b4d5f6a7b8c",
"threshold_pct": null,
"underlying": "BTC",
"webhook_url": "https://example.com/webhooks/alphapipeline"
}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://alphapipeline-eu.onrender.com/v1/prediction/hip4-alerts/subscribe?secret=replace-with-your-own-32-byte-random-secret&underlying=BTC&webhook_url=https%3A%2F%2Fexample.com%2Fwebhooks%2Falphapipeline'
# 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://alphapipeline-eu.onrender.com/v1/prediction/hip4-alerts/subscribe?secret=replace-with-your-own-32-byte-random-secret&underlying=BTC&webhook_url=https%3A%2F%2Fexample.com%2Fwebhooks%2Falphapipeline' \
| 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.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%2Falphapipeline-eu.onrender.com%2Fv1%2Fprediction%2Fhip4-alerts%2Fsubscribe
const res = await pay("https://alphapipeline-eu.onrender.com/v1/prediction/hip4-alerts/subscribe?secret=replace-with-your-own-32-byte-random-secret&underlying=BTC&webhook_url=https%3A%2F%2Fexample.com%2Fwebhooks%2Falphapipeline");
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://alphapipeline-eu.onrender.com/v1/prediction/hip4-alerts/subscribe?secret=replace-with-your-own-32-byte-random-secret&underlying=BTC&webhook_url=https%3A%2F%2Fexample.com%2Fwebhooks%2Falphapipeline")
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 |
|---|---|---|---|---|
| 52 min ago | Passed | 402 | 211 ms | $0.02 |
| 5 h ago | Passed | 402 | 215 ms | $0.02 |
| 9 h ago | Passed | 402 | 227 ms | $0.02 |
| 14 h ago | Passed | 402 | 194 ms | $0.02 |
| 18 h ago | Passed | 402 | 153 ms | $0.02 |
Show 10 older checks
| 22 h ago | Passed | 402 | 187 ms | $0.02 |
| 26 h ago | Passed | 402 | 106 ms | $0.02 |
| 30 h ago | Passed | 402 | 175 ms | $0.02 |
| 34 h ago | Passed | 402 | 73 ms | $0.02 |
| 38 h ago | Passed | 402 | 200 ms | $0.02 |
| 42 h ago | Passed | 402 | 95 ms | $0.02 |
| 46 h ago | Passed | 402 | 154 ms | $0.02 |
| 2 days ago | Passed | 402 | 97 ms | $0.02 |
| 2 days ago | Passed | 402 | 211 ms | $0.02 |
| 2 days ago | Passed | 402 | 122 ms | $0.02 |