Document
by ISHOB in Documents & files
Normalized scholarly metadata + abstract + full rights/attribution for one open-licensed document
https://ai-data-archive.health-womens01.workers.dev/api/document/:id- Price
- $0.001
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 18 min ago, next in 45 min
Reliability
Latest check failed 18 min ago: Expected HTTP 402, got 404
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://ai-data-archive.health-womens01.workers.dev/api/document/:id
Each call costs $0.001 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.
GET https://ai-data-archive.health-womens01.workers.dev/api/document/:idExample response
The provider's example. We can't check it without paying.
{
"abstract": "...",
"canonical_id": "pmc-13364419",
"license": "CC-BY-4.0",
"title": "..."
}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://ai-data-archive.health-womens01.workers.dev/api/document/:id'
# 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://ai-data-archive.health-womens01.workers.dev/api/document/:id' \
| 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.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%2Fai-data-archive.health-womens01.workers.dev%2Fapi%2Fdocument%2F%3Aid
const res = await pay("https://ai-data-archive.health-womens01.workers.dev/api/document/:id");
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://ai-data-archive.health-womens01.workers.dev/api/document/:id")
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 |
|---|---|---|---|---|
| 18 min ago | Expected HTTP 402, got 404 | 404 | 332 ms | - |
| 6 h ago | Expected HTTP 402, got 404 | 404 | 349 ms | - |
| 11 h ago | Expected HTTP 402, got 404 | 404 | 278 ms | - |
| 16 h ago | Expected HTTP 402, got 404 | 404 | 390 ms | - |
| 20 h ago | Expected HTTP 402, got 404 | 404 | 715 ms | - |
Show 10 older checks
| 25 h ago | Expected HTTP 402, got 404 | 404 | 386 ms | - |
| 30 h ago | Expected HTTP 402, got 404 | 404 | 431 ms | - |
| 34 h ago | Expected HTTP 402, got 404 | 404 | 478 ms | - |
| 39 h ago | Expected HTTP 402, got 404 | 404 | 290 ms | - |
| 44 h ago | Expected HTTP 402, got 404 | 404 | 370 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 390 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 393 ms | - |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 420 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 226 ms | - |
| 3 days ago | Expected HTTP 402, got 404 | 404 | 305 ms | - |