x402-niche-briefs.fly.dev
One section of the California Delete Act DROP 45-day cycle ops pack for registered data brokers: ops_checklist, intake_fields, or do_not, plus buyer, trigger and portal metadata. Pass ?section=ops_checklist|intake_fields|do_not. JSON. Full pack: /v1/ca-drop-cycle ($0.05). Ops checklist only; not legal advice. Unknown section returns 404, not charged.
DataLiveeip155:8453Exactvia cdp
CaliforniaDelete-actDropData-brokerPrivacy
Settlements · 30d
350↑ 17300%
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days.
$3.88
Verified settled volume
355 settlements proven x402 by their on-chain EIP-3009 marker.
$0.010
Listed price
As published in the catalog. Always read the live 402 before paying.
2
Calls · 30d
Upstream's own call count for this endpoint, not ours.
2
Unique payers · 30d
Last called 2026-10-25 20:35Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x847f54ae8dDFD71ed7bC930C1f7a73576FAb03A9The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Provider
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
0.01USDC≈ $0.01 USD
on Base · exact scheme
Pay 0.01 USDC on Base to 0x847f…b03A9. The signed payment is good for 5 minutes.
- Paid to
- 0x847f…b03A9
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 10000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x847f54ae8dDFD71ed7bC930C1f7a73576FAb03A9",
"amount": "10000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"section": "ops_checklist"
}
},
"output": {
"type": "json",
"example": {
"sku": "ca-drop-cycle",
"as_of": "2026-09-06",
"buyer": "Ops lead or agent acting for a mid-market / small California data broker (or counsel's ops desk) that must run recurring 45-day hash-match-status cycles on C...",
"items": [
"Confirm entity string matches Data Broker Registry listing exactly",
"Log into client's DROP account (client credentials; do not store passwords in this SKU)"
],
"title": "California Delete Act DROP 45-day cycle ops pack",
"portal": {
"name": "CalPrivacy DROP",
"registry": "California Data Broker Registry (public)",
"cycle_days": 45,
"live_since": "2026-08-01"
},
"section": "ops_checklist",
"disclaimer": "Operational checklist only. Not legal advice. Not a determination of data-broker status or exemption. Do not give counsel opinions. Client runs DROP under th...",
"buyer_trigger": "Broker appears on the public CalPrivacy Data Broker Registry and DROP has been live since Aug 1, 2026 — next 45-day cycle is due or overdue.",
"full_pack_url": "https://x402-niche-briefs.fly.dev/v1/ca-drop-cycle"
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method"
],
"properties": {
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"type": "object",
"required": [
"section"
],
"properties": {
"section": {
"enum": [
"ops_checklist",
"intake_fields",
"do_not"
],
"type": "string",
"description": "CA DROP pack section id"
}
}
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"as_of",
"sku",
"title",
"buyer",
"buyer_trigger",
"portal",
"section",
"items",
"full_pack_url",
"disclaimer"
],
"properties": {
"sku": {
"type": "string"
},
"as_of": {
"type": "string"
},
"buyer": {
"type": "string"
},
"items": {
"type": "array",
"items": {
"type": "string"
}
},
"title": {
"type": "string"
},
"portal": {
"type": "object",
"required": [
"name",
"live_since",
"cycle_days",
"registry"
],
"properties": {
"name": {
"type": "string"
},
"registry": {
"type": "string"
},
"cycle_days": {
"type": "number"
},
"live_since": {
"type": "string"
}
}
},
"section": {
"type": "string"
},
"disclaimer": {
"type": "string"
},
"buyer_trigger": {
"type": "string"
},
"full_pack_url": {
"type": "string"
}
}
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-10-25 20:35Z
- Last indexed by Roundhouse
- 2026-10-26 20:40Z
- Last enriched (probe, favicon, geo)
- 2026-10-26 10:46Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 402
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service x402-niche-briefs.fly.dev and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=x402-niche-briefs.fly.dev' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://x402-niche-briefs.fly.dev/v1/ca-drop-cycle/section, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.