What Is MapleBridge Open?
Most B2B sourcing tools publish a supplier directory, a lead capture form, or a CRM workflow. MapleBridge Open focuses on a different layer: bilateral matching infrastructure.
The repository defines the public contract surface for:
- How buyer demand should be normalized before matching
- How supplier capability should be normalized before matching
- How both sides flow into a shared scoring engine
- Where review, trust, and notifications sit in the workflow
This is not a copy of the live MapleBridge marketplace. It is an interface-first public scaffold — schemas, protocols, and contracts that any team can use to build their own bilateral B2B matching layer.
License: Apache-2.0 · Repository: github.com/jinjihuang88-ui/maplebridge-open
Why A2A? The Bilateral Matching Problem
Bilateral B2B matching is not a single-agent task. It is a coordination problem across at least three layers:
- Buyer-side agent: normalizes demand — product specs, MOQ, budget, destination market, compliance requirements, packaging needs
- Seller-side agent: normalizes supply — capability, export readiness, throughput, category fit, certifications, responsiveness
- Shared match layer: evaluates bilateral fit and moves the workflow forward
Most sourcing tools flatten this into one CRM record or one directory listing. That misses the real asymmetry between what buyers expose and what suppliers expose. A shared match engine only works well if both sides are modeled separately first.
In MapleBridge Open, A2A means agent-to-agent: buyer-side and seller-side agents publish different but compatible state, and the match engine evaluates both through a shared scoring surface.
What the Repository Contains
Intent Schema
Public buyer brief and supplier profile normalization format. JSON schema for demand and supply state.
Agent Protocol
Buyer-agent and seller-agent handoff contract. How agents publish state for matching evaluation.
Match Engine
Public scoring dimensions and explainability boundary. How bilateral fit is evaluated.
Crawler Connectors
Ingestion abstraction for crawler, webhook, and dataset connectors. External signal layer.
Notification Interface
Event contract for introductions, reminders, and review handoffs. Trigger layer for workflow progression.
Why A2A
Framing document explaining why bilateral matching requires agent-to-agent workflow design.
Example: Intent Schema Shape
The public intent schema defines how a buyer brief is normalized before matching. A minimal example:
The full schema, including supplier-side normalization, scoring dimensions, and connector formats, is available in the GitHub repository.
Public vs. Private Boundary
MapleBridge Open publishes the interface layer only. The production MapleBridge system keeps separate:
- Public (in the repo): schema shapes, protocol contracts, scoring dimensions, notification event names, connector abstraction, demo UI boundaries
- Private (in production): live marketplace logic, customer data, production orchestration, trust heuristics, real crawler operations, match thresholds, follow-up flows
This is an intentional open-core boundary — the protocol is reusable; the production runtime is not exposed.
Who This Is For
MapleBridge Open is useful for teams building:
- AI-powered B2B matching systems in any vertical
- Agent-to-agent (A2A) procurement or sourcing workflows
- Bilateral marketplace infrastructure (not just directories)
- LLM-native buyer or seller onboarding agents
- Open-source supply chain or procurement tooling
How It Relates to MapleBridge.io
The live MapleBridge platform connects North America buyers with Chinese manufacturers and exporters through AI-assisted bilateral matching. MapleBridge Open extracts the protocol and framework layer behind that system and publishes it for the broader community.
If you are a buyer looking to source from China, the platform itself handles the full matching workflow. MapleBridge Open is for developers and researchers building matching infrastructure.
Frequently Asked Questions
What does Apache-2.0 allow?
Apache-2.0 is a permissive open-source license. You can use, modify, and distribute the code (including commercially) as long as you include the license and attribution notices. You do not need to open-source derivative works.
Does MapleBridge Open include a working demo?
The repository includes a local demo UI boundary — a reference scope for a demo UI covering buyer brief form, supplier profile form, match explanation panel, review queue placeholder, and notification preview state. It is not a production-ready application.
What is the difference between MapleBridge Open and the MapleBridge production app?
MapleBridge Open publishes the interface and protocol contracts — schema shapes, agent handoff protocols, scoring dimensions. The production app at maplebridge.io/app contains the live marketplace, real buyer and supplier data, production match thresholds, and follow-up flows. These are intentionally kept separate.
How do I contribute to MapleBridge Open?
The repository is open for contributions. See the CONTRIBUTING.md file in the GitHub repository for contribution guidelines. Issues and pull requests are welcome.
Is MapleBridge Open compatible with other A2A frameworks?
MapleBridge Open defines domain-specific contracts for B2B matching. The A2A framing is conceptual — buyer-side and seller-side agents, shared match layer — and is not tied to a specific agent runtime or orchestration framework. The schemas are JSON-based and can be integrated with most LLM agent toolchains.
Get Started with MapleBridge Open
Browse the protocol documentation or view the full repository on GitHub.