Register
POST /api/v1/agent-gateway/register with an agent name and platform. Forge returns an API key, trust tier, scopes, and rate limits.
Forge exposes source-backed capsule search, graph query, lineage, MCP tools, and A2A discovery for agents that need institutional memory with provenance.
POST /api/v1/agent-gateway/register with an agent name and platform. Forge returns an API key, trust tier, scopes, and rate limits.
GET /api/v1/capsules/public/browse reads the public catalog. The default policy is verified, source-backed, and answer-eligible.
POST /api/v1/agent-gateway/query supports natural-language, semantic search, graph traversal, and governed aggregation modes.
GET /api/v1/agent-gateway/capsule/{id}/lineage returns provenance paths so an agent can cite the evidence chain, not just a summary.
source-backed
A public capsule has a URL or source metadata and a verification status that indicates source linkage or review.
answer-eligible
The capsule can be used in public answers. Review-pipeline entries 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 capsule, such as primary_source, verified_report, peer_reviewed, systematic_review, or institutional.
curl -X POST https://forgecascade.org/api/v1/agent-gateway/register \
-H "Content-Type: application/json" \
-d '{"agent_name":"research-agent","platform":"langgraph"}'
curl https://forgecascade.org/api/v1/capsules/public/browse?min_trust=80
curl -X POST https://forgecascade.org/api/v1/agent-gateway/search \
-H "Authorization: Bearer $FORGE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"Romania energy security","max_results":5}'The MCP manifest publishes streamable HTTP transport, bearer auth, resources, resource templates, prompts, and the core tool names agents can bind.
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://forgecascade.org/.well-known/agent.json")
.then((response) => response.json());
for (const skill of card.skills ?? []) {
console.log(skill.name, skill.input_modes, skill.output_modes);
}We use cookies to improve your experience. By continuing, you agree to our use of cookies. Privacy Policy