Integration Partnerships

Bring Brali knowledge into a product without hiding why it can be trusted.

Build an assistant, agent, learning experience, or internal knowledge workflow on stable Brali identities, explicit evidence states, and versioned data.

Available now

Use the public interfaces

Static Knowledge API v1 for read-only records and manifests.
Browser query for transparent Topic → Protocol → Evidence packets.
Integration kits for common AI development workflows.
Versioned data releases for reproducible downstream use.

Important boundary

MCP is local today

The repository includes a read-only local stdio MCP server. Brali does not currently promise a hosted remote MCP service. A partnership proposal can describe the hosting, update, or service boundary you actually need.

Review the developer contract

A strong integration proposal explains

the users and decisions the integration is meant to support;
which Brali records, datasets, or interfaces it needs;
whether the use is non-commercial, commercial, internal, or public;
how canonical IDs, evidence states, provenance, and updates remain visible;
what is missing from the current static API or local MCP workflow.

Good-fit projects

Evidence-aware assistants, bounded RAG systems, learning and coaching tools, knowledge navigation, dataset enrichment, evaluation harnesses, and localization workflows are all reasonable starting points. The proposal should stay concrete about the user experience and avoid turning unreviewed material into confident advice.