https://github.com/jinjihuang88-ui/maplebridge-open
Public API docs for MapleBridge, a North America to China B2B supplier matching platform.
https://github.com/jinjihuang88-ui/maplebridge-open
ai b2b china-sourcing llm openapi small-commodity supply-chain trade-matching webhook yiwu
Last synced: 2 months ago
JSON representation
Public API docs for MapleBridge, a North America to China B2B supplier matching platform.
- Host: GitHub
- URL: https://github.com/jinjihuang88-ui/maplebridge-open
- Owner: jinjihuang88-ui
- License: apache-2.0
- Created: 2026-03-15T02:27:38.000Z (4 months ago)
- Default Branch: main
- Last Pushed: 2026-04-11T15:26:48.000Z (3 months ago)
- Last Synced: 2026-04-11T17:22:51.045Z (3 months ago)
- Topics: ai, b2b, china-sourcing, llm, openapi, small-commodity, supply-chain, trade-matching, webhook, yiwu
- Homepage: https://maplebridge.io
- Size: 35.2 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Security: docs/security-boundary.md
Awesome Lists containing this project
- awesome-canada-china-trade - MapleBridge Open - Open examples for buyer intent, supplier capability, and AI-assisted sourcing handoffs. (AI Sourcing Tools)
README
# MapleBridge Open
[](LICENSE)
[](https://maplebridge.io)
[](https://maplebridge.io/open/)
[](https://github.com/jinjihuang88-ui/maplebridge-open)
MapleBridge Open is a public protocol and example repo for AI-assisted China sourcing. It shows how a buyer brief can become structured buyer intent, how supplier capability can be represented, and how a match can be explained before a human introduction happens.
The practical use case is narrow on purpose: North American buyers looking for verified Chinese manufacturers, small-MOQ supplier options, OEM/ODM/private-label partners, and clearer alternatives to search-first sourcing workflows.
It is not the production marketplace code. It is the open contract surface: buyer intent, supplier capability, matching signals, connector boundaries, and review handoffs.
## Why This Exists
Most sourcing failures do not start with a lack of suppliers. They start with an unclear brief.
MapleBridge Open makes the brief and matching logic visible enough for builders, buyers, partners, and AI agents to reason about it:
- What does the buyer actually need?
- What can the supplier actually support?
- Does MOQ, compliance, export-market fit, and packaging fit line up?
- What should be reviewed by a human before an introduction?
## What You Can Reuse
- JSON examples for buyer intent and supplier capability.
- A small local matching demo that runs without production access.
- Public match explanation fields for auditability.
- Connector and notification boundaries for partner integrations.
- A clean public/private boundary for open-core or agent workflow projects.
## Who This Is For
- Builders working on AI agents for sourcing, procurement, B2B marketplaces, or supplier discovery.
- Buyers who want to understand how MapleBridge structures a sourcing brief before supplier search starts.
- Suppliers and partners who want a clean integration boundary without access to private production systems.
- Researchers comparing agent-to-agent workflows for bilateral matching.
## What It Shows
Most sourcing tools begin with supplier search. MapleBridge begins with the brief.
This repository shows a public version of that workflow:
1. A buyer agent normalizes the buyer's demand.
2. A supplier agent normalizes supplier capability.
3. A match layer compares category, MOQ, compliance, market fit, and review risk.
4. A human review layer decides whether an introduction should happen.
## Quick Demo
Run the local example without touching MapleBridge production systems:
```bash
npm install
npm run demo
```
Expected output:
```text
Buyer intent: Low-MOQ insulated bottle order for Canada
Best supplier: Shenzhen drinkware OEM with FDA/LFGB experience
Match score: 0.91
Why it matched: category fit, MOQ fit, compliance fit, North America export fit
Review state: human_review_recommended
```
## Repository Map
| Path | Purpose |
| --- | --- |
| `schemas/intent.schema.json` | Public JSON Schema for normalized buyer and supplier intents |
| `protocols/agent-protocol.md` | Buyer-agent and seller-agent handoff contract |
| `frameworks/match-engine.md` | Public matching dimensions and explainability boundary |
| `connectors/crawler-connectors.md` | Connector abstraction for external supply and demand signals |
| `notifications/notification-interface.md` | Event model for introductions, reminders, and review handoffs |
| `examples/` | Concrete buyer, supplier, and match examples |
| `demo/run-local-match.js` | Small local demo that makes the workflow visible |
| `.github/ISSUE_TEMPLATE/` | Small contribution templates for examples, schema, and docs |
| `docs/promotion-playbook.md` | Non-spam launch and visibility playbook |
| `docs/share-kit.md` | Short platform-specific copy for compliant sharing |
| `docs/github-visibility-plan.md` | GitHub discovery, issue cleanup, and outreach sequence |
| `llms.txt` | AI crawler summary for LLM and answer-engine discovery |
## Example Objects
Buyer intent:
```json
{
"intent_id": "buyer-low-moq-bottle-ca",
"role": "buyer",
"language": "en",
"product_category": "drinkware",
"summary": "Low-MOQ insulated bottle order for Canada",
"country": "Canada",
"moq": { "value": 500, "unit": "units" },
"compliance": ["BPA-free", "FDA food contact"],
"fit_constraints": ["custom logo", "retail packaging", "ship to Toronto"],
"confidence": 0.86,
"review_state": "needs_review"
}
```
Supplier capability:
```json
{
"intent_id": "supplier-shenzhen-drinkware-oem",
"role": "supplier",
"language": "en",
"product_category": "drinkware",
"summary": "Shenzhen drinkware OEM with FDA/LFGB experience",
"country": "China",
"moq": { "value": 300, "unit": "units" },
"compliance": ["BPA-free", "FDA food contact", "LFGB"],
"channels": ["OEM", "private label", "North America export"],
"fit_constraints": ["custom logo", "retail packaging"],
"confidence": 0.9,
"review_state": "machine_ready"
}
```
## Public Boundary
Open in this repository:
- protocol shape
- schema examples
- matching dimensions
- connector boundary
- review handoff notes
- local demo data
Not open in this repository:
- production application code
- customer data
- live crawler sources
- private ranking thresholds
- production credentials
- private supplier or buyer records
## Useful Links
- Live website: [maplebridge.io](https://maplebridge.io)
- Public open docs: [maplebridge.io/open/](https://maplebridge.io/open/)
- Local demo guide: [demo/README.md](demo/README.md)
- Share kit: [docs/share-kit.md](docs/share-kit.md)
- Why A2A matters: [docs/why-a2a.md](docs/why-a2a.md)
- Security boundary: [docs/security-boundary.md](docs/security-boundary.md)
- Roadmap: [ROADMAP.md](ROADMAP.md)
- Contributing: [CONTRIBUTING.md](CONTRIBUTING.md)
- GitHub visibility plan: [docs/github-visibility-plan.md](docs/github-visibility-plan.md)
## How To Help
Useful contributions are narrow and practical:
- Add better sample buyer intents for real sourcing categories.
- Add supplier capability examples for OEM, ODM, private label, or low-MOQ cases.
- Improve schema naming and compatibility notes.
- Add connector examples that do not expose production data.
- Improve match explanations so humans can audit why a recommendation happened.
Good first issues:
- [Add one buyer intent example for a real sourcing category](https://github.com/jinjihuang88-ui/maplebridge-open/issues/11)
- [Add supplier capability examples for OEM and low-MOQ cases](https://github.com/jinjihuang88-ui/maplebridge-open/issues/12)
If this is useful, star the repo or open a small issue with the sourcing workflow you want represented.