GGKP Knowledge Brokerage API
Home
What is GGKP?
Home
What is GGKP?
  1. Home
  • Overview
  • Use Cases
  • Security
  • FAQ
  • Taxonomy
    • Retrieve Master Taxonomy
      GET
    • Retrieve Taxonomy by Term ID
      GET
    • Retrieve Domain-Specific Taxonomy
      GET
  • Search
    • Federated Search
      POST
    • Semantic Search
      POST
    • List Connected Sources
      GET
    • Register New Source
      POST
    • Upload Knowledge Products
      POST
    • List Products by Source
      GET
    • Delete Products
      DELETE
  • Classifier
    • Classify PDF Document
      POST
    • Generate Body and Summary
      POST
  • Bots
    • Generic Bot
      POST
  1. Home

Use Cases

The following deployments illustrate what is achievable with the GGKP Knowledge Brokerage API
across different integration architectures. Each represents a distinct pattern — from large-scale
federated search infrastructure to domain-scoped conversational agents to evidence-synthesis
pipelines — and each is running in production on the same API surface documented in this guide.

1. GGKP AI Search — Federated Search at Scale#

Live at: https://search.ggkp.org
GGKP AI Search is the reference implementation of the Search Federator, deployed as a public
pilot that demonstrates the federated index operating at real-world content volume. The portal
currently indexes over 200,000 knowledge products drawn from across the GGKP partner network
— spanning the Green Finance, Green Industry, and Green Policy Platforms, GEF ISLANDS, GEF FARM,
SPAR6C, and several additional partner repositories — and exposes them through a single query
interface.
Users can search the full corpus in either keyword or semantic mode, apply domain filters, and
receive an AI-generated summary response alongside ranked document results. The platform is
explicitly positioned as a pilot: it validates search quality and semantic relevance at scale
before those capabilities are embedded in individual partner portals.
API capabilities used: Search Federator, Knowledge Assistant, domain filtering.
EndpointRole
POST /search-federator/searchFederated keyword search across all indexed sources
POST /search-federator/semanticAI-powered semantic search with intent understanding
POST /generic/api/genericAI-generated summary response above search results

Keyword Search#

Semantic Search Across the Full Corpus#

The semantic endpoint understands query intent rather than matching keywords — a distinction that
becomes practically significant at 200,000+ products, where relevant documents that do not contain
the exact query terms would be invisible to keyword search alone.

2. GEF ISLANDS & GEF FARM — Semantic Search with a Domain-Scoped Librarian Bot#

GEF ISLANDS: https://www.gefislands.org/gef-learn
GEF FARM: https://www.geffarm.org/gef-farm-knowledge
Both the GEF ISLANDS and GEF FARM programme portals follow the same integration architecture,
adapted to the content scope and user community of each programme. The pattern combines two API
capabilities: semantic search over a programme-specific corpus, and an embedded Knowledge
Assistant — a local librarian bot — whose responses are grounded exclusively in that programme's
indexed knowledge.
GEF ISLANDS supports biodiversity conservation and sustainable land management in small island
developing states. Programme officers and country-level stakeholders use the GEF Learn section to
navigate a specialist corpus where the relevant vocabulary differs meaningfully from general green
economy terminology. The librarian bot allows users to ask questions in plain language and receive
synthesised, cited answers without needing to understand the underlying taxonomy or document
structure.
GEF FARM applies the same dual-capability pattern to food systems, agriculture, and rural
management across GEF-supported countries. Content entering the portal is automatically classified
on ingestion via /classify, with taxonomy scope constrained to the FARM domain, so that search
relevance and assistant grounding remain tightly aligned with the programme's thematic boundaries.
API capabilities used: Search Federator (semantic), Knowledge Assistant (domain-scoped),
Automatic Classifier, Taxonomy Management, Product Management.
EndpointRole
POST /search-federator/semanticProgramme-scoped semantic search
POST /generic/api/genericDomain-scoped librarian bot (system-prompted)
POST /classifyAutomated classification on content ingestion
GET /taxonomy-manage/view-domainname-dataDomain-filtered vocabulary for ISLANDS or FARM
POST /search-federator/upload-productsIndexing classified products into the federated corpus

