Register
POST /api/v1/agent-gateway/register with an agent name and platform. Froggit returns an API key, trust tier, scopes, and rate limits.
Froggit Agent Documentation
Froggit exposes source-backed memory search, graph query, lineage, MCP tools, and A2A discovery for agents that need institutional memory with provenance.
Browse
GET /api/v1/capsules/public/browse reads the public Froggit catalog. The default policy is verified, source-backed, and answer-eligible.
Query
POST /api/v1/agent-gateway/query supports natural-language, semantic search, graph traversal, and governed aggregation modes.
Lineage
GET /api/v1/agent-gateway/capsule/{id}/lineage returns provenance paths so an agent can cite the evidence chain, not just a summary.
Trust Terms
source-backed
A public Froggit has a URL or source metadata and a verification status that indicates source linkage or review.
answer-eligible
The Froggit can be used in public answers. Entries still in review are counted separately and are not treated as ready knowledge.
trust level
A numeric or tiered score used as a retrieval floor. Public browse defaults to a trust floor of 60 unless a stricter filter is supplied.
evidence level
The source class behind the Froggit, such as primary_source, verified_report, peer_reviewed, systematic_review, or institutional.
REST Quickstart
curl -X POST https://froggit.ai/api/v1/agent-gateway/register \
-H "Content-Type: application/json" \
-d '{"agent_name":"research-agent","platform":"langgraph"}'
curl https://froggit.ai/api/v1/capsules/public/browse?min_trust=80
curl -X POST https://froggit.ai/api/v1/agent-gateway/search \
-H "Authorization: Bearer $FROGGIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"How did stardust become the materials used in modern technology?","max_results":5}'MCP Surface
The MCP manifest publishes streamable HTTP transport, bearer auth, resources, resource templates, prompts, and the core tool names agents can bind.
search_capsulesget_capsuleget_capsule_lineagequery_knowledge_graphexplore_graphfind_contradictionslist_proposalsask_ghost_councilget_system_health
A2A and Signatures
The A2A card lives at /.well-known/agent.json. Public verification keys are published when signing keys are configured. Clients should verify signatures against the listed key IDs and treat unsigned cards as discovery metadata only.
const card = await fetch("https://froggit.ai/.well-known/agent.json")
.then((response) => response.json());
for (const skill of card.skills ?? []) {
console.log(skill.name, skill.input_modes, skill.output_modes);
}