Trials
by TrialBase DB in Search & web
Search normalized clinical trials by registry, condition, intervention, sponsor, country, status, phase, study type, or free text.
https://api.trialbase-db.org/v1/trials- Price
- $0.1
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 352 ms
- 1.0 s slowest 5%
- Last check
- Passed
- 5 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://api.trialbase-db.org/v1/trials
Each call costs $0.1 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
From the listing.
GET https://api.trialbase-db.org/v1/trials?condition=Intimate+partner+violence&limit=1®istry=isrctnParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
condition | string | No | |
count | boolean | No | Include the total matching-record count. |
country | string | No | |
cursor | string | No | Opaque keyset cursor from a previous response. |
intervention | string | No | |
limit | integer | No | Default: 20. |
phase | string | No | |
q | string | No | |
registry | string | No | |
sponsor | string | No | |
status | string | No | |
study_type | string | No |
Example response
The provider's example. We can't check it without paying.
{
"data": [
{
"brief_title": "Effectiveness of an intimate partner violence intervention to reduce detection gaps among diverse ethnic groups of women",
"countries": [
"Israel"
],
"enrollment_count": 3829,
"id": 679751,
"primary_registry": "isrctn",
"registry_id": "ISRCTN17465883",
"start_date": "2022-06-07",
"status": "unknown",
"study_type": "INTERVENTIONAL"
}
],
"has_more": false,
"next_cursor": null
}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.1.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.trialbase-db.org/v1/trials?condition=Intimate+partner+violence&limit=1®istry=isrctn'
# 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://api.trialbase-db.org/v1/trials?condition=Intimate+partner+violence&limit=1®istry=isrctn' \
| 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.1 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.1" });
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.1 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.trialbase-db.org%2Fv1%2Ftrials
const res = await pay("https://api.trialbase-db.org/v1/trials?condition=Intimate+partner+violence&limit=1®istry=isrctn");
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.1 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.1"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://api.trialbase-db.org/v1/trials?condition=Intimate+partner+violence&limit=1®istry=isrctn")
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 |
|---|---|---|---|---|
| 5 h ago | Passed | 402 | 550 ms | $0.1 |
| 10 h ago | Passed | 402 | 249 ms | $0.1 |
| 16 h ago | Passed | 402 | 235 ms | $0.1 |
| 21 h ago | Passed | 402 | 1.0 s | $0.1 |
| 26 h ago | Passed | 402 | 349 ms | $0.1 |
Show 10 older checks
| 31 h ago | Passed | 402 | 489 ms | $0.1 |
| 36 h ago | Passed | 402 | 522 ms | $0.1 |
| 40 h ago | Passed | 402 | 266 ms | $0.1 |
| 45 h ago | Passed | 402 | 313 ms | $0.1 |
| 2 days ago | Passed | 402 | 423 ms | $0.1 |
| 2 days ago | Passed | 402 | 265 ms | $0.1 |
| 2 days ago | Passed | 402 | 406 ms | $0.1 |
| 3 days ago | Passed | 402 | 352 ms | $0.1 |
| 3 days ago | Passed | 402 | 881 ms | $0.1 |
| 3 days ago | Passed | 402 | 757 ms | $0.1 |