x402 List

x402 Protocol Service Directory

Insurance DOI Bulletin Feed (x402)

Data PAYMENT-READY

payment-ready until 2026-08-20

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.

Pay from $0.006 to $0.012 per request in USDC on Arbitrum One / Polygon, settled onchain via the x402 protocol, no signup, no API key needed.

listed 2026-06-03 · no on-chain settlement recorded yet

BASE URL https://api.dynsuplabs.com WEBSITE https://api.dynsuplabs.com ENDPOINTS 4 NETWORK Arbitrum One / Polygon ASSET USDC MEMBER SINCE 2026-06-03 MONITORED SINCE 2026-06-03

ASSESSMENT

updated 3h ago

Evidence-backed signals, not a single score. Click any chip for the proof. Measured values stay read-only; unknown is honest.

reliability 100%
uptime 24h
100%
uptime 7d
100%
uptime 30d
100%
uptime 90d
97.2%
response p95
453ms
avg response
297ms
total checks
2,736

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

compliance A (13/13)

13 of 13 x402 conformance checks pass. Full checklist below.

jump to compliance checklist

price $0.006 to $0.012 (p41 in Data)
price (min)
$0.006
price (max)
$0.012
category percentile (min)
p41 in Data
category percentile (max)
p32 in Data
endpoints / prices
4 / 2
model
tiered
stability
100%
risk clean

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.

traction $0.00 30d · 0 buyers
volume 30d
$0.00
buyers 30d
0
settlements 30d
0
first settlement
---
last settlement
---
top buyer share
-
trend 7d vs 30d
-
networks
eip155:137
volume all-time
$0
settlements all-time
0
median settlement 30d
-
max settlement 30d
-
settled via
-

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

Top buyer share is a concentration signal, not part of the ranking score.

WHAT IT DOES

ai-derived

Provides access to insurance department of insurance bulletins and NAIC form adoptions.

category
insurance-data
in
query params
insurancedata-feedregulatorybulletins

AI-generated summary. The measured data is never altered by it.

ENDPOINTS

Service endpoints with HTTP method, path, description, pricing, and network
METHOD PATH DESCRIPTION PRICE NETWORK ASSET 402 CHANNEL
GET /api/v1/bulletins/recent $0.006 Arbitrum One/Polygon USDC header
GET /api/v1/bulletins/search $0.012 Arbitrum One/Polygon USDC header
GET /api/v1/bulletins/state/CA $0.006 Arbitrum One/Polygon USDC header
GET /api/v1/naic-668/adoptions $0.006 Arbitrum One/Polygon USDC header
4 endpoints

REQUEST / RESPONSE EXAMPLE

An unpaid request to GET /api/v1/bulletins/recent returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.

// request
curl -i 'https://api.dynsuplabs.com/api/v1/bulletins/recent'
// 402 response (captured by monitor) · 4 payloads · click to expand
[
  {
    "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
  },
  {
    "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
  },
  {
    "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
  },
  {
    "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
  }
]

OVER TIME

All charts use the 30d selector; 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. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.

UPTIME
07-15 · uptime 100.0% · 223ms avg07-16 · uptime 100.0% · 217ms avg07-17 · uptime 100.0% · 179ms avg07-18 · uptime 100.0% · 169ms avg07-19 · uptime 100.0% · 196ms avg07-20 · uptime 100.0% · 173ms avg07-21 · uptime 100.0% · 181ms avg07-22 · uptime 100.0% · 275ms avg07-23 · uptime 100.0% · 279ms avg07-24 · uptime 100.0% · 297ms avg07-25 · uptime 100.0% · 266ms avg07-26 · uptime 100.0% · 306ms avg07-27 · uptime 100.0% · 302ms avg07-28 · uptime 100.0% · 243ms avg07-29 · uptime 100.0% · 331ms avg07-30 · uptime 100.0% · 290ms avg07-31 · uptime 100.0% · 346ms avg08-01 · uptime 100.0% · 391ms avg08-02 · uptime 100.0% · 395ms avg08-03 · uptime 100.0% · 280ms avg08-04 · uptime 100.0% · 552ms avg08-05 · uptime 100.0% · 337ms avg08-06 · uptime 100.0% · 450ms avg08-07 · uptime 100.0% · 368ms avg08-08 · uptime 100.0% · 476ms avg08-09 · uptime 100.0% · 185ms avg08-10 · uptime 100.0% · 493ms avg08-11 · uptime 100.0% · 334ms avg08-12 · uptime 100.0% · 187ms avg08-13 · uptime 100.0% · 204ms avg07-1508-13
30d UPTIME 100%
RESPONSE TIME
07-15 · 223ms avg07-15 · 223ms avg07-16 · 217ms avg07-16 · 217ms avg07-17 · 179ms avg07-17 · 179ms avg07-18 · 169ms avg07-18 · 169ms avg07-19 · 196ms avg07-19 · 196ms avg07-20 · 173ms avg07-20 · 173ms avg07-21 · 181ms avg07-21 · 181ms avg07-22 · 275ms avg07-22 · 275ms avg07-23 · 279ms avg07-23 · 279ms avg07-24 · 297ms avg07-24 · 297ms avg07-25 · 266ms avg07-25 · 266ms avg07-26 · 306ms avg07-26 · 306ms avg07-27 · 302ms avg07-27 · 302ms avg07-28 · 243ms avg07-28 · 243ms avg07-29 · 331ms avg07-29 · 331ms avg07-30 · 290ms avg07-30 · 290ms avg07-31 · 346ms avg07-31 · 346ms avg08-01 · 391ms avg08-01 · 391ms avg08-02 · 395ms avg08-02 · 395ms avg08-03 · 280ms avg08-03 · 280ms avg08-04 · 552ms avg08-04 · 552ms avg08-05 · 337ms avg08-05 · 337ms avg08-06 · 450ms avg08-06 · 450ms avg08-07 · 368ms avg08-07 · 368ms avg08-08 · 476ms avg08-08 · 476ms avg08-09 · 185ms avg08-09 · 185ms avg08-10 · 493ms avg08-10 · 493ms avg08-11 · 334ms avg08-11 · 334ms avg08-12 · 187ms avg08-12 · 187ms avg08-13 · 204ms avg08-13 · 204ms avg07-1508-13
AVG RESP 298ms
PRICE (captured 402, USD)
07-14 · $0.00607-20 · $0.00608-13 · $0.006$0.00607-1408-13

Median across 4 endpoints. Use the selector to isolate one.

SUB-SCORES (uptime + x402 compliance)
07-14 uptime: 95.8% compliance: 92% checks07-15 uptime: 99.2% compliance: 92% checks07-16 uptime: 100.0% compliance: 92% checks07-17 uptime: 100.0% compliance: 100% checks07-18 uptime: 100.0% compliance: 100% checks07-19 uptime: 100.0% compliance: 100% checks07-20 uptime: 100.0% compliance: 100% checks07-21 uptime: 100.0% compliance: 100% checks07-22 uptime: 100.0% compliance: 100% checks07-23 uptime: 100.0% compliance: 100% checks07-24 uptime: 100.0% compliance: 100% checks07-25 uptime: 100.0% compliance: 100% checks07-26 uptime: 100.0% compliance: 100% checks07-27 uptime: 100.0% compliance: 100% checks07-28 uptime: 100.0% compliance: 93% checks07-29 uptime: 100.0% compliance: 93% checks07-30 uptime: 100.0% compliance: 93% checks07-31 uptime: 100.0% compliance: 93% checks08-01 uptime: 100.0% compliance: 93% checks08-02 uptime: 100.0% compliance: 93% checks08-03 uptime: 100.0% compliance: 93% checks08-04 uptime: 100.0% compliance: 100% checks08-05 uptime: 100.0% compliance: 100% checks08-06 uptime: 100.0% compliance: 100% checks08-07 uptime: 100.0% compliance: 100% checks08-08 uptime: 100.0% compliance: 100% checks08-09 uptime: 100.0% compliance: 100% checks08-10 uptime: 100.0% compliance: 100% checks08-11 uptime: 100.0% compliance: 100% checks08-12 uptime: 100.0% compliance: 100% checks08-13 uptime: 100.0% compliance: 100% checksuptimecompliance07-1408-13

checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression

PILLARS OVER TIME (measured)

Measured site and economics pillars from the assessment history, so the latest value shown elsewhere on this page reads as a point on a trend rather than a permanent state.

VOLUME (on-chain settlement, USD)
no on-chain volume yet
DISTINCT BUYERS
no distinct buyers yet

COMPLIANCE

13/13 checks pass · grade A

last 402 captured 2026-07-20 · last up 2026-08-13

  • 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

SITE PILLARS

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
recent checks (18) live · click to expand
TIME STATUS RESP CAUSE
● OK 196ms
● OK 366ms
● OK 368ms
● SLOW 1290ms
● OK 268ms
● OK 398ms
● OK 338ms
● OK 362ms
● OK 443ms
● OK 386ms
● OK 423ms
● OK 241ms
● OK 205ms
● OK 228ms
● OK 172ms
● OK 151ms
● OK 182ms
● OK 146ms

EMBED THIS BADGE

Show that Insurance DOI Bulletin Feed (x402) is monitored on x402-list. Paste this on your site or README, it links back to this live listing.

Insurance DOI Bulletin Feed (x402) listed on x402-list
status
Insurance DOI Bulletin Feed (x402) uptime on x402-list
live uptime
// 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>

RUN THIS SERVICE?

Keep this listing accurate: propose changes to the name, description, website, category or add new endpoints to monitor. Ownership is verified with a domain proof and every change is reviewed manually; measured data stays read-only.

[ 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) ]

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