Btc Factors
by PreReason in Onchain & crypto
What moved with the Bitcoin price. Multi-factor attribution across macro, on-chain, and derivatives positioning: the factors that moved beyond their own noise band in the same window, an association, not a cause. For research agents. A paid call serves today or any ?date= on record.
https://api.prereason.com/api/btc/factors- Price
- $0.05
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 474 ms
- 717 ms slowest 5%
- Last check
- Passed
- 4 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://api.prereason.com/api/btc/factors
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://api.prereason.com/api/btc/factors?format=jsonParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | No | Historical date in YYYY-MM-DD format. A paid call serves today or any ?date= on record. |
format | string | No | Response format. markdown is token-optimized for LLMs, json is structured. Default is markdown. One of: json, markdown. |
Example response
The provider's example. We can't check it without paying.
Example response, 62 lines
{
"briefing_metadata": {
"correlations_count": 6,
"description": "Rule-based \"why is Bitcoin moving\" with macro factors (Fed balance, TGA, net liquidity, dollar), on-chain factors (hash rate, volume), BTC perp derivatives positioning (funding rate + open interest), and 30-day ATM implied volatility",
"metrics_count": 17,
"name": "Factor Attribution"
},
"briefing_used": "btc.factors",
"metrics": {
"bitcoin-hash-rate": {
"name": "bitcoin-hash-rate"
},
"bitcoin-price": {
"name": "bitcoin-price"
},
"bitcoin-volume-24h": {
"name": "bitcoin-volume-24h"
},
"btc-perp-funding-zscore-30d": {
"name": "btc-perp-funding-zscore-30d"
},
"btc-perp-oi-contracts": {
"name": "btc-perp-oi-contracts"
},
"btc-perp-positioning-regime": {
"name": "btc-perp-positioning-regime"
},
"deribit-btc-iv-30d": {
"name": "deribit-btc-iv-30d"
},
"dxy": {
"name": "dxy"
},
"etf-tlt": {
"name": "etf-tlt"
},
"fed-balance": {
"name": "fed-balance"
},
"hash-ribbon": {
"name": "hash-ribbon"
},
"net-liquidity": {
"name": "net-liquidity"
},
"okx-btc-funding-rate": {
"name": "okx-btc-funding-rate"
},
"okx-btc-open-interest": {
"name": "okx-btc-open-interest"
},
"spy": {
"name": "spy"
},
"tga": {
"name": "tga"
},
"treasury-30y": {
"name": "treasury-30y"
}
}
}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://api.prereason.com/api/btc/factors?format=json'
# 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://api.prereason.com/api/btc/factors?format=json' \
| 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.prereason.com%2Fapi%2Fbtc%2Ffactors
const res = await pay("https://api.prereason.com/api/btc/factors?format=json");
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://api.prereason.com/api/btc/factors?format=json")
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 |
|---|---|---|---|---|
| 4 h ago | Passed | 402 | 448 ms | $0.05 |
| 9 h ago | Passed | 402 | 512 ms | $0.05 |
| 13 h ago | Passed | 402 | 717 ms | $0.05 |
| 18 h ago | Passed | 402 | 428 ms | $0.05 |
| 22 h ago | Passed | 402 | 521 ms | $0.05 |
Show 10 older checks
| 26 h ago | Passed | 402 | 529 ms | $0.05 |
| 30 h ago | Passed | 402 | 326 ms | $0.05 |
| 34 h ago | Passed | 402 | 625 ms | $0.05 |
| 39 h ago | Passed | 402 | 419 ms | $0.05 |
| 43 h ago | Passed | 402 | 470 ms | $0.05 |
| 47 h ago | Passed | 402 | 488 ms | $0.05 |
| 2 days ago | Passed | 402 | 460 ms | $0.05 |
| 2 days ago | Passed | 402 | 488 ms | $0.05 |
| 2 days ago | Passed | 402 | 583 ms | $0.05 |
| 3 days ago | Passed | 402 | 456 ms | $0.05 |