MapleBridge Open Layer

Public Interfaces for Buyer Agent, Seller Agent, and Match Engine

MapleBridge Open is a separate public protocol layer for supplier matching workflows. It explains how buyer intent, supplier capability, match explanation, connector signals, and notification contracts can support bilateral B2B matching while the production app, database, and private ranking logic remain untouched.

View Agent Protocol View Intent Schema Open on GitHub Why A2A

This area exists to define the public contract surface for builders and partners. It does not expose the production MapleBridge app, production prompts, or production buyer and supplier data.

Latest Public Examples

MapleBridge Open now includes concrete sample payloads for skincare packaging, smart home electronics, recycled packaging, and low-MOQ sourcing workflows. Each example separates buyer intent, supplier capability, match explanation, and human-review notes so builders can inspect why a sourcing match is plausible before an introduction happens.

AI product capability page Sample payloads page Buyer intent to match explanation Sample payloads on GitHub Public changelog Suggest a sourcing use case

What Is Public Here

AI Capability

AI Supplier Matching Infrastructure

Explains MapleBridge as a product capability layer: buyer intent parser, supplier fit scoring, MOQ and compliance risk signals, match explanations, human review notes, public payloads, and open protocol boundaries.

Open page
Knowledge Graph

AI Sourcing Knowledge Graph

Explains the citation-ready graph behind MapleBridge: buyer intent, supplier fields, risk signals, match explanation, human review, and machine-readable assets.

Open page
Schema

Intent Schema

Defines the shared language for buyer demand, supplier supply, structured enrichment, fit filters, and audit-friendly fields.

Open page
Protocol

Buyer and Seller Agent Protocol

Defines how separate domain agents publish profiles, request clarifications, hand off work, and send match-ready payloads into a common engine.

Open page
Scoring

Match Engine Framework

Defines weighted fit dimensions, confidence bands, explainability outputs, and the line between public framework and private production thresholds.

Open page
Examples

Sample Payloads

Shows simplified buyer intent, supplier capability, and match explanation payloads for public inspection and AI citation.

Open page
Explanation

Intent to Match Explanation

Explains why keyword overlap is not enough and how MapleBridge separates intent, capability, matched fields, and open questions.

Open page
Connectors

Crawler Connector Layer

Defines a safe abstraction for web, webhook, dataset, and directory connectors without exposing production source lists or anti-abuse logic.

Open page
Notifications

Notification Interface

Defines the event contract for reminder, intro, follow-up, and human-review notifications without exposing the live outbound delivery chain.

Open page
Demo

Local Demo UI

Defines a reference UI boundary for local development, testing, and partner demos, separate from the production MapleBridge app.

Open page
Positioning

Why A2A

Explains why bilateral B2B matching is framed as buyer-agent plus seller-agent coordination through a shared match and review layer.

Open page

What Stays Private

  • Production app workflow and session logic at /app.
  • Production database tables, live buyer and seller records, and real matching decisions.
  • Production prompts, thresholds, suppression rules, private source seeds, and anti-spam logic.
  • Production notification credentials and live follow-up sequences.

Related MapleBridge Pages

For Buyers Resources Verifiable Signals Public Methodology North America China Sourcing FAQ GitHub Repository Apache-2.0 License