Download Game! Currently 106 players and visitors. Last logged in:EronkBylethSabaothLmt

Blitzer's Blog >> 70973

Back to blogs index
Posted: 10 Jun 2026 08:05 [ permalink ]
2. The MIND MAP API (Swagger / OpenAPI Prototype)
To power an infinite spatial canvas, the API cannot just return "all data." It
must support Spatial Bounding Box Querying, so the HTML5 browser only loads
what is currently visible on the screen.

YAML
openapi: 3.0.0
info:
  title: Hauki MIND MAP API
  version: 1.0.0
  description: The Conceptual Nexus and Spatial Knowledge Graph for the Hauki
Ecosystem.
paths:
  /api/v1/nodes:
    post:
      summary: Spawn a new concept object in space
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Node'
      responses:
        '201':
          description: Node created successfully

  /api/v1/nodes/viewport:
    get:
      summary: Fetch all objects within a specific 3D spatial bounding box
      parameters:
        - name: x_min
          in: query
          required: true
          schema: { type: number }
        - name: x_max
          in: query
          required: true
          schema: { type: number }
        - name: y_min
          in: query
          required: true
          schema: { type: number }
        - name: y_max
          in: query
          required: true
          schema: { type: number }
        - name: z_plane
          in: query
          required: false
          schema: { type: number, default: 0 }
      responses:
        '200':
          description: Array of Nodes and their localized Edges
          
  /api/v1/edges:
    post:
      summary: Forge a logical link between two objects
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Edge'

  /api/v1/graph/expand/{node_id}:
    get:
      summary: Fetch a concept and all related objects up to N degrees of
separation
      parameters:
        - name: depth
          in: query
          schema: { type: integer, default: 1 }