Back to Browse
ClinicalTrials.gov NCT Study Resolver
x402
ClinicalTrials.gov NCT Study Resolver is a paid API for AI agents from foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).
Resolves a single NCT identifier into its current registry status, study phase, dates, and provenance from ClinicalTrials.gov.
Price / call$0.005
Success—
StatusUnknown
How this service works
Pay-per-request evidence and data tools: CSV validation and reconciliation, DNS/email configuration evidence, and bounded official weather, earthquake, vehicle, company and study records. Exact USDC prices, explicit JSON contracts and source provenance. No mailbox, ownership, medical or safety guarantees.
Output
Returns a normalized JSON object containing the NCT study's current registry status, study phase, start and completion dates, source freshness metadata (retrieval timestamp, cache age), attribution and provenance details (license, terms URL, upstream calls), and the raw source identifiers from ClinicalTrials.gov.
Example use cases
Verify clinical trial recruitment status
“Is clinical trial NCT04280705 still recruiting patients? Can you check its current status and give me the study start and completion dates?”
Confirm trial phase for research report
“I'm writing a report on a cancer drug — can you pull up the current phase and registry status for NCT02142803 from ClinicalTrials.gov?”
Due diligence on biotech pipeline asset
“We're evaluating a biotech company and need to verify the current regulatory status and timeline for their trial NCT03425656 — can you fetch the official ClinicalTrials.gov record?”
Technical details
Endpoint
POSThttps://foundry-par007-machine-revenue-mainnet.inference-chip-index.workers.dev/v2/official/clinicaltrials-studyWhen to prefer
Use this endpoint when you need authoritative, up-to-date registry metadata for a single known NCT identifier with explicit provenance and freshness tracking. Prefer it over general web search when you need structured, machine-readable trial data with clear attribution and cache transparency. If you need to search trials by condition rather than a specific NCT ID, use a sibling search endpoint instead.
Side effects
- Invalid NCT ID format (must match ^NCT\d{8}$) returns a validation error
- NCT ID not found in ClinicalTrials.gov returns an empty normalizedResult array
- Network or upstream ClinicalTrials.gov API unavailability may cause timeout or error
- Payment not provided or insufficient USDC results in HTTP 402 rejection
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| nct_id | string |
Output
Schema · Response
{
"type": "json",
"example": {
"route": "clinicaltrials-study",
"result": {
"query": {
"nct_id": "NCT00110383"
},
"source": "ClinicalTrials.gov",
"freshness": {
"state": "CURRENT_RETRIEVAL",
"retrievedAt": "2026-09-06T00:00:00Z",
"cacheAgeSeconds": 0,
"maximumCacheSeconds": 0,
"recordAgeIsNotRetrievalAge": true
},
"sourceUrl": "https://clinicaltrials.gov",
"observedAt": "2026-09-06T00:00:00Z",
"provenance": {
"license": "ClinicalTrials.gov terms; bounded factual study metadata only",
"termsUrl": "https://clinicaltrials.gov/about-site/terms-conditions",
"truncated": false,
"attribution": "ClinicalTrials.gov, US National Library of Medicine",
"limitations": [
"Synthetic example only; identifiers and null values illustrate fields, not a live observation."
],
"modifications": "Selected factual fields, normalized names and bounded result count; no source ownership claimed.",
"upstreamCalls": 1,
"documentationUrl": "https://clinicaltrials.gov/data-api/api"
},
"sourceUpdatedAt": null,
"normalizedResult": [
{
"nctId": "NCT00110383",
"title": null,
"phases": [],
"sourceUrl": "https://clinicaltrials.gov/study/NCT00110383",
"startDate": null,
"studyType": null,
"overallStatus": null,
"completionDate": null,
"lastUpdatePostDate": null
}
],
"sourceProcessedAt": null,
"rawSourceIdentifiers": []
},
"observed_at": "2026-09-06T00:00:00Z"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"