Bloque Por Fecha Pago
by Vextorium in Onchain & crypto
Block number closest to a date and time on EVM chains (ethereum, base, arbitrum, optimism, polygon, bsc, avax...), with the block's own timestamp. For historical state queries and event filters.
https://api.vextorium.com/bloque-por-fecha-pago- Price
- $0.003
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 5 h ago, next any minute now
Reliability
Latest check failed 5 h ago: Amount "0.003" is not in atomic token units
How to call it
POST https://api.vextorium.com/bloque-por-fecha-pago
Each call costs $0.003 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://api.vextorium.com/bloque-por-fecha-pago
content-type: application/json
{
"cadena": "base",
"fecha": "2025-01-01"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
cadena | string | Yes | Chain, e.g. ethereum, base, arbitrum |
fecha | string | Yes | YYYY-MM-DD, ISO 8601 or Unix timestamp |
Example response
The provider's example. We can't check it without paying.
{
"bloque": 24450127,
"cadena": "base",
"diferencia_segundos": 1,
"fecha_pedida": "2025-01-01T00:00:00+00:00",
"fuente": "DefiLlama",
"momento_bloque": "2025-01-01T00:00:01+00:00"
}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.003.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.vextorium.com/bloque-por-fecha-pago' \
-H 'content-type: application/json' \
--data-raw '{"cadena":"base","fecha":"2025-01-01"}'
# 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://api.vextorium.com/bloque-por-fecha-pago' \
-H 'content-type: application/json' \
--data-raw '{"cadena":"base","fecha":"2025-01-01"}' \
| 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.003 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.003" });
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.003 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.vextorium.com%2Fbloque-por-fecha-pago&method=POST
const res = await pay("https://api.vextorium.com/bloque-por-fecha-pago", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"cadena": "base",
"fecha": "2025-01-01"
}),
});
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.003 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.003"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://api.vextorium.com/bloque-por-fecha-pago",
json={
"cadena": "base",
"fecha": "2025-01-01",
},
)
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 |
|---|---|---|---|---|
| 5 h ago | Amount "0.003" is not in atomic token units | 402 | 299 ms | $0.003 |
| 9 h ago | Amount "0.003" is not in atomic token units | 402 | 229 ms | $0.003 |
| 14 h ago | Amount "0.003" is not in atomic token units | 402 | 82 ms | $0.003 |
| 19 h ago | Amount "0.003" is not in atomic token units | 402 | 85 ms | $0.003 |
| 24 h ago | Amount "0.003" is not in atomic token units | 402 | 97 ms | $0.003 |
Show 10 older checks
| 29 h ago | Amount "0.003" is not in atomic token units | 402 | 267 ms | $0.003 |
| 33 h ago | Amount "0.003" is not in atomic token units | 402 | 137 ms | $0.003 |
| 38 h ago | Amount "0.003" is not in atomic token units | 402 | 76 ms | $0.003 |
| 42 h ago | Amount "0.003" is not in atomic token units | 402 | 85 ms | $0.003 |
| 46 h ago | Amount "0.003" is not in atomic token units | 402 | 93 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 104 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 90 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 3.1 s | $0.003 |
| 3 days ago | Amount "0.003" is not in atomic token units | 402 | 73 ms | $0.003 |
| 3 days ago | Amount "0.003" is not in atomic token units | 402 | 79 ms | $0.003 |