70trust / 100
Aggro Range Calculator
by Aggro range estimator in Markets & finance
x402 APIPassing, checked 3 h ago
Aggro range estimator: Estimate detection radius after visibility and alertness modifiers.
POST https://market.datapackvibe.com/x402/aggro-range-calculator
Last 30 days
All checks passedSome failedAll failedNot checked
Status and outage history · Atom feed
- Uptime
- 65.0%
- Response time
- 92 ms typical, 2.8 s slowest 5%
- Last check
- 3 h ago
- Next check
- any minute now
How to call it
POST https://market.datapackvibe.com/x402/aggro-range-calculator
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/aggro-range-calculator
content-type: application/json
{
"alertness": 1,
"base_range": 20,
"visibility": 1
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
alertness | number | No | Default: 1. |
base_range | number | No | Default: 20. |
visibility | number | No | Default: 1. |
Example response
The provider's example. We can't check it without paying.
{
"files": [],
"order_id": "ord_example",
"result": {
"detection_range": 20
},
"sku": "aggro-range-calculator",
"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/aggro-range-calculator' \
-H 'content-type: application/json' \
--data-raw '{"alertness":1,"base_range":20,"visibility":1}'
# 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/aggro-range-calculator' \
-H 'content-type: application/json' \
--data-raw '{"alertness":1,"base_range":20,"visibility":1}' \
| 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.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%2Faggro-range-calculator&method=POST
const res = await pay("https://market.datapackvibe.com/x402/aggro-range-calculator", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"alertness": 1,
"base_range": 20,
"visibility": 1
}),
});
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/aggro-range-calculator",
json={
"alertness": 1,
"base_range": 20,
"visibility": 1,
},
)
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 |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 92 ms | $0.01 |
| 7 h ago | Passed | 402 | 60 ms | $0.01 |
| 11 h ago | Expected HTTP 402, got 530 | 530 | 36 ms | - |
| 15 h ago | Expected HTTP 402, got 530 | 530 | 34 ms | - |
| 18 h ago | Passed | 402 | 63 ms | $0.01 |
| 22 h ago | Passed | 402 | 62 ms | $0.01 |
| 26 h ago | Passed | 402 | 315 ms | $0.01 |
| 30 h ago | Passed | 402 | 1.3 s | $0.01 |
| 34 h ago | Expected HTTP 402, got 530 | 530 | 39 ms | - |
| 37 h ago | Expected HTTP 402, got 530 | 530 | 32 ms | - |
| 40 h ago | Expected HTTP 402, got 530 | 530 | 33 ms | - |
| 44 h ago | Passed | 402 | 60 ms | $0.01 |
| 47 h ago | Passed | 402 | 70 ms | $0.01 |
| 2 days ago | Passed | 402 | 5.1 s | $0.01 |
| 2 days ago | Passed | 402 | 871 ms | $0.01 |