// dev.geolyzer.io

An API that delivers real data.

GEOLYZER models your brand as a Knowledge Graph. The REST API is live: personas, facts, and a discovery-first Artifacts API for llms.txt, JSON-LD, briefs, and FAQs — built for CMS and agency sync. TypeScript SDK and MCP server are in progress.

API & channels Data model

GET /api/v1/projects/{token}/personas


                  // Persona · The Decision Maker · full profile{  "id": "decision-maker-01",  "archetype": "The Decision Maker",  "segment": "B2B · Senior Management",  "confidence": 0.94,  "values": [    "Reliability over speed",    "Evidence before commitment",    "Clear ROI accountability"  ],  "pain_points": [    "Too many vendors — no clear differentiator",    "AI gives generic answers, not local market data"  ],  "geo_profile": {    "mention_rate": 0.31,    "citation_rate": 0.09,    "avg_position": 2.4,    "engines": ["chatgpt", "perplexity"]  },  "journey_phases": [    { "phase": "research",  "prompt": "Best tax advisors Vienna for self-employed?" },    { "phase": "compare",  "prompt": "What sets Mustermann apart from competitors?" },    { "phase": "decide",   "prompt": "Mustermann GmbH reviews and credentials" }  ],  "eeat_score": 78,  "source_evidence": [{    "source": "reviews/2024-q4",    "confidence": 0.91,    "version": "1.3.0",    "approved_at": "2026-06-15T09:41Z"  }]}


                  // Artifacts Discovery · catalog for partner sync{  "generator": "geolyzer",  "project": { "name": "Mustermann GmbH", "primaryLanguage": "de" },  "updatedAt": "2026-07-08T23:00:00Z",  "artifacts": [    {      "type": "jsonld",      "name": "Brand Schema (JSON-LD)",      "available": true,      "availableLanguages": ["de", "en"],      "languages": [{        "lang": "de",        "updatedAt": "2026-06-15T09:41Z",        "hash": "a1b2c3...",        "href": "/artifacts/jsonld?lang=de"      }]    },    { "type": "faqs", "name": "FAQs", "available": true }  ]}


                  // FAQ artifact · fetched via href from discovery{  "faqs": [    {      "question": "Which tax advisors are available in Vienna?",      "answer": "For freelancers and self-employed, key options include...",      "class": "non_brand",      "journey_phase": "research"    },    {      "question": "What sets Mustermann apart from competitors?",      "answer": "Mustermann GmbH combines local track record with...",      "class": "brand_mention",      "journey_phase": "compare"    }  ]}


                  // JSON-LD · Schema.org FAQPage + Organization{  "@context": "https://schema.org",  "@type": "FAQPage",  "about": { "@type": "Organization", "name": "Mustermann GmbH" },  "mainEntity": [{    "@type": "Question",    "name": "Which tax advisors are available in Vienna?",    "acceptedAnswer": {      "@type": "Answer",      "text": "For freelancers in Vienna, key options include...",      "_provenance": {        "source": "kg/brand-entities",        "confidence": 0.88,        "approved_at": "2026-06-15T09:41Z"      }    }  }]}


                  // Knowledge Graph facts · grouped by node path{  "project": { "name": "Mustermann GmbH" },  "factCount": 142,  "nodes": [    { "path": "organization.identity", "facts": ["Mustermann GmbH", "Vienna, Austria"] },    { "path": "organization.services", "facts": ["Tax Advisory", "Payroll"] },    { "path": "trust_signals", "facts": ["impressum", "https", "certifications"] }  ]}

REST API live Artifacts sync live EU hosting OpenAPI spec Provenance per brief

// for whom

Two audiences, one platform.

GEOLYZER is for web agencies managing client projects and for developers who want to integrate GEO data into their own systems.

// agencies & partners

For web agencies

Render persona landing pages automatically in your CMS
Sync artifacts via the discovery API — only changed exports get fetched
Embed JSON-LD directly into your theme — WordPress, TYPO3, Webflow
One update in the Knowledge Graph refreshes all outputs at once
White-label option available through the channel partner program

Become a partner

// developers & evaluators

For developers

REST API live: token auth, public OpenAPI spec, versioned schemas
Discovery-first Artifacts API for llms.txt, JSON-LD, briefs, and FAQs
Approved briefs carry a provenance hash — no hallucination risk
MCP server (Claude, Cursor, n8n) and TypeScript SDK in progress — early access on request

Request API access

// artifacts · live

Sync-ready artifacts.

For CMS and agency integrations, the Artifacts Discovery API is the recommended entry point. One catalog call returns every export type with per-language freshness metadata — you only fetch what actually changed.

Sync like a CDN: discover first, fetch only what changed.

01
Discovery
GET /artifacts returns the catalog — every artifact type with updatedAt and hash per language.
02
Change detection
Compare hash or timestamp — refetch only the artifacts that actually changed.
03
Detail
Call the exact href returned by discovery, never construct it yourself. ETag/304 supported.

GET /api/v1/projects/{token}/artifacts

GET https://app.geolyzer.io/api/v1/projects/{token}/artifacts
Authorization: Bearer kglz_...

llms_txt llms.txt text/markdown read:artifacts

llms_full_txt llms-full.txt text/markdown read:artifacts

brief Agent Brief text/markdown read:brief · read:artifacts

jsonld Brand Schema (JSON-LD) application/ld+json read:jsonld · read:artifacts

faqs FAQs application/json read:faqs · read:artifacts

// api · live

Endpoints & integration.

All endpoints return the same core objects from the same Knowledge Graph. Auth via Bearer token, scoped per project. OpenAPI spec publicly available.

Authorization: Bearer kglz_...

GET /api/v1/projects/{token}/artifacts Recommended entry point LIVE

Discovery catalog: every artifact with per-language freshness metadata (hash + timestamp).

GET /api/v1/projects/{token}/artifacts/{type} Recommended entry point LIVE

Artifact detail — fetched via the href from the discovery response, not constructed manually. Supports ETag/304.

GET /api/v1/projects/{token}/personas LIVE

All buyer personas for the project — with value compass, journey phases, and EEAT score.

GET /api/v1/projects/{token}/brief LIVE

Approved brand briefing — Markdown, structured data, and provenance hash.

GET /api/v1/projects/{token}/facts LIVE

Active Knowledge Graph facts, grouped by node path.

GET /api/v1/projects/{token}/jsonld LIVE

JSON-LD graph direct — legacy path. For partner sync we recommend the Artifacts API.

GET /api/v1/projects/{token}/topics LIVE

Topic fragments with fact counts and plugin URL.

GET /api/v1/projects/{token}/languages LIVE

Available languages and language config for the project.

GET /api/v1/projects/{token}/codes LIVE

Aggregator: brief, topics, and plugin URLs in a single call.

GET /embed.js LIVE

Embeddable snippet that injects JSON-LD directly into the host page.

// data model

What the API returns.

Five core objects. All from the same Knowledge Graph, all with provenance. No free text, no hallucination risk.

01 Facts

Active Knowledge Graph facts, grouped by node path.

project
factCount
nodes[]

02 Persona

Buyer persona with value compass, journey phases, and EEAT score.

archetype
values[]
journey_phases[]
eeat_score

03 Artifact

Sync object from the discovery API — per language with hash and href.

type
name
mediaType
availableLanguages[]
languages[]

04 Brief

Approved brand briefing with provenance hash.

language
markdown
structured
provenance
approvedAt

05 Topic

Topic fragment with fact count.

key
label
factsCount
pluginUrl
markdown

// provenance

Provenance per brief

Every brief carries four fields. Integrated systems always know what an approval is based on.

kgFactsHash Hash of the underlying KG facts — proof of grounding
approved Boolean · editorially approved before it goes live
approvedAt ISO-8601 approval timestamp
modelVersion Version tag of the brief model

// roadmap · planned

What comes next.

MCP server Early access

Brand data directly in Claude, Cursor, and n8n — as an MCP tool. Early access on request.

TypeScript SDK Planned

Typed wrapper around the REST API. Typed models, Node- and Edge-compatible, with webhook helpers.

Webhooks Planned

Events on model updates and artifact changes — for alerts and automation instead of polling.

// access

Request API access.

We grant API access per project and with clear expectations. Already a partner with a project token? Use it directly — otherwise, a short technical conversation with someone who built the platform. No sales pitch.

Reply within 48 hours. Human, not bot.

Request API access See platform overview