geo-query

Geo Knowledge Graph — Querying

Query and explore entities, types, properties, and relations in the Geo knowledge graph via its GraphQL API.

When to apply

Use this skill when the user wants to:

• Look up an entity by ID.
• Search for entities of a given type (optionally scoped to a space).
• Explore what properties and relations an entity has.
• Discover the schema for an unfamiliar entity type before publishing.
• Find type, property, or relation type IDs.

API basics

• Endpoint: https://api-testnet.geobrowser.io/graphql
• Method: POST with Content-Type: application/json
• Auth: none required for reads.
• UUIDs: 32-char hex, no dashes (e.g. 7ed45f2bc48b419e8e4664d5ff680b0d).
• Browser links: https://www.geobrowser.io/space/{spaceId}/{entityId}.

Core concepts (compact)

• Entity: a unique node in the graph (person, place, article, etc.). Has an ID, name, description, types, values, and relations.
• Property: a typed attribute on an entity (text, date, datetime, time, boolean, decimal, integer, float).
• Relation: a typed edge between two entities. Relations are themselves entities — they can have their own properties.
• Type: a category (Person, Article, …). Types define a schema of default properties that every entity of that type inherits.
• Space: an independent community/topic scope. An entity can live in multiple spaces; each has its own perspective.

Full conceptual details: see reference.md.

List query: entities vs entitiesConnection

There are two list queries with the same top-level args (typeId, spaceId, typeIds, spaceIds, filter, first, offset, orderBy) but different shapes. Choose based on result set size:

	entities	entitiesConnection
Return shape	flat array	{ nodes, edges, pageInfo, totalCount }
Pagination	first + offset (capped at offset 1000)	first + cursor (after/before)
Use when	small, bounded lookups; default for <1000 results	totalCount needed, or unbounded result sets