Insurance DOI Bulletin Feed (x402)

offline

payment-ready 2026-08-29, probe currently failing

Normalized state Department of Insurance bulletins and NAIC Model Law 668 adoption feed.

api.dynsuplabs.com ↗

Call it x402 v2

x402 v2

Base URL: https://api.dynsuplabs.com
Payment: x402 v2, header channel

$ curl -i 'https://api.dynsuplabs.com/api/v1/bulletins/recent'

An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the PAYMENT-SIGNATURE header.

Endpoints 4 paid routes on api.dynsuplabs.com

GET/api/v1/bulletins/recentArbitrum One+Pol$0.006since 06-16

GET/api/v1/bulletins/searchArbitrum One+Pol$0.012since 06-16

GET/api/v1/bulletins/state/CAArbitrum One+Pol$0.006since 06-16

GET/api/v1/naic-668/adoptionsArbitrum One+Pol$0.006since 06-16

Prices as captured in the 402 response: median $0.006 across the 4 endpoints.

Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
Method	Path	Description	Price	Network	Asset	402 channel	Captured
GET	/api/v1/bulletins/recent	No description	$0.006	Arbitrum One+Pol	USDC, UNKNOWN	header	since 06-16
GET	/api/v1/bulletins/search	No description	$0.012	Arbitrum One+Pol	USDC, UNKNOWN	header	since 06-16
GET	/api/v1/bulletins/state/CA	No description	$0.006	Arbitrum One+Pol	USDC, UNKNOWN	header	since 06-16
GET	/api/v1/naic-668/adoptions	No description	$0.006	Arbitrum One+Pol	USDC, UNKNOWN	header	since 06-16

Payment evidence

402 payload captured at 2026-07-20 13:47:02 UTC. Check evidence JSON · Measurement methodology.

{
  "accepts": [
    {
      "asset": "0x3c499c542cef5e3811e1192ce70d8cc03d5c3359",
      "extra": {
        "doc": "Custom scheme 'exact-prepay-proof': this API does NOT use the standard x402 facilitator-settled 'exact' flow. To pay, the client MUST itself broadcast a USDC transfer of the stated amount to payTo on a supported chain (Polygon 137 or Arbitrum 42161), wait for the transfer to land, then retry the request with an X-PAYMENT header = base64(JSON) of { txHash, chainId, payerAddress, amount, timestamp }. S2 verifies that transaction hash on-chain (recipient, amount, confirmations, freshness) before delivering data. Blockchain transactions are irreversible; payments for successfully delivered responses are final and non-refundable. There is no facilitator and no signed-authorization (EIP-3009) settlement; sending a standard 'exact' signed authorization will be rejected. Full terms: https://api.dynsuplabs.com/legal/tos — flow doc: /api/v1/endpoints#payment.",
        "flow": "prepay-then-prove",
        "not_standard_exact": true,
        "payment_payload_fields": [
          "txHash",
          "chainId",
          "payerAddress",
          "amount",
          "timestamp"
        ]
      },
      "payTo": "0xc899D17E9aA71A77640c938268AFF997b484D548",
      "amount": "6000",
      "scheme": "exact-prepay-proof",
      "network": "eip155:137",
      "maxTimeoutSeconds": 300
    },
    {
      "asset": "0xaf88d065e77c8cc2239327c5edb3a432268e5831",
      "extra": {
        "doc": "Custom scheme 'exact-prepay-proof': this API does NOT use the standard x402 facilitator-settled 'exact' flow. To pay, the client MUST itself broadcast a USDC transfer of the stated amount to payTo on a supported chain (Polygon 137 or Arbitrum 42161), wait for the transfer to land, then retry the request with an X-PAYMENT header = base64(JSON) of { txHash, chainId, payerAddress, amount, timestamp }. S2 verifies that transaction hash on-chain (recipient, amount, confirmations, freshness) before delivering data. Blockchain transactions are irreversible; payments for successfully delivered responses are final and non-refundable. There is no facilitator and no signed-authorization (EIP-3009) settlement; sending a standard 'exact' signed authorization will be rejected. Full terms: https://api.dynsuplabs.com/legal/tos — flow doc: /api/v1/endpoints#payment.",
        "flow": "prepay-then-prove",
        "not_standard_exact": true,
        "payment_payload_fields": [
          "txHash",
          "chainId",
          "payerAddress",
          "amount",
          "timestamp"
        ]
      },
      "payTo": "0xc899D17E9aA71A77640c938268AFF997b484D548",
      "amount": "6000",
      "scheme": "exact-prepay-proof",
      "network": "eip155:42161",
      "maxTimeoutSeconds": 300
    }
  ],
  "resource": {
    "url": "",
    "terms_url": "https://api.dynsuplabs.com/legal/tos",
    "description": "DOI bulletins for a specific state",
    "privacy_url": "https://api.dynsuplabs.com/legal/privacy"
  },
  "x402Version": 2
}

