13trust / 100

Narrative

by Saylor Innovations Watchdog API in Onchain & crypto

x402 APIFailing, checked 4 h ago

Solana token narrative classification (AI, dog, cat, political, gaming, DeFi) plus socials

GET https://saylorinnovations.com/api/narrative/:mint

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
0.0%
Response time
- typical, - slowest 5%
Last check
4 h ago: Expected HTTP 402, got 400
Next check
any minute now

How to call it

GET https://saylorinnovations.com/api/narrative/:mint

Each call costs $0.005 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/narrative/:mint

Example response

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

{
  "fetched_at": 1787934806.16,
  "mint": "DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263",
  "name": "Bonk",
  "narratives": [
    "dog"
  ],
  "socials": {
    "telegram": "https://t.me/Official_Bonk_Inu",
    "twitter": "https://twitter.com/bonk_inu",
    "website": "https://www.bonkcoin.com"
  },
  "symbol": "Bonk"
}

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 'https://saylorinnovations.com/api/narrative/:mint'

# 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/narrative/:mint' \
  | 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%2Fsaylorinnovations.com%2Fapi%2Fnarrative%2F%3Amint
const res = await pay("https://saylorinnovations.com/api/narrative/:mint");
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.get("https://saylorinnovations.com/api/narrative/:mint")
    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
4 h agoExpected HTTP 402, got 400400347 ms-
9 h agoExpected HTTP 402, got 400400374 ms-
13 h agoExpected HTTP 402, got 400400298 ms-
17 h agoExpected HTTP 402, got 400400313 ms-
22 h agoExpected HTTP 402, got 400400638 ms-
26 h agoExpected HTTP 402, got 400400738 ms-
31 h agoExpected HTTP 402, got 400400337 ms-
34 h agoExpected HTTP 402, got 400400198 ms-
39 h agoExpected HTTP 402, got 400400670 ms-
43 h agoExpected HTTP 402, got 400400329 ms-
47 h agoExpected HTTP 402, got 400400768 ms-
2 days agoExpected HTTP 402, got 400400207 ms-
2 days agoExpected HTTP 402, got 400400674 ms-
2 days agoExpected HTTP 402, got 4004001.8 s-
3 days agoExpected HTTP 402, got 400400418 ms-