Ref Check
by CitePulse in Security & trust
Bibliography verification for AI research agents — POST up to 20 citations (DOIs or free-text references) and get a per-reference verdict: exists/not-found, retracted/withdrawn (Crossref + Retraction Watch + OpenAlex), and title/author/year mismatches against a real record. Built for agents auditing LLM-generated bibliographies before a citation ships.
https://citepulse.theaslangroupllc.com/api/ref-check- Price
- $0.02
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 8 h ago, next any minute now
Reliability
Latest check failed 8 h ago: Amount "0.02" 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/ref-check
Each call costs $0.02 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/ref-checkParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
citations | string | No | Comma-separated DOIs/free-text refs (GET), or JSON array in the body (POST) — up to 20 items. Each item can be a plain string (DOI or a full reference string) or an object {doi, title, authors, year} for stricter mismatch checking. |
Example response
The provider's example. We can't check it without paying.
{
"checked": 3,
"not_found": 1,
"results": [
{
"confidence": 0.98,
"input": "10.1016/S0140-6736(97)11096-0",
"is_retracted": true,
"retraction": [
{
"date": "2010-02-06",
"notice_doi": "10.1016/s0140-6736(10)60175-4",
"source": "retraction-watch",
"type": "retraction"
}
],
"verdict": "retracted"
}
],
"retracted": 1,
"verified": 1
}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.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://citepulse.theaslangroupllc.com/api/ref-check'
# 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/ref-check' \
| 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fcitepulse.theaslangroupllc.com%2Fapi%2Fref-check
const res = await pay("https://citepulse.theaslangroupllc.com/api/ref-check");
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
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/ref-check")
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 |
|---|---|---|---|---|
| 8 h ago | Amount "0.02" is not in atomic token units | 402 | 276 ms | $0.02 |
| 16 h ago | Amount "0.02" is not in atomic token units | 402 | 273 ms | $0.02 |
| 24 h ago | Amount "0.02" is not in atomic token units | 402 | 248 ms | $0.02 |
| 32 h ago | Amount "0.02" is not in atomic token units | 402 | 195 ms | $0.02 |
| 41 h ago | Amount "0.02" is not in atomic token units | 402 | 297 ms | $0.02 |
Show 10 older checks
| 2 days ago | Amount "0.02" is not in atomic token units | 402 | 260 ms | $0.02 |
| 2 days ago | Amount "0.02" is not in atomic token units | 402 | 239 ms | $0.02 |
| 3 days ago | Amount "0.02" is not in atomic token units | 402 | 203 ms | $0.02 |
| 3 days ago | Amount "0.02" is not in atomic token units | 402 | 345 ms | $0.02 |
| 3 days ago | Amount "0.02" is not in atomic token units | 402 | 238 ms | $0.02 |
| 4 days ago | Amount "0.02" is not in atomic token units | 402 | 278 ms | $0.02 |
| 4 days ago | Amount "0.02" is not in atomic token units | 402 | 304 ms | $0.02 |
| 4 days ago | Amount "0.02" is not in atomic token units | 402 | 219 ms | $0.02 |
| 4 days ago | Amount "0.02" is not in atomic token units | 402 | 230 ms | $0.02 |
| 5 days ago | Amount "0.02" is not in atomic token units | 402 | 237 ms | $0.02 |