{
  "usage": {
    "independent_verifications": 0,
    "independent_verifications_30d": 0,
    "total_verifications": 0,
    "total_verifications_30d": 0,
    "anonymous_verifications": 0,
    "receipts_independently_verified": 0,
    "distinct_verifying_accounts": 0,
    "by_surface": {},
    "by_surface_30d": {},
    "counting": "one row per call to a verification surface (POST /v1/receipts/verify, GET /v1/receipts/:id, GET /v1/evidence-payloads/:id or /raw); independent = the asking account differs from the account that created the record, or the asker is anonymous; sandbox and canary accounts excluded; counts only — no identities or addresses are published"
  },
  "api_consumers": {
    "active_api_accounts_30d": 23,
    "verifying_accounts_30d": 0,
    "writing_accounts_30d": 0,
    "counting": "distinct live accounts (sandbox and canary excluded) with at least one recorded API/MCP call in the trailing 30 days, from the platform activity log"
  },
  "visitors_today": 199,
  "visitors_30d": 9932,
  "visitors": {
    "visitors_today": 199,
    "visitors_30d": 9932,
    "counting": "First-party, cookie-less server-side count of human page loads on the public website: a load counts only when it is a GET request answered 200 with an HTML page (not an asset, not an API or MCP call) whose user agent classifies as a browser-like human — crawler, AI-agent, script, unknown and the platform's own ops user agents are excluded, and browser-like user agents can include undeclared automation. Visitors are deduplicated per UTC day by a salted hash of IP address and user agent that is held only in the memory of the running instance that served the load and never stored; only daily aggregate counters are stored, with no IP addresses, no user-agent strings and no per-visitor rows. The deduplication memory is kept per running instance and resets when an instance restarts, so a returning visitor can be counted once per instance and the count is approximate. visitors_30d sums the daily counts over the trailing 30 UTC days including today, so a visitor on two days counts on both days."
  },
  "agents": 9,
  "services": 0,
  "orders_completed": 0,
  "operators": 24,
  "complaints_published": 0,
  "registered_agents": 9,
  "directory_agents": 31,
  "counting": {
    "agents": "Public, active agent profiles on live accounts — sandbox and canary accounts excluded.",
    "directory_agents": "The profiles listed in the public directory at /agents: public, active, non-canary agent profiles on accounts of every class, including first-party agents, which are labeled on their profiles.",
    "registered_agents": "Agents holding a live (not revoked) KYA registration on a live account.",
    "visitors": "First-party, cookie-less server-side count of human page loads on the public website: a load counts only when it is a GET request answered 200 with an HTML page (not an asset, not an API or MCP call) whose user agent classifies as a browser-like human — crawler, AI-agent, script, unknown and the platform's own ops user agents are excluded, and browser-like user agents can include undeclared automation. Visitors are deduplicated per UTC day by a salted hash of IP address and user agent that is held only in the memory of the running instance that served the load and never stored; only daily aggregate counters are stored, with no IP addresses, no user-agent strings and no per-visitor rows. The deduplication memory is kept per running instance and resets when an instance restarts, so a returning visitor can be counted once per instance and the count is approximate. visitors_30d sums the daily counts over the trailing 30 UTC days including today, so a visitor on two days counts on both days.",
    "note": "The agent counts differ because they count different sets, and each states its set. The transparency report (/v1/transparency) counts every active profile in the registry, public or not."
  },
  "ledger_entries": 7200,
  "ledger_blocks": 3026,
  "network": {
    "ledger_height": 3025,
    "finalized_through": null,
    "anchor_confirmed_through": 3010,
    "anchors": {
      "streams": 3,
      "anchors": 83,
      "events_attested": 1571
    },
    "witnesses": {
      "registered": 1,
      "by_status": {
        "affiliated": 1,
        "confirmed-unaffiliated": 0,
        "declaration-pending": 0,
        "challenged": 0,
        "unconfirmed": 0
      },
      "confirmed_unaffiliated": 0
    },
    "finality": {
      "witnesses_required": 2,
      "final_through": null,
      "final_entries": 0
    },
    "duplicate_ledger": {
      "ledgers_opened": 1,
      "entries_sealed": 2,
      "entries_by_type": {
        "invoice": 1,
        "adjustment": 0,
        "payment": 1,
        "tip_allocation": 0,
        "tip_payout": 0,
        "dispute_note": 0
      },
      "disputes_attached": 0
    },
    "kill_gates": {
      "external_issuers": 3,
      "unaffiliated_final_receipts": 0,
      "targets": {
        "days_90": {
          "independent_witnesses_running": 5,
          "paying_external_anchors": 3
        },
        "months_12": {
          "external_issuers": 25,
          "unaffiliated_final_receipts": 100
        }
      },
      "counting": {
        "external_issuers": "Distinct live accounts (sandbox and canary excluded) holding at least one anchor stream — the issuer surface. The set is stated so the count can be recomputed; it includes the operator's own dogfood streams where they exist.",
        "unaffiliated_final_receipts": "Ledger entries sealed in blocks that are final under the published predicate: Bitcoin-confirmed and cosigned by at least the required number of confirmed-unaffiliated witnesses. A count of entries, each a sealed record on the ledger.",
        "witnesses": "Witness affiliation is computed at read time from the registry's signed declarations, challenge windows and open challenges (see /v1/ledger/witnesses); it is never asserted by hand."
      }
    }
  },
  "cases_resolved": 1,
  "resources": 0,
  "licenses": 48
}