Grossman 2007 Boston Syncope from eight caller-assigned flags: ACS signs/symptoms, cond…
Grossman 2007 Boston Syncope from eight caller-assigned flags: ACS signs/symptoms, conduction disease, worrisome cardiac history, valvular heart disease, family history of sudden death, persistent abnormal ED vitals, volume depletion, and primary CNS event. h…
by api.magentlab.com · discovered, not yet claimed by its owner · updated 2026-10-13
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Grossman 2007 Boston Syncope from eight caller-assigned flags: ACS signs/symptoms, conduction disease, worrisome cardiac history, valvular heart disease, family history of sudden death, persistent abnormal ED vitals, volume depletion, and primary CNS event. high_risk (Boston-positive) iff any is true; low_risk iff none. Adult (enrolled 18+). Not a disposition or admission order. magent does not examine the patient or interpret ECG/hematocrit. Not San Francisco Syncope, EGSYS, ROSE, or OESIL.
Tags: boston-syncope · syncope · emergency · grossman · calculator · bazaar
Call contract
- Method
- POST
- Input
- HTTP request
- Output
- json
- Last paid call
- 2026-10-13
{
"items": [
{
"acs_signs_symptoms": false,
"conduction_disease": false,
"family_history_sudden_death": false,
"persistent_abnormal_vitals": false,
"primary_cns_event": false,
"valvular_heart_disease": false,
"volume_depletion": false,
"worrisome_cardiac_history": false
},
{
"acs_signs_symptoms": false,
"conduction_disease": false,
"family_history_sudden_death": false,
"persistent_abnormal_vitals": false,
"primary_cns_event": false,
"valvular_heart_disease": false,
"volume_depletion": false,
"worrisome_cardiac_history": false
}
]
}{
"count": 2,
"items": [
{
"citation": {
"authors": "Grossman SA, Fischer C, Lipsitz LA, et al.",
"doi": "10.1016/j.jemermed.2007.04.001",
"id": "grossman-2007",
"pmid": "17976548",
"source": "J Emerg Med. 2007;33(3):233-239",
"title": "Predicting adverse outcomes in syncope"
},
"criteria": [
{
"factor": "acs_signs_symptoms",
"met": false
},
{
"factor": "conduction_disease",
"met": false
},
{
"factor": "worrisome_cardiac_history",
"met": false
},
{
"factor": "valvular_heart_disease",
"met": false
},
{
"factor": "family_history_sudden_death",
"met": false
},
{
"factor": "persistent_abnormal_vitals",
"met": false
},
{
"factor": "volume_depletion",
"met": false
},
{
"factor": "primary_cns_event",
"met": false
},
{
"factor": "high_risk_any",
"met": false
}
],
"disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.",
"formula": "boston_syncope",
"formula_expression": "high_risk iff acs_signs_symptoms or conduction_disease or worrisome_cardiac_history or valvular_heart_disease or family_history_sudden_death or persistent_abnormal_vitals or volume_depletion or primary_cns_event; low_risk iff not high_risk (Grossman 2007 Boston Syncope; Boston-positive iff any of eight caller-assigned flags)",
"high_risk": false,
"low_risk": true
},
{
"citation": {
"authors": "Grossman SA, Fischer C, Lipsitz LA, et al.",
"doi": "10.1016/j.jemermed.2007.04.001",
"id": "grossman-2007",
"pmid": "17976548",
"source": "J Emerg Med. 2007;33(3):233-239",
"title": "Predicting adverse outcomes in syncope"
},
"criteria": [
{
"factor": "acs_signs_symptoms",
"met": false
},
{
"factor": "conduction_disease",
"met": false
},
{
"factor": "worrisome_cardiac_history",
"met": false
},
{
"factor": "valvular_heart_disease",
"met": false
},
{
"factor": "family_history_sudden_death",
"met": false
},
{
"factor": "persistent_abnormal_vitals",
"met": false
},
{
"factor": "volume_depletion",
"met": false
},
{
"factor": "primary_cns_event",
"met": false
},
{
"factor": "high_risk_any",
"met": false
}
],
"disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.",
"formula": "boston_syncope",
"formula_expression": "high_risk iff acs_signs_symptoms or conduction_disease or worrisome_cardiac_history or valvular_heart_disease or family_history_sudden_death or persistent_abnormal_vitals or volume_depletion or primary_cns_event; low_risk iff not high_risk (Grossman 2007 Boston Syncope; Boston-positive iff any of eight caller-assigned flags)",
"high_risk": false,
"low_risk": true
}
],
"path": "/api/calc/boston_syncope"
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/39282.jsonfor the price and payment options. - Pay. Call
GET https://api.magentlab.com/api/calc/boston_syncope. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.005 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 5 calls · 2 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.005 | 0x836Be278f1739fB4308091cD1852F7971Bc19Ee2 | 600s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x836Be278f1739fB4308091cD1852F7971Bc19Ee2",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "5000",
"amountUsd": 0.005,
"maxTimeoutSeconds": 600
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl "https://api.magentlab.com/api/calc/boston_syncope"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://api.magentlab.com/api/calc/boston_syncope");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://api.magentlab.com/api/calc/boston_syncope")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- api.magentlab.com
- Endpoint
- https://api.magentlab.com/api/calc/boston_syncope
- Machine-readable
/resources/39282.json