78trust / 100

Btc Context

by PreReason in Onchain & crypto

x402 APIPassing, checked 5 h ago

Bitcoin context with on-chain and liquidity data. Active addresses, hash ribbon, difficulty and momentum, each with its trend, for AI agents. A paid call serves today or any ?date= on record.

GET
https://api.prereason.com/api/btc/context
Price
$0.02
per call in USDC
Uptime
100%
last 30 days
Response time
586 ms
836 ms slowest 5%
Last check
Passed
5 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://api.prereason.com/api/btc/context

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://api.prereason.com/api/btc/context?format=json

Parameters

ParameterTypeRequiredDescription
datestringNoHistorical date in YYYY-MM-DD format. A paid call serves today or any ?date= on record.
formatstringNoResponse 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, 26 lines
{
  "briefing_metadata": {
    "correlations_count": 1,
    "description": "Bitcoin price, mining health, and liquidity overview with 7-day and 30-day trends",
    "metrics_count": 5,
    "name": "BTC Context"
  },
  "briefing_used": "btc.context",
  "metrics": {
    "bitcoin-difficulty": {
      "name": "bitcoin-difficulty"
    },
    "bitcoin-hash-rate": {
      "name": "bitcoin-hash-rate"
    },
    "bitcoin-price": {
      "name": "bitcoin-price"
    },
    "hash-ribbon": {
      "name": "hash-ribbon"
    },
    "net-liquidity": {
      "name": "net-liquidity"
    }
  }
}

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://api.prereason.com/api/btc/context?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/context?format=json' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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%2Fapi.prereason.com%2Fapi%2Fbtc%2Fcontext
const res = await pay("https://api.prereason.com/api/btc/context?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.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://api.prereason.com/api/btc/context?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

WhenResultHTTPTimePrice
5 h agoPassed402515 ms$0.02
9 h agoPassed402595 ms$0.02
14 h agoPassed402530 ms$0.02
18 h agoPassed402553 ms$0.02
22 h agoPassed402561 ms$0.02
Show 10 older checks
26 h agoPassed402832 ms$0.02
31 h agoPassed402836 ms$0.02
35 h agoPassed402600 ms$0.02
39 h agoPassed402689 ms$0.02
43 h agoPassed402535 ms$0.02
2 days agoPassed402571 ms$0.02
2 days agoPassed402545 ms$0.02
2 days agoPassed402495 ms$0.02
3 days agoPassed402606 ms$0.02
3 days agoPassed402353 ms$0.02