ToolVet
78trust / 100

Sei

by Pocket Network in Onchain & crypto

x402 APIPassing, checked 1 h ago

Read-only access to Sei mainnet (pacific-1) on every surface a Sei node exposes: the EVM JSON-RPC methods, the CometBFT RPC (as JSON-RPC or GET routes such as /status and /block) and the Cosmos SDK LCD (GET /cosmos/... and /sei-protocol/...). Served by the Pocket Network decentralised supplier set. Pay per request in USDC; no account, no API key.

POST
https://test.agent.pocket.network/v1/sei
Price
$0.005
per call in USDC
Uptime
100%
last 30 days
Response time
242 ms
417 ms slowest 5%
Last check
Passed
1 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

POST https://test.agent.pocket.network/v1/sei

Each call costs $0.005 in USDC on Base Sepolia, 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://test.agent.pocket.network/v1/sei
content-type: application/json

{
  "method": "GET /abci_info"
}

Parameters

ParameterTypeRequiredDescription
methodstringNoCometBFT RPC method, e.g. block
paramsanyNoParameters per the CometBFT RPC spec

Example response

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

{
  "data": {
    "id": 1,
    "jsonrpc": "2.0",
    "result": {}
  },
  "portal": {
    "provenance": "third-party-supplier",
    "schemaCheck": "passed",
    "serviceId": "sei"
  }
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://test.agent.pocket.network/v1/sei' \
  -H 'content-type: application/json' \
  --data-raw '{"method":"GET /abci_info"}'

# 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://test.agent.pocket.network/v1/sei' \
  -H 'content-type: application/json' \
  --data-raw '{"method":"GET /abci_info"}' \
  | 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.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
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.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Ftest.agent.pocket.network%2Fv1%2Fsei&method=POST
const res = await pay("https://test.agent.pocket.network/v1/sei", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "method": "GET /abci_info"
  }),
});
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.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://test.agent.pocket.network/v1/sei",
        json={
            "method": "GET /abci_info",
        },
    )
    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
1 h agoPassed402202 ms$0.005
6 h agoPassed402245 ms$0.005
11 h agoPassed402231 ms$0.005
15 h agoPassed402245 ms$0.005
19 h agoPassed402171 ms$0.005
Show 10 older checks
24 h agoPassed402274 ms$0.005
28 h agoPassed402216 ms$0.005
32 h agoPassed402177 ms$0.005
36 h agoPassed402206 ms$0.005
41 h agoPassed402237 ms$0.005
45 h agoPassed402267 ms$0.005
2 days agoPassed402189 ms$0.005
2 days agoPassed402221 ms$0.005
2 days agoPassed402314 ms$0.005
3 days agoPassed402203 ms$0.005