Other captured 402 responses (3)

Captured payload 2 of 4

{
  "accepts": [
    {
      "asset": "0x3c499c542cef5e3811e1192ce70d8cc03d5c3359",
      "extra": {
        "doc": "Custom scheme 'exact-prepay-proof': this API does NOT use the standard x402 facilitator-settled 'exact' flow. To pay, the client MUST itself broadcast a USDC transfer of the stated amount to payTo on a supported chain (Polygon 137 or Arbitrum 42161), wait for the transfer to land, then retry the request with an X-PAYMENT header = base64(JSON) of { txHash, chainId, payerAddress, amount, timestamp }. S2 verifies that transaction hash on-chain (recipient, amount, confirmations, freshness) before delivering data. Blockchain transactions are irreversible; payments for successfully delivered responses are final and non-refundable. There is no facilitator and no signed-authorization (EIP-3009) settlement; sending a standard 'exact' signed authorization will be rejected. Full terms: https://api.dynsuplabs.com/legal/tos — flow doc: /api/v1/endpoints#payment.",
        "flow": "prepay-then-prove",
        "not_standard_exact": true,
        "payment_payload_fields": [
          "txHash",
          "chainId",
          "payerAddress",
          "amount",
          "timestamp"
        ]
      },
      "payTo": "0xc899D17E9aA71A77640c938268AFF997b484D548",
      "amount": "6000",
      "scheme": "exact-prepay-proof",
      "network": "eip155:137",
      "maxTimeoutSeconds": 300
    },
    {
      "asset": "0xaf88d065e77c8cc2239327c5edb3a432268e5831",
      "extra": {
        "doc": "Custom scheme 'exact-prepay-proof': this API does NOT use the standard x402 facilitator-settled 'exact' flow. To pay, the client MUST itself broadcast a USDC transfer of the stated amount to payTo on a supported chain (Polygon 137 or Arbitrum 42161), wait for the transfer to land, then retry the request with an X-PAYMENT header = base64(JSON) of { txHash, chainId, payerAddress, amount, timestamp }. S2 verifies that transaction hash on-chain (recipient, amount, confirmations, freshness) before delivering data. Blockchain transactions are irreversible; payments for successfully delivered responses are final and non-refundable. There is no facilitator and no signed-authorization (EIP-3009) settlement; sending a standard 'exact' signed authorization will be rejected. Full terms: https://api.dynsuplabs.com/legal/tos — flow doc: /api/v1/endpoints#payment.",
        "flow": "prepay-then-prove",
        "not_standard_exact": true,
        "payment_payload_fields": [
          "txHash",
          "chainId",
          "payerAddress",
          "amount",
          "timestamp"
        ]
      },
      "payTo": "0xc899D17E9aA71A77640c938268AFF997b484D548",
      "amount": "6000",
      "scheme": "exact-prepay-proof",
      "network": "eip155:42161",
      "maxTimeoutSeconds": 300
    }
  ],
  "resource": {
    "url": "",
    "terms_url": "https://api.dynsuplabs.com/legal/tos",
    "description": "Current state-by-state NAIC Model Law 668 adoption status",
    "privacy_url": "https://api.dynsuplabs.com/legal/privacy"
  },
  "x402Version": 2
}

Captured payload 3 of 4

