globax-proof/1 · v1.0.0 · public beta

    Proof interoperability

    GlobaX turns human activity into deterministic system records. Every record carries a stable public identifier. This page documents the open interface that lets an independent machine resolve that identifier and read its verification state — without an account, an API key, or access to the GlobaX application.

    Quick start

    One unauthenticated GET. CORS is open, so this works from a browser, a server, or an agent.

    curl -s https://globax-social-fusion.com/api/public/v1/proof/gx_post_57647469-5cfd-4251-9467-45538ddd6482
    Capabilities document /.well-known/globax-proof.json

    Endpoints

    GET
    /.well-known/globax-proof.json

    Zero-knowledge entry point. Tells an unfamiliar machine what GlobaX proof is and where verification lives.

    GET
    /api/public/v1/capabilities

    Full discovery document: endpoints, fields, integrity model, privacy model, boundaries, versioning.

    GET
    /api/public/v1/proof/{gx_code}

    Resolve a proof identifier to its machine-readable verification state.

    Verification response

    {
  "protocol": "globax-proof/1",
  "api_version": "1.0.0",
  "verified": true,
  "proof": {
    "proof_id": "…",
    "gx_code": "gx_post_57647469-5cfd-4251-9467-45538ddd6482",
    "proof_type": "…",
    "module": "social_post",
    "receipt_state": "recorded_beta",
    "lifecycle_status": "active",
    "is_demo": false,
    "recorded_at": "2026-08-19T17:58:08.318Z",
    "label": "…",
    "location_label": "…",
    "prototype_notice": "…"
  },
  "integrity": {
    "canonical_uri": "…/api/public/v1/proof/gx_post_57647469-5cfd-4251-9467-45538ddd6482",
    "human_uri": "…/proof/gx_post_57647469-5cfd-4251-9467-45538ddd6482",
    "record_digest": "<sha-256 hex>",
    "digest_algorithm": "sha-256",
    "checked_at": "…"
  },
  "boundaries": { "…": "what this does and does not verify" }
}

    record_digest is a SHA-256 fingerprint over protocol|proof_id|gx_code|moment_type|receipt_state|status|is_demo|created_at. Two reads of an unchanged record produce the same digest, so an external system can detect drift. It is a fingerprint, not a signature.

    Status codes

    200Record found. Verification payload returned.
    400Malformed identifier (pattern ^[A-Za-z0-9_.:-]{3,128}$).
    404No public record resolves to this identifier.
    503Verification service temporarily unavailable.
    {
  "protocol": "globax-proof/1",
  "api_version": "1.0.0",
  "verified": false,
  "error": {
    "code": "not_found",
    "message": "No public GlobaX proof record resolves to this identifier."
  },
  "boundaries": { "…": "…" }
}

    What this proves — and what it does not

    Verifiable

    • that a proof record with this identifier exists in the GlobaX system of record
    • the module and moment type the record was created under
    • the recorded receipt state and lifecycle status
    • the timestamp at which the record was written
    • whether the record is seeded demonstration data

    Not verifiable

    • identity of any account, person, or organisation
    • any monetary amount, balance, payment, settlement, or withdrawal
    • eligibility for money, shares, securities, or any financial product
    • endorsement, partnership, certification, or accreditation by GlobaX
    • external real-world facts asserted by a user inside the recorded activity

    Public beta prototype. Recognition and record-keeping only. A verified proof record is not a payment, settlement, investment, security, guarantee, or partner claim.

    Privacy model

    The public payload contains no personal data. Account identifiers, action trails, media, record titles, share links and internal application paths are not part of the response. The owning account identifier is blocked a second time at the database layer by column-level grants, so no unauthenticated request can retrieve it — not through this API and not by asking the data layer directly.

    Honest scope

    This interface proves that GlobaX proof records are externally resolvable and independently readable. It does not yet constitute universal interoperability with third-party activity sources, financial institutions or public bodies. That next step requires either a published external schema and adaptor standard, or at least one genuinely independent third-party integration. Neither is claimed here.

    Proof momentsArchitectureDevelopersLegal and prototype status