66trust / 100

Assistant Bx Mining Block Probability Stress Grid

by market.datapackvibe.com in Markets & finance

x402 APIPassing, checked 49 min ago

At-least-one solo block probability — Two-input scenario grid: Two-input scenario grid for At-least-one solo block probability. Supplied mining assumptions only; formula and units disclosed. No live prices, mining or guaranteed return. Specialised preset in a shared 50-profile, 20-operation engine. 0.01 USDC includes one bounded two-input scenario grid report.

POST
https://market.datapackvibe.com/x402/assistant-bx-mining-block-probability-stress-grid
Price
$0.01
per call in USDC
Uptime
70.6%
last 30 days
Response time
87 ms
1.8 s slowest 5%
Last check
Passed
49 min ago, next in 5 h

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

POST https://market.datapackvibe.com/x402/assistant-bx-mining-block-probability-stress-grid

Each call costs $0.01 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://market.datapackvibe.com/x402/assistant-bx-mining-block-probability-stress-grid
content-type: application/json

{
  "baseline": {
    "days": 100,
    "expected_blocks_per_day": 0.01
  },
  "field_x": "expected_blocks_per_day",
  "field_y": "days",
  "values_x": [
    0.01,
    0.011000000000000001
  ],
  "values_y": [
    100,
    110.00000000000001
  ]
}

Parameters

ParameterTypeRequiredDescription
baselineobjectYes Default: {"days":100,"expected_blocks_per_day":0.01}.
field_xstringYes One of: expected_blocks_per_day, days. Default: "expected_blocks_per_day".
field_ystringYes One of: expected_blocks_per_day, days. Default: "days".
values_xarray of numberYes Default: [0.01,0.011000000000000001].
values_yarray of numberYes Default: [100,110.00000000000001].

Example response

The provider's example. We can't check it without paying.

{
  "files": [],
  "order_id": "ord_example",
  "result": {
    "completed": true,
    "workflow": "bx-mining-block-probability-stress-grid"
  },
  "sku": "assistant-bx-mining-block-probability-stress-grid",
  "status": "delivered"
}

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.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://market.datapackvibe.com/x402/assistant-bx-mining-block-probability-stress-grid' \
  -H 'content-type: application/json' \
  --data-raw '{"baseline":{"days":100,"expected_blocks_per_day":0.01},"field_x":"expected_blocks_per_day","field_y":"days","values_x":[0.01,0.011000000000000001],"values_y":[100,110.00000000000001]}'

# 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://market.datapackvibe.com/x402/assistant-bx-mining-block-probability-stress-grid' \
  -H 'content-type: application/json' \
  --data-raw '{"baseline":{"days":100,"expected_blocks_per_day":0.01},"field_x":"expected_blocks_per_day","field_y":"days","values_x":[0.01,0.011000000000000001],"values_y":[100,110.00000000000001]}' \
  | 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fmarket.datapackvibe.com%2Fx402%2Fassistant-bx-mining-block-probability-stress-grid&method=POST
const res = await pay("https://market.datapackvibe.com/x402/assistant-bx-mining-block-probability-stress-grid", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "baseline": {
      "days": 100,
      "expected_blocks_per_day": 0.01
    },
    "field_x": "expected_blocks_per_day",
    "field_y": "days",
    "values_x": [
      0.01,
      0.011000000000000001
    ],
    "values_y": [
      100,
      110.00000000000001
    ]
  }),
});
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://market.datapackvibe.com/x402/assistant-bx-mining-block-probability-stress-grid",
        json={
            "baseline": {
                "days": 100,
                "expected_blocks_per_day": 0.01,
            },
            "field_x": "expected_blocks_per_day",
            "field_y": "days",
            "values_x": [
                0.01,
                0.011000000000000001,
            ],
            "values_y": [
                100,
                110.00000000000001,
            ],
        },
    )
    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
49 min agoPassed40285 ms$0.01
10 h agoPassed40276 ms$0.01
19 h agoExpected HTTP 402, got 53053062 ms-
30 h agoExpected HTTP 402, got 53053047 ms-
41 h agoPassed40293 ms$0.01
Show 10 older checks
2 days agoPassed40275 ms$0.01
3 days agoPassed402772 ms$0.01
3 days agoPassed40283 ms$0.01
3 days agoPassed4022.0 s$0.01
4 days agoPassed40263 ms$0.01
4 days agoPassed40269 ms$0.01
4 days agoPassed40299 ms$0.01
4 days agoPassed40268 ms$0.01
5 days agoPassed4021.1 s$0.01
5 days agoPassed402126 ms$0.01