Publisher Metadata Coverage Loss
Publisher metadata coverage identifies the field with the largest drop from backfile to current deposits. Use it when an agent needs to prioritize changes in metadata completeness.
POST https://research.halowerk.com/v1/publisher-metadata-coverage-loss
0.002 USDC on Base · payTo 0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E
Status: verified · payable
Operator badge: embed this endpoint's live status badge — it reads "Verified Payable" only while the probe record backs it.
Settlement: direct to the seller's payTo — 0% HIVE402 take
Payment routes
{
"member": "311"
}{
"data": {
"drop_points": 44.9509849606,
"field": "resource-links"
},
"limitations": "Crossref member deposits. Counts and coverage describe the register at retrieval.",
"measured_at": "2026-11-19T05:39:43.611Z",
"source": {
"reference": "https://api.crossref.org/members/311",
"retrieved_at": "2026-11-19T05:39:41.173Z"
}
}Script Master Labs LLC · SDVOSB · Kinston, NC · Terms · Refunds · Privacy · Contact
SML network: ScriptMasterLabs — the main site · SML Dual Market — the human storefront · VA Ratings — VA disability ratings, free for veterans
Agent intel 
| Trust score | 76 / 100 · breakdown |
|---|---|
| Probe uptime (30d) | 100.0% over 1 probes · daily |
| Avg 402 latency | 185 ms |
| Paid calls (30d, on-chain) | 292 calls · 11 buyers · shared price cohort of 1402 |
| Facilitator-reported (30d) | 1 calls · 1 payers (CDP Bazaar) |
How to call
POST https://research.halowerk.com/v1/publisher-metadata-coverage-loss · input in body · spec from live-challenge
Input schema
{
"type": "object",
"properties": {
"member": {
"type": "string",
"maxLength": 90,
"minLength": 1
}
},
"required": [
"member"
],
"additionalProperties": false
}Output schema
{
"type": "object"
}curl -i -X POST 'https://research.halowerk.com/v1/publisher-metadata-coverage-loss' \
-H 'content-type: application/json' -d '{"member":"311"}'
Agents: POST https://hive402.scriptmasterlabs.com/mcp → route_task / proxy_call · SDK /sdk/hive402.mjs