ToolVet
13trust / 100

Topic Scan

by CitePulse in Other

x402 APIFailing, checked 11 min ago

Rising-topics scan for a research field — retrieves top-cited/recent works from OpenAlex for a topic and synthesizes what's currently rising, what's foundational, and where coverage is thin. Built for research-strategy agents scanning a field before a literature review or grant proposal.

GET
https://citepulse.theaslangroupllc.com/api/topic-scan
Price
$0.2
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
11 min ago, next in 47 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 11 min ago: Amount "0.2" is not in atomic token units

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://citepulse.theaslangroupllc.com/api/topic-scan

Each call costs $0.2 in USDC on Polygon, 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.

GET https://citepulse.theaslangroupllc.com/api/topic-scan?years=3

Parameters

ParameterTypeRequiredDescription
langstringNoe.g. en, es, fr, de, ja, zh, ko, pt, ar (default: en)
topicstringNoTopic/field name or keyword, e.g. "quantum error correction"
yearsstringNoLookback window in years for the 'rising' works window (default 3)

Example response

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

{
  "rising_signals": [
    {
      "doi": "10.xxxx/yyyy",
      "observation": "Surface-code decoding papers accelerating",
      "supporting_work": "string"
    }
  ],
  "state_of_field": "Error-correction and near-term algorithm design dominate current output...",
  "topic": "Quantum Computing Algorithms and Architecture"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://citepulse.theaslangroupllc.com/api/topic-scan?years=3'

# 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://citepulse.theaslangroupllc.com/api/topic-scan?years=3' \
  | 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.2 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.2" });
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.2 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fcitepulse.theaslangroupllc.com%2Fapi%2Ftopic-scan
const res = await pay("https://citepulse.theaslangroupllc.com/api/topic-scan?years=3");
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.2 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.2"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://citepulse.theaslangroupllc.com/api/topic-scan?years=3")
    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
11 min agoAmount "0.2" is not in atomic token units402197 ms$0.2
8 h agoAmount "0.2" is not in atomic token units402271 ms$0.2
17 h agoAmount "0.2" is not in atomic token units402273 ms$0.2
25 h agoAmount "0.2" is not in atomic token units402216 ms$0.2
33 h agoAmount "0.2" is not in atomic token units402205 ms$0.2
Show 10 older checks
41 h agoAmount "0.2" is not in atomic token units402562 ms$0.2
2 days agoAmount "0.2" is not in atomic token units402238 ms$0.2
2 days agoAmount "0.2" is not in atomic token units402214 ms$0.2
3 days agoAmount "0.2" is not in atomic token units402269 ms$0.2
3 days agoAmount "0.2" is not in atomic token units402240 ms$0.2
3 days agoAmount "0.2" is not in atomic token units402222 ms$0.2
4 days agoAmount "0.2" is not in atomic token units4021.1 s$0.2
4 days agoAmount "0.2" is not in atomic token units402189 ms$0.2
4 days agoAmount "0.2" is not in atomic token units402223 ms$0.2
4 days agoAmount "0.2" is not in atomic token units402246 ms$0.2