addrbookList your agent
← Directory

CryptoDataAPI on RealtimeAPI

api.realtimeapi.ai · x402

CryptoDataAPI: Get Quant Regimes. The 6-regime taxonomy reference (any valid key). Stable vocabulary for all quant endpoints: id, label, display name, description and the suggested algo-basket stance per regime. Raw HMM states map many-to-one onto these labels; the labels are the API contract. `catalog_version` is the versioned guarantee behind that: unchanged means every `id` still maps to the same `label` you can see here — safe to pin `regime.id` directly rather than re-resolving `label`...
Name and description as published by x402 Bazaar

Filed under Maps, places & transport by addrbook, from the words in its listing

Live

Last successful check: 13 Nov 2026, 15:30 UTC.

answered, last 24 hours
100%
answered, last 30 days
100%
How addrbook checks →

Evidence

1 of 4 shown

  1. Answers when askedShown

    Answered a check 3 hours ago.

  2. Owner provenNot shown

    No one has proven control of its domain or of the wallet it is paid at.

  3. Track recordNot shown

    Listed for 3 days; 30 are needed.

  4. Independent paying walletsNot shown

    1 different wallets paid it in 30 days, as the x402 Bazaar reports (not yet counted by addrbook); 10 are needed.

  5. Tool scanDoes not apply

    Not an MCP server.

Decided by method 2026.11.4, from its recorded evidence. A check that does not apply is left out of the count.

Connect

https://api.realtimeapi.ai/v1/cryptodata/quant/regimes

x402: an unpaid request gets a 402 with the price and pay-to wallet. The check never pays.

Who's behind it

Listed by
  • x402 Bazaarlast seen UTC
Wallets named
  • 0xdfd0074a3f1839f3af603f4083ae48f4d6497a45named by x402 Bazaar
Proven to belong to it
Nothing yet. Is it yours?
Listed since

Payments

different wallets paid it, last 30 days
1
paid calls, last 30 days
1
last paid call (UTC)

As the x402 Bazaar reports, from payments Coinbase's facilitator settled. Read . addrbook has not counted these payments itself.

How it asks to be paid

NetworkPricePaid inSettled byPays to
Base$0.01USDCPer request0xdfd0074a3f1839f3af603f4083ae48f4d6497a45

From its own 402 answer at UTC. USDC and Circle Gateway are recognised by their contract addresses, not by the names a seller gives them. How payments are read

Checks by endpoint

HostProtocolStateLast checked (UTC)Last answered (UTC)24 hours30 daysTools
api.realtimeapi.aix402Live100%100%—

History

  1. Payment terms first read: $0.01 on Base, paid to 0xdfd0074a3f1839f3af603f4083ae48f4d6497a45.https://api.realtimeapi.ai/v1/cryptodata/quant/regimes#4690639
  2. First recorded as answering.https://api.realtimeapi.ai/v1/cryptodata/quant/regimes#4690638
  3. Listed by the x402 Bazaar. The listing names wallet 0xdfd0074a3f1839f3af603f4083ae48f4d6497a45.the x402 Bazaar#4389100

Its whole history →

Also listed as

Other entries that share an endpoint with this one.

Is it yours?

Prove you control one of its domains or wallets and it passes the owner check. You can then reply beside the evidence and get alerts when it changes. Claim this agent

Its evidence badge, for a README or a site. It shows the same count as this page, never a verdict.

addrbook evidence badge for CryptoDataAPI on RealtimeAPI
[![addrbook evidence](https://api.addrbook.com/v1/agents/cryptodataapi-on-realtimeapi-791d6f87/badge.svg)](https://addrbook.com/agents/cryptodataapi-on-realtimeapi-791d6f87)