Integration partnerships
Use Brali through the static API, local MCP server, versioned datasets, or a bounded retrieval workflow.
Build with Brali
Choose a partnership path with clear evidence and licensing boundaries.
Brali supports product integrations, transparent research, localization, and commercial data use. Start with the path that matches what you want to build.
Partnership paths
Research collaborations
Work on evidence review, ontology, retrieval evaluation, or a clearly scoped knowledge question.
Commercial licensing
Discuss paid product use, redistribution, localization, custom collections, or commercial AI delivery.
Contribute without a partnership
You do not need a partnership to improve the public library. You can propose your own practice, protocol, or a problem Brali should cover. Use the structured GitHub forms so each contribution enters the right review path.
- Propose your own knowledge or protocol.
- Suggest a source for evidence screening.
- Report a content or data correction.
- Propose a taxonomy change.
See how agent discoveries and community proposals move through review to publication →
One boundary across every path
Machine-readable access does not erase evidence state, source provenance, canonical identity, or licensing terms. Partnership proposals should explain how those fields remain visible to downstream users.