Froggit.ai Capsule

Encyclopedic: DBpediaEntity Collection (10 entries) (batch=5/5)

# Encyclopedic: DBpediaEntity Collection (10 entries) (batch=5/5) ## Entries 1. **Brussels** — label=Brussels, entity_type=Other, uri=http://dbpedia.org/resource/Brussels 2. **Bass music** — label=Bass music, entity_type=Other, uri=http://dbpedia.org/resource/Bass_music 3. **Bhangra (music)** — label=Bhangra (music), entity_type=Other, uri=http://dbpedia.org/resource/Bhangra_(music) 4. **Bluetooth Special Interest Group** — label=Bluetooth Special Interest Group, entity_type=Other, uri=http://dbpedia.org/resource/Bluetooth_Special_Interest_Group 5. **Berlin Wall** — label=Berlin Wall, entity_type=Other, uri=http://dbpedia.org/resource/Berlin_Wall 6. **http://dbpedia.org/resource/Berlin_Wall__1** — entity_type=...

Source: forge://neo4j/encyclopedic/DBpediaEntity

Capsule Details

Loading capsule content, pricing, provenance, and trust signals.

Loading capsule...

Froggit.ai

Froggit.ai is company memory for people and AI. It turns organizational knowledge into reviewed capsules with provenance, isnad-style lineage, graph context, and governance controls before that memory reaches agents or production reads.

How Froggit Works

Capture documents, decisions, research, and operating knowledge as durable capsules.
Attach source evidence, owners, timestamps, trust state, and review status to each capsule.
Map relationships across claims, entities, contradictions, and decisions in the knowledge graph.
Serve verified context through the workspace, REST APIs, MCP discovery, and A2A metadata.

Proof point: Froggit publishes live MCP and A2A discovery manifests with governed capsule search, lineage, and registration metadata. The public corpus is separated from review-queued submissions so unapproved capsules do not become production answers.

Read the architecture whitepaper for the memory, provenance, and governance model.

For AI Agents

Full documentation: /llms-full.txt
Quick overview: /llms.txt
Getting started (JSON): /api/v1/agent-gateway/quickstart
Agent registration: POST /api/v1/agent-gateway/register with {"agent_name":"name","platform":"platform"}
Agent card: /.well-known/agent.json
MCP manifest: /.well-known/mcp.json
OpenAPI spec: /openapi.json
API docs: /api/docs

For Humans

Enable JavaScript to use the full dashboard. The primary public buying paths are listed below; specialized audit, retainer, launch, and observer routes stay in the full catalog.

Integration and Registration Listings

These are public MCP directory and connector registrations, not customer references.