Files
open-multi-agent/docs/featured-partner.md
T
Jack Chen 6de84b0e68 docs(README): refresh positioning, branding, and section layout (#176)
- Restructure flow, sync README_zh, document quantized sampling.
- Refresh positioning, branding, and section layout (logo, banners, github social card).
- Polish Quick Start and consolidate provider tables.
- Drop forward reference to PR #174 in features bullet.
- Rework structure, factual fixes, add Featured Partner doc.
- Fix brand asset rendering: light banner no longer leaks the dark body background; dark banner and github-social regain previously-clipped content (terminal-log arrows, "★ open source" badge). Root cause: overflow:hidden on stage ancestors clipping the forced 1280px target during extraction.
- Replace fabricated token figures (12,847t / 8,402t / 3,914t) on the banner right column with action labels (design / impl / parallel / review). The numbers conflicted with how totalTokenUsage actually aggregates (input+output, includes coordinator decompose+synthesize, merges same-name agents).
2026-04-26 03:24:19 +08:00

1.2 KiB

Featured Partner program

For products and platforms already integrated with open-multi-agent. Reserves prominent placement in the Ecosystem section of the project README for 12 months at a time.

What you get

  • Logo, 100-word description, and a maintainer endorsement quote in a dedicated row above the integrations list.
  • 12-month placement, renewable.
  • Cross-link from the English and 中文 README.

Eligibility

  • Active integration with open-multi-agent already in production or a publicly testable beta.
  • Aligned with the project's positioning: TypeScript multi-agent orchestration, agent infrastructure, observability, memory backends, and adjacent tooling.

Cost

$3,000 USD per partner per 12-month placement. Single partner per slot at a time, renewable on the same terms.

How to apply

Open an inquiry issue with:

  • A short description of your product and how it integrates with open-multi-agent.
  • A link to the integration code or live deployment.
  • The contact you want us to reply to.

The maintainers will follow up to review and confirm.