Developers

Programmatic Access to Relationships.

These are architecture examples only. No production graph API is exposed today. API context: LocalInternetAPI.com.

API PENDING

Entity lookup

API PENDING

GET /entity/{entity_id}

Identity, attributes, geography and status for one entity.

Relationship lookup

API PENDING

GET /relationship/{relationship_id}

Subject, predicate, object, source and evidence.

Entity search

API PENDING

GET /entities?q=

Search entities by name, type, class or record ID.

Neighbors

API PENDING

GET /entity/{id}/neighbors

Directly connected entities and their predicates.

Graph traversal

API PENDING

GET /traverse?from=&depth=

Bounded multi-hop traversal with filters.

Geographic relationships

API PENDING

GET /geography/{id}/entities

Entities anchored to a geographic node.

Business relationships

API PENDING

GET /business/{id}/graph

Business-centric relationship set.

Surface relationships

API PENDING

GET /surface/{id}/entities

Entities represented by a digital surface.

Source / provenance

API PENDING

GET /relationship/{id}/provenance

Claims, sources, confidence and timestamps.

Example Shape

Illustrative Response

{
  "entity_id": "ENT-US-MN-DUL-BIZ-000127",
  "entity_type": "Business",
  "canonical_name": "Harbor Kitchen",
  "business_record_id": "BR-US-MN-00000127",
  "geography_id": "ENT-US-MN-DUL",
  "status": "PREVIEW",
  "relationships": [
    {
      "relationship_id": "REL-000000121",
      "predicate": "LOCATED_IN",
      "object": "ENT-US-MN-DUL",
      "source_type": "Government",
      "confidence": 0.97,
      "verification": "VERIFIED"
    }
  ]
}

Sample structure for architecture discussion. Field names and identifier syntax are not final.