{
  "accepts": [
    {
      "asset": "0x3c499c542cef5e3811e1192ce70d8cc03d5c3359",
      "extra": {
        "doc": "Custom scheme 'exact-prepay-proof': this API does NOT use the standard x402 facilitator-settled 'exact' flow. To pay, the client MUST itself broadcast a USDC transfer of the stated amount to payTo on a supported chain (Polygon 137 or Arbitrum 42161), wait for the transfer to land, then retry the request with an X-PAYMENT header = base64(JSON) of { txHash, chainId, payerAddress, amount, timestamp }. S2 verifies that transaction hash on-chain (recipient, amount, confirmations, freshness) before delivering data. Blockchain transactions are irreversible; payments for successfully delivered responses are final and non-refundable. There is no facilitator and no signed-authorization (EIP-3009) settlement; sending a standard 'exact' signed authorization will be rejected. Full terms: https://api.dynsuplabs.com/legal/tos — flow doc: /api/v1/endpoints#payment.",
        "flow": "prepay-then-prove",
        "not_standard_exact": true,
        "payment_payload_fields": [
          "txHash",
          "chainId",
          "payerAddress",
          "amount",
          "timestamp"
        ]
      },
      "payTo": "0xc899D17E9aA71A77640c938268AFF997b484D548",
      "amount": "6000",
      "scheme": "exact-prepay-proof",
      "network": "eip155:137",
      "maxTimeoutSeconds": 300
    },
    {
      "asset": "0xaf88d065e77c8cc2239327c5edb3a432268e5831",
      "extra": {
        "doc": "Custom scheme 'exact-prepay-proof': this API does NOT use the standard x402 facilitator-settled 'exact' flow. To pay, the client MUST itself broadcast a USDC transfer of the stated amount to payTo on a supported chain (Polygon 137 or Arbitrum 42161), wait for the transfer to land, then retry the request with an X-PAYMENT header = base64(JSON) of { txHash, chainId, payerAddress, amount, timestamp }. S2 verifies that transaction hash on-chain (recipient, amount, confirmations, freshness) before delivering data. Blockchain transactions are irreversible; payments for successfully delivered responses are final and non-refundable. There is no facilitator and no signed-authorization (EIP-3009) settlement; sending a standard 'exact' signed authorization will be rejected. Full terms: https://api.dynsuplabs.com/legal/tos — flow doc: /api/v1/endpoints#payment.",
        "flow": "prepay-then-prove",
        "not_standard_exact": true,
        "payment_payload_fields": [
          "txHash",
          "chainId",
          "payerAddress",
          "amount",
          "timestamp"
        ]
      },
      "payTo": "0xc899D17E9aA71A77640c938268AFF997b484D548",
      "amount": "6000",
      "scheme": "exact-prepay-proof",
      "network": "eip155:42161",
      "maxTimeoutSeconds": 300
    }
  ],
  "resource": {
    "url": "",
    "terms_url": "https://api.dynsuplabs.com/legal/tos",
    "description": "Recent state DOI bulletins from the last 7 days",
    "privacy_url": "https://api.dynsuplabs.com/legal/privacy"
  },
  "x402Version": 2
}

Captured payload 4 of 4

{
  "accepts": [
    {
      "asset": "0x3c499c542cef5e3811e1192ce70d8cc03d5c3359",
      "extra": {
        "doc": "Custom scheme 'exact-prepay-proof': this API does NOT use the standard x402 facilitator-settled 'exact' flow. To pay, the client MUST itself broadcast a USDC transfer of the stated amount to payTo on a supported chain (Polygon 137 or Arbitrum 42161), wait for the transfer to land, then retry the request with an X-PAYMENT header = base64(JSON) of { txHash, chainId, payerAddress, amount, timestamp }. S2 verifies that transaction hash on-chain (recipient, amount, confirmations, freshness) before delivering data. Blockchain transactions are irreversible; payments for successfully delivered responses are final and non-refundable. There is no facilitator and no signed-authorization (EIP-3009) settlement; sending a standard 'exact' signed authorization will be rejected. Full terms: https://api.dynsuplabs.com/legal/tos — flow doc: /api/v1/endpoints#payment.",
        "flow": "prepay-then-prove",
        "not_standard_exact": true,
        "payment_payload_fields": [
          "txHash",
          "chainId",
          "payerAddress",
          "amount",
          "timestamp"
        ]
      },
      "payTo": "0xc899D17E9aA71A77640c938268AFF997b484D548",
      "amount": "12000",
      "scheme": "exact-prepay-proof",
      "network": "eip155:137",
      "maxTimeoutSeconds": 300
    },
    {
      "asset": "0xaf88d065e77c8cc2239327c5edb3a432268e5831",
      "extra": {
        "doc": "Custom scheme 'exact-prepay-proof': this API does NOT use the standard x402 facilitator-settled 'exact' flow. To pay, the client MUST itself broadcast a USDC transfer of the stated amount to payTo on a supported chain (Polygon 137 or Arbitrum 42161), wait for the transfer to land, then retry the request with an X-PAYMENT header = base64(JSON) of { txHash, chainId, payerAddress, amount, timestamp }. S2 verifies that transaction hash on-chain (recipient, amount, confirmations, freshness) before delivering data. Blockchain transactions are irreversible; payments for successfully delivered responses are final and non-refundable. There is no facilitator and no signed-authorization (EIP-3009) settlement; sending a standard 'exact' signed authorization will be rejected. Full terms: https://api.dynsuplabs.com/legal/tos — flow doc: /api/v1/endpoints#payment.",
        "flow": "prepay-then-prove",
        "not_standard_exact": true,
        "payment_payload_fields": [
          "txHash",
          "chainId",
          "payerAddress",
          "amount",
          "timestamp"
        ]
      },
      "payTo": "0xc899D17E9aA71A77640c938268AFF997b484D548",
      "amount": "12000",
      "scheme": "exact-prepay-proof",
      "network": "eip155:42161",
      "maxTimeoutSeconds": 300
    }
  ],
  "resource": {
    "url": "",
    "terms_url": "https://api.dynsuplabs.com/legal/tos",
    "description": "Search bulletins by keyword",
    "privacy_url": "https://api.dynsuplabs.com/legal/privacy"
  },
  "x402Version": 2
}

Can I trust it score from our own monitoring

score from our own monitoring

Not ranked yet: this listing was not in the ranked pool for Data the last time we built it, which happens at most once a minute. A service listed moments ago enters at the next rebuild.

Reliability: 0% uptime 30d
Compliance: A 13/13 checks pass, stale (probe failing)
Price: $0.006 to $0.012 p49 in Data
Risk: clean no risk flag
Traction: $0.00 30d 0 buyers

13/13 compliance checks

402 payload captured
accepts[] array present
payTo address recoverable
payTo at accepts[0].payTo (conformant shape)
payTo is a valid on-chain address
atomic price declared
atomic price in a sane range
asset (token) address declared
network resolves to CAIP-2
payment scheme declared
served over HTTPS
declares the current x402 version (2)
EIP-712 domain parameters present on every EVM entry
x402 v2 envelope delivered in the payment-required header

402 terms unchanged since 2026-07-20. Last up 2026-08-29.

── Site signals

homepage reachable
openapi doc
pricing page
llms.txt
robots.txt
terms page

How the score works

The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.

Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.

Traction is a conservative undercount.

All measured facts

What it does

Normalized state Department of Insurance bulletins and NAIC Model Law 668 adoption feed. Micropayment-gated REST API via x402 protocol. Supports Polygon (eip155:137) and Arbitrum (eip155:42161) chains with USDC payments. Pricing: $0.001/request for bulletins, $0.002/request for search.

Insurance DOI Bulletin Feed (x402) is a listed x402 Data API. Captured payment terms name Arbitrum One, Polygon. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.

Assessment computed at 2026-10-19 01:53:14 UTC. Latest service check observed at 2026-10-18 21:40:01 UTC. Service data JSON · Measurement methodology.

Page rendered at 2026-10-19 03:04:06 UTC. This response time is separate from the observation and computation times attached to each measurement.

Latest endpoint observation: 2026-08-29 02:47:10 UTC. Latest price capture: 2026-07-20 13:47:02 UTC. Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.

Assessment computed at 2026-10-19 01:53:14 UTC. Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.

Observed daily coverage: 2026-09-20 to 2026-10-19 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.

Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.

x402 List home · Services · Data

uptime · latest daily rollup: -
uptime 7d: 0%
uptime 30d: 0%
uptime 90d: 94.2%
response p95: -
avg response: -
total checks: 123

Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.

price (min): $0.006
price (max): $0.012
category percentile (min): p49 in Data
category percentile (max): p32 in Data
endpoints / prices: 4 / 2
model: tiered
stability: 100%

No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.

domain age: -
registrar: -
hosting: custom
domain created: ---

Identity facts, not a risk score.

assessment volume 30d: $0.00
exact assessment volume 30d (USD): 0
assessment recorded at (UTC): 2026-10-19T01:53:14.294Z
buyers 30d: 0
settlements 30d: 0
measured since: --- (start of our harvest window)
last settlement: ---
top buyer share: -
top 3 buyers share: -
concentrated volume: no
trend 7d vs 30d: -
networks: eip155:137
volume all-time: $0
settlements all-time: 0
median settlement 30d: -
max settlement 30d: -

Assessment volume uses the latest 30d assessment. Over time sums daily address snapshots, rounded to cents and refreshed separately. The two sources can differ in timing, precision and shared-address attribution. Amounts use cents for comparison; known sub-cent values keep up to 12 significant digits. The exact stored assessment value is shown above.

Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.

Top buyer share lowers the on-chain traction part of the ranking score behind this page's verdict and /best, by up to half when one address holds all 30d volume. The Recommended and Highest volume sorts of the services list do not use it; they use the Concentrated volume rule instead.

member since: 2026-06-03

Recent checks

Latest 18 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)	Status	HTTP	Response
2026-10-18 21:40:01 UTC	Offline	no response	346ms
2026-10-18 15:39:00 UTC	Offline	no response	110ms
2026-10-18 09:38:02 UTC	Offline	no response	539ms
2026-10-18 03:37:00 UTC	Offline	no response	69ms
2026-10-17 21:36:00 UTC	Offline	no response	69ms
2026-10-17 15:33:00 UTC	Offline	no response	69ms
2026-10-17 09:32:00 UTC	Offline	no response	203ms
2026-10-17 03:31:01 UTC	Offline	no response	363ms
2026-10-16 21:30:01 UTC	Offline	no response	284ms
2026-10-16 15:29:00 UTC	Offline	no response	61ms
2026-10-16 09:28:00 UTC	Offline	no response	27ms
2026-10-16 03:27:00 UTC	Offline	no response	22ms
2026-10-15 21:26:00 UTC	Offline	no response	25ms
2026-10-15 15:25:00 UTC	Offline	no response	31ms
2026-10-15 09:24:00 UTC	Offline	no response	30ms
2026-10-15 03:23:02 UTC	Offline	no response	485ms
2026-10-14 21:22:00 UTC	Offline	no response	20ms
2026-10-14 15:21:00 UTC	Offline	no response	34ms

Changes0 in 30d

No changes recorded in the last 30 days.

all changes

Over time

On-chain volume daily snapshots, USD 30d: $0.00

                                                                                                 
                                                                                                 
                                                                                                 
                                                                                                 
                                                                                                 
       ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  
    $0

volume no data in the payload

Distinct buyers per dayDistinct buyers per day

        ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·  ·

Uptime 29 of 29 completed days below 100%

       ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ░░ ·

uptime 0%

       09-20                                     10-04                                   10-19*

Volume 30d: $0.00
Uptime: 29 of 29 completed days below 100%

Daily on-chain settlement volume in US dollars, 2026-09-20 to 2026-10-19; 30 days have no data in the payload; distinct buyers per day

Day    Volume             USD  Buyers
09-20  · no data, 30 days to 10-19*

More charts

Scores over time

x402 compliance low 13/13, high 13/13

       ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄

09-20 to 10-19* UTC

      ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄

      09-20         10-04     10-19*

Price percentile in Data own low to high; exact values below

       ▁▁ ▃▃ ▃▃ ▃▃ ▃▃ ▃▃ ▃▃ ▃▃ ▃▃ ▅▅ ▅▅ ▅▅ ▅▅ ▅▅ ▇▇ ▇▇ ▇▇ ▇▇ ▇▇ ▇▇ ▇▇ ▇▇ ▇▇ ▇▇ ▅▅ ▅▅ ▅▅ ▅▅ ▅▅ ▅▅

09-20 to 10-19* UTC

      ▁▃▃▃▃▃▃▃▃▅▅▅▅▅▇▇▇▇▇▇▇▇▇▇▅▅▅▅▅▅

      09-20         10-04     10-19*

Site signals present (of 6) own low to high; exact values below

       ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄ ▄▄

09-20 to 10-19* UTC

      ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄

      09-20         10-04     10-19*

       09-20                                     10-04                                   10-19*

      09-20         10-04     10-19*

Scores: one day per column, 09-20 to 10-19*, on the columns of Response time. Uptime held below 100% on some days in this window, including any partial day. Daily readings remain in the Uptime strip and Values. The checklist grew from 11 to 14 checks on 2026-07-28, before this window. Pillar lines use their own low and high. Exact dated readings are available in each readout and in Values.

Each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/insurance-doi-bulletin-feed-x402/price, /scores, /volume and /buyers.

Values

* today so far, partial (UTC).

The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.

Daily snapshot total, no volume data in the last 30d. The visible 30d total in Traction comes from the latest assessment. These sources can differ in their window, refresh time, cent rounding and shared-address attribution.

Daily address snapshots: 2026-09-20 to 2026-10-19 UTC; * today so far, partial (UTC). Daily snapshots store cents. A recorded $0.00 with settlements cannot distinguish exact zero from volume rounded away. Lost precision is unavailable here.

Settlement volume uses the stored USD valuation of tracked payments; it is distinct from token quantities. USD-pegged assets are valued at 1 USD per token in these rollups. The measured settlement floor does not cover all payments to this service.

Assessment history last recorded at 2026-10-19 01:53:14 UTC. Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.

Daily values, 2026-09-20 to 2026-10-19: address settlement volume in USD, distinct buyer and settlement counts, uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
Day	Volume	Buyers	Settlements	Uptime	Response	Compliance	Price percentile	Site signals
2026-09-20	no data	no data	no data	0%	no data	13/13	p47	0/6
2026-09-21	no data	no data	no data	0%	no data	13/13	p48	0/6
2026-09-22	no data	no data	no data	0%	no data	13/13	p48	0/6
2026-09-23	no data	no data	no data	0%	no data	13/13	p48	0/6
2026-09-24	no data	no data	no data	0%	no data	13/13	p48	0/6
2026-09-25	no data	no data	no data	0%	no data	13/13	p48	0/6
2026-09-26	no data	no data	no data	0%	no data	13/13	p48	0/6
2026-09-27	no data	no data	no data	0%	no data	13/13	p48	0/6
2026-09-28	no data	no data	no data	0%	no data	13/13	p48	0/6
2026-09-29	no data	no data	no data	0%	no data	13/13	p49	0/6
2026-09-30	no data	no data	no data	0%	no data	13/13	p49	0/6
2026-10-01	no data	no data	no data	0%	no data	13/13	p49	0/6
2026-10-02	no data	no data	no data	0%	no data	13/13	p49	0/6
2026-10-03	no data	no data	no data	0%	no data	13/13	p49	0/6
2026-10-04	no data	no data	no data	0%	no data	13/13	p50	0/6
2026-10-05	no data	no data	no data	0%	no data	13/13	p50	0/6
2026-10-06	no data	no data	no data	0%	no data	13/13	p50	0/6
2026-10-07	no data	no data	no data	0%	no data	13/13	p50	0/6
2026-10-08	no data	no data	no data	0%	no data	13/13	p50	0/6
2026-10-09	no data	no data	no data	0%	no data	13/13	p50	0/6
2026-10-10	no data	no data	no data	0%	no data	13/13	p50	0/6
2026-10-11	no data	no data	no data	0%	no data	13/13	p50	0/6
2026-10-12	no data	no data	no data	0%	no data	13/13	p50	0/6
2026-10-13	no data	no data	no data	0%	no data	13/13	p50	0/6
2026-10-14	no data	no data	no data	0%	no data	13/13	p49	0/6
2026-10-15	no data	no data	no data	0%	no data	13/13	p49	0/6
2026-10-16	no data	no data	no data	0%	no data	13/13	p49	0/6
2026-10-17	no data	no data	no data	0%	no data	13/13	p49	0/6
2026-10-18	no data	no data	no data	0%	no data	13/13	p49	0/6
2026-10-19*	no data	no data	no data	no data	no data	13/13	p49	0/6

Alternatives in Data

SniperX•x402 strong 97/100 99.9% up 30d $576.86 30d

claw402 strong 97/100 100% up 30d $1.1k 30d

glim.sh strong 95/100 100% up 30d $29.83 30d

cn402 strong 93/100 100% up 30d $39.51 30d

twit.sh strong 93/100 100% up 30d $46.68 30d

5 of 386 other ranked services in Data, ordered by the same measured score.

see the whole category

Own this service?

Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.

Update this listing

Earn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.

Verify this service ($0.25)

Embed a badge

HTML

<a href="https://x402-list.com/services/insurance-doi-bulletin-feed-x402?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/insurance-doi-bulletin-feed-x402.svg" alt="Insurance DOI Bulletin Feed (x402) listed on x402-list" height="28">
</a>

Markdown

[![Insurance DOI Bulletin Feed (x402) on x402-list](https://x402-list.com/badge/insurance-doi-bulletin-feed-x402.svg)](https://x402-list.com/services/insurance-doi-bulletin-feed-x402?utm_source=badge&utm_medium=referral&utm_campaign=embed)

HTML, live uptime variant

<a href="https://x402-list.com/services/insurance-doi-bulletin-feed-x402?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/insurance-doi-bulletin-feed-x402.svg?data=uptime" alt="Insurance DOI Bulletin Feed (x402) uptime on x402-list" height="28">
</a>

Delisting

To request delisting, email info@x402-list.com or update your listing at /services/insurance-doi-bulletin-feed-x402/update.