13trust / 100

Evm Polygon

by saylorinnovations.com in Onchain & crypto

x402 APIFailing, checked 5 h ago

EVM Network Status (polygon) — On-Chain Data

GET
https://saylorinnovations.com/api/evm/polygon/:chain
Price
$0.001
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

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 5 h ago: Expected HTTP 402, got 404

Status and outage history · Atom feed

How to call it

GET https://saylorinnovations.com/api/evm/polygon/:chain

Each call costs $0.001 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

The listing has no example input.

GET https://saylorinnovations.com/api/evm/polygon/:chain

Example response

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

{
  "base_fee_gwei": 0.0041,
  "block": 51738756,
  "block_age_seconds": 1,
  "chain": "base",
  "chain_id": 8453,
  "gas_price_gwei": 0.0052
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://saylorinnovations.com/api/evm/polygon/:chain'

# 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://saylorinnovations.com/api/evm/polygon/:chain' \
  | 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.001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.001" });
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.001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsaylorinnovations.com%2Fapi%2Fevm%2Fpolygon%2F%3Achain
const res = await pay("https://saylorinnovations.com/api/evm/polygon/:chain");
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.001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://saylorinnovations.com/api/evm/polygon/:chain")
    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 agoExpected HTTP 402, got 404404393 ms-
10 h agoExpected HTTP 402, got 404404197 ms-
14 h agoExpected HTTP 402, got 404404230 ms-
19 h agoExpected HTTP 402, got 404404460 ms-
24 h agoExpected HTTP 402, got 404404739 ms-
Show 10 older checks
28 h agoExpected HTTP 402, got 404404676 ms-
32 h agoExpected HTTP 402, got 404404584 ms-
37 h agoExpected HTTP 402, got 404404498 ms-
41 h agoExpected HTTP 402, got 404404374 ms-
46 h agoExpected HTTP 402, got 404404380 ms-
2 days agoExpected HTTP 402, got 404404219 ms-
2 days agoExpected HTTP 402, got 404404302 ms-
2 days agoExpected HTTP 402, got 404404195 ms-
3 days agoExpected HTTP 402, got 404404410 ms-
3 days agoExpected HTTP 402, got 404404323 ms-