Crypto ETF Sentinel — Full SEC ↔ issuer comment-letter history for one US spot crypto ETF
Crypto ETF Sentinel — Full SEC ↔ issuer comment-letter history for one US spot crypto ETF issuer: UPLOAD/CORRESP pairs in order with a review-intensity profile. Comment-letter cadence is a leading indicator of approval proximity. Use when assessing how far along one filing's SEC review is. Pass the issuer's SEC CIK as cik.
50000 (raw units)
price
3
calls / 30d
2
unique payers
2026-09-11
updated
Provider
api.cryptoetfsentinel.com · discovered, not yet claimed by its owner
Payment (x402 accepts[])
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x169Bf49c6ee5A179190121Ab8D180B50e31683d1",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "50000",
"maxTimeoutSeconds": 300
},
{
"scheme": "exact",
"network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
"payTo": "Ezzbt3d3K76pmQpwbeXkggCs5n7Q3JWG3iCmtdKdpMxk",
"asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
"amount": "50000",
"maxTimeoutSeconds": 300
}
]Output schema
{
"bazaar": {
"info": {
"input": {
"method": "GET",
"queryParams": {
"cik": "0001980994"
},
"type": "http"
},
"output": {
"example": {
"data": {
"letters": [
{
"accession": "0001193125-24-004598",
"edgar_url": "https://www.sec.gov/Archives/edgar/data/1980994/000119312524004598/",
"filing_date": "2024-01-09",
"form_type": "CORRESP"
}
],
"review_profile": {
"last_letter": "2024-01-09",
"review_rounds": 5,
"review_status": "approved",
"stage": "trading"
}
},
"meta": {
"total": null
}
},
"type": "json"
}
},
"schema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"method": {
"enum": [
"GET",
"HEAD",
"DELETE"
],
"type": "string"
},
"queryParams": {
"properties": {
"cik": {
"description": "Zero-padded SEC CIK identifier (e.g. ``0001980994``). Optional — pass one to target a specific issuer (discover CIKs via /v1/issuers); omit to get the largest issuer by AUM.",
"pattern": "^[0-9]{1,10}$",
"type": "string"
}
},
"required": [],
"type": "object"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method"
],
"type": "object"
},
"output": {
"properties": {
"example": {
"properties": {
"data": {
"description": "The endpoint payload — type varies per route"
},
"error": {
"type": [
"string",
"null"
]
},
"meta": {
"properties": {
"limit": {
"type": [
"integer",
"null"
]
},
"offset": {
"type": [
"integer",
"null"
]
},
"total": {
"type": [
"integer",
"null"
]
}
},
"type": "object"
}
},
"required": [
"data"
],
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}
}
}Use it
curl
curl "https://api.cryptoetfsentinel.com/v1/issuers/comment-letters" # -> 402 Payment Required, accepts[] lists how to pay # retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid
JavaScript
const res = await fetch("https://api.cryptoetfsentinel.com/v1/issuers/comment-letters");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}Python
import httpx
res = httpx.get("https://api.cryptoetfsentinel.com/v1/issuers/comment-letters")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerMachine-readable
Everything on this page is also available as clean JSON at /resources/5913.json, and this resource appears in /discovery/resources and /discovery/search.