{
  "$schema": "https://schemas.web-bot-auth.org/v1/web-bot-auth.json",
  "version": "1.0",
  "lastUpdated": "2026-05-17",
  "entity": {
    "name": "Humark",
    "url": "https://humark.id",
    "operator": "AU-SVRN",
    "operatorUrl": "https://ausvrn.com"
  },
  "policy": {
    "stance": "open",
    "summary": "Humark is open to participating in signed-bot identity programs (Cloudflare Web Bot Auth, IETF HTTP Message Signatures for crawlers). When an AI lab publishes a signed-bot identity, the entry below should be populated with their verification key and identity endpoint.",
    "preferredScheme": "http-message-signatures",
    "fallbackScheme": "user-agent-and-ip-allowlist-via-robots-txt"
  },
  "verifiedBots": [],
  "trustAnchor": {
    "method": "well-known-publication",
    "verificationUrl": "https://humark.id/.well-known/web-bot-auth.json"
  },
  "contact": "hello@humark.id",
  "notes": [
    "This file is a readiness signal. As of 2026-05-17 no AI lab has published a signed-bot identity that Humark verifies against. The verifiedBots array will be populated when labs adopt Cloudflare's Web Bot Auth or an equivalent IETF-track HTTP-signature scheme.",
    "Crawler policy in the meantime is in /robots.txt with the three-tier model (training, search-retrieval, user-triggered).",
    "AI labs interested in establishing a verified-bot relationship should write to hello@humark.id with their preferred signature scheme, key endpoint, and contact for revocation."
  ]
}