SEC v. Ripple - Case History

What the provider says

Quoted from x402 Bazaar · source record · read 2026-10-26

---

Facts and where they come from

Price

0.02 USDC per call Provider claim

Recorded value: 0.02 USDC per call.

Unit

per call

Protocol

x402, REST · transport: HTTP Provider claim

Auth

x402

Endpoint

https://www.blockchainiq.co/api/x402/v1/dispatch/sec-v-ripple

Source

x402 Bazaar (Coinbase CDP) · Public discovery API (provider-published records)

Last checked

Not checked by us yet — the data is as the source published it

First seen

2026-10-24

Usage

1 calls · 1 unique payers in the 30 days before 2026-10-24. Measured by the x402 Bazaar, not by us and not by the provider.

Payments and earnings

No settled payment on record. Earnings for this service are unknown — not zero. The source counts 1 calls in 30 days, which at the published price is roughly $0.02 of activity. Activity is not revenue; no charge has been reconciled for it.

Payment rails

A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it. See evidence levels.

Input and output, as published

Request

{
    "method": "GET",
    "queryParams": [],
    "type": "http"
}

Response

{
    "example": {
        "data": {
            "articles": [],
            "blocks": [
                {
                    "heading": "What the court decided",
                    "paragraphs": [
                        "..."
                    ],
                    "type": "prose"
                }
            ],
            "figuresAsOf": null,
            "footnotes": [
                "General-circulation research and market commentary. Not investment advice."
            ],
            "glossaryTerms": [
                {
                    "term": "Security",
                    "url": "https://www.blockchainiq.co/glossary/security"
                }
            ],
            "kicker": "Dispatch \u00b7 Regulation",
            "lede": "For four and a half years, one lawsuit held the U.S. crypto industry's regulatory status hostage.",
            "ledeUpdatedAt": null,
            "markdown": "# SEC v. Ripple\n\nFor four and a half years, one lawsuit held the U.S. crypto industry's regulatory status hostage.\n\n### What the court decided\n\n...",
            "publishedAt": "2026-09-25",
            "related": [
                {
                    "label": "All Dispatches",
                    "url": "https://www.blockchainiq.co/dispatch"
                }
            ],
            "slug": "sec-v-ripple",
            "title": "SEC v. Ripple",
            "url": "https://www.blockchainiq.co/dispatch/sec-v-ripple"
        },
        "disclaimer": "Market data and analysis, not investment advice.",
        "source": "Blockchain IQ",
        "terms": "https://www.blockchainiq.co/terms"
    },
    "type": "json"
}

Examples are the provider's own, not a call we made.

Provenance

One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.

Endpoint checks

We have not called this endpoint yet. Until we do, everything above is what the source published — no more.

Tags

---