Semantic Search Scoped to GEF ISLANDS#

Domain-Scoped Knowledge Assistant (Librarian Bot)#

The system parameter is the mechanism that scopes the assistant to its domain. Without it,
the assistant draws on the full GGKP knowledge base; with it, responses are constrained to the
programme corpus and carry the appropriate editorial framing for the platform's users.

Automated Classification on Content Ingestion#

The classifier returns per-term confidence scores and AI-generated reasoning, enabling a
lightweight review workflow before products are committed to the federated index:
{
  "status": "success",
  "data": {
    "sectors": [
      {
        "name": "Agriculture",
        "score": 0.91,
        "reasoning": "Document addresses smallholder farming practices in island agricultural systems"
      }
    ],
    "themes": [
      {
        "name": "Biodiversity",
        "score": 0.94,
        "reasoning": "Central focus on ecosystem preservation and species protection strategies"
      }
    ],
    "regions": [
      {
        "name": "Asia-Pacific",
        "score": 0.89,
        "reasoning": "Case studies drawn from Pacific island nations"
      }
    ]
  },
  "meta": {
    "config": {
      "active_taxonomy": ["Sectors", "Themes", "Regions", "Knowledge"],
      "threshold": 0.80,
      "max_results": 5
    },
    "total_time": 2.31
  }
}

3. Waste Management Policy Support System — Capacity Assessment and Knowledge Recommendations#

Live at: https://wastepolicysupport.org/
The Waste Management Policy Support System (WMPSS) is built around a three-stage workflow that
takes countries from structured self-assessment through gap identification to targeted knowledge
recommendations. Each stage is distinct in its function, and the third depends directly on the
outputs of the first two — making this a genuinely sequential pipeline rather than a set of
independently usable tools.
Stage 1 — Structured Capacity Assessment. Countries complete a secure, structured
questionnaire that captures their current waste management capacity across six components. The
questionnaire is self-administered, meaning that national counterparts report their own situation
directly into the system without requiring external facilitation. The data collected is
country-specific, sensitive in some contexts, and stored securely — access is scoped to the
submitting country and authorised platform administrators.
Stage 2 — Data Analytics and Gap Identification. Once a country's assessment is submitted,
the platform analyses the responses to identify where capacity falls below expected thresholds
across the six components. This produces a structured gap profile: a machine-readable
representation of what needs to improve, at what severity, and in which thematic areas. This
profile is the direct input to Stage 3.
Stage 3 — AI-Powered Knowledge Recommendations. For each identified gap, the platform
queries the GGKP Knowledge Assistant to retrieve a curated set of knowledge products from across
the GGKP network that are relevant to addressing that specific capacity deficit. The assistant
grounds its output in the indexed knowledge base, ensuring that every recommendation is
traceable to a specific document, and surfaces resources that country teams may not have
encountered through general search.
API capabilities used: Knowledge Assistant (/generic/api/generic), Search Federator
(/search-federator/semantic), Taxonomy (Themes — Waste Management, Circular Economy).
EndpointRole in Pipeline
POST /search-federator/semanticRetrieval of domain-relevant knowledge products by gap theme
POST /generic/api/genericGap-specific knowledge recommendation generation

Selecting the Right Integration Pattern#

The three deployments above map onto three recognisably distinct patterns, each suited to
different user needs and content contexts.
PatternWhen to UseCore Endpoints
Federated search portalLarge multi-source corpus; users need cross-boundary discoveryPOST /search-federator/search, POST /search-federator/semantic
Domain-scoped librarian botSpecialist programme with defined knowledge boundaries; users need guidance, not just resultsPOST /search-federator/semantic, POST /generic/api/generic (system-scoped)
Evidence-based recommendation pipelinePolicy or advisory context; recommendations must be traceable to verified sourcesPOST /search-federator/semantic, POST /search-federator/search, POST /generic/api/generic (RAG pattern)
The API's composability — each service can be called independently or in combination — means
hybrid architectures are straightforward to construct. Partners whose integration requirements
do not map cleanly onto one of these patterns are encouraged to contact the GGKP technical team.
Previous
Overview
Next
Security
Built with