Crypto ETF Sentinel — Chronological profile evolution for one US spot crypto ETF issuer…
Crypto ETF Sentinel — Chronological profile evolution for one US spot crypto ETF issuer: custodian, fee, AP-count and in-kind deltas across successive POS AM filings. Use when tracing how a fund's terms changed over time (fee cuts, custodian switches). Pass t…
by api.cryptoetfsentinel.com · discovered, not yet claimed by its owner · updated 2026-10-08
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
Crypto ETF Sentinel — Chronological profile evolution for one US spot crypto ETF issuer: custodian, fee, AP-count and in-kind deltas across successive POS AM filings. Use when tracing how a fund's terms changed over time (fee cuts, custodian switches). Pass the issuer's SEC CIK as cik; optional limit.
Tags: bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-08
{
"cik": "0001980994",
"limit": 20
}{
"data": [
{
"accession": "0001193125-26-012345",
"ap_count_cash": 5,
"ap_count_cash_delta": 1,
"ap_count_inkind": 3,
"ap_count_inkind_delta": 3,
"basket_size": 40000,
"basket_size_delta": 0,
"cik": "0001980994",
"custodian": "Coinbase Custody Trust Company, LLC",
"custodian_changed": false,
"fee_delta": null,
"filing_date": "2026-01-15",
"inkind_changed": true,
"inkind_eligible": true,
"sponsor_fee": "0.25%"
}
],
"meta": {
"total": 1
}
}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/32524.jsonfor the price and payment options. - Pay. Call
GET https://api.cryptoetfsentinel.com/v1/profiles/history. 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, Solana, 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.05 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base, Solana
- Demand
- 2 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.05 | 0x169Bf49c6ee5A179190121Ab8D180B50e31683d1 | 300s |
| exact | Solana solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp | USDC | $0.05 | Ezzbt3d3K76pmQpwbeXkggCs5n7Q3JWG3iCmtdKdpMxk | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x169Bf49c6ee5A179190121Ab8D180B50e31683d1",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "50000",
"amountUsd": 0.05,
"maxTimeoutSeconds": 300
},
{
"scheme": "exact",
"network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
"payTo": "Ezzbt3d3K76pmQpwbeXkggCs5n7Q3JWG3iCmtdKdpMxk",
"asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
"amount": "50000",
"amountUsd": 0.05,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"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"
}Example shape — generated from the schema, not a captured live response
{
"example": {
"data": null,
"error": "string",
"meta": {
"limit": 0,
"offset": 0,
"total": 0
}
},
"type": "string"
}Examples
curl "https://api.cryptoetfsentinel.com/v1/profiles/history"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://api.cryptoetfsentinel.com/v1/profiles/history");
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.cryptoetfsentinel.com/v1/profiles/history")
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.cryptoetfsentinel.com
- Endpoint
- https://api.cryptoetfsentinel.com/v1/profiles/history
- Machine-readable
/resources/32524.json