Verified buyer identity
Submissions and status reads need a verified email, an active grant and the exact consumer client. A typed email is never proof.
Early access
Foundry OMS & MCP
Let buyers' agents ask, quote and request. You approve.
Buyers add the Forge Foundry MCP to their AI client, research the products you publish, and send inquiries, RFQs and order requests. Every one lands in Foundry OMS for your team. Your store keeps checkout and payment.
Foundry OMS · RequestsSample data
- RFQ240 × HX-40Buyer agent · verifiedAwaiting review
- OrderSales order request, 12 linesBuyer agent · verifiedMapping needed
- InquiryFood-grade seal options?Anonymous researchAnswered
- RFPAnnual supply, 4 SKUsBuyer agent · verifiedDraft quote
Received snapshot · immutable
Qty 240 · 2 in. NPT · 316 SS · need-by Dec 12 · ship to verified buyer address
A request is not an order. Checkout and payment stay on your store.
Short answer
Foundry OMS is the review queue for requests that buyers' AI agents submit through the Forge Foundry MCP. Agents can research and request; your team decides; your store or ERP stays the system of record for orders and payment.
How it works
From published catalog to reviewed request.
- 01
Publish
Opt in your business and the products agents may see. Private costs and internal IDs never become public facts.
- 02
Connect
A buyer adds the Forge Foundry MCP to a supported AI client and signs in with a verified email.
- 03
Request
Their agent reads your catalog, asks questions, and submits an inquiry, RFQ, RFP or order request.
- 04
Review
Your team sees an immutable snapshot, responds, and (with Digit) can create a draft quote or requested order.
Forge Foundry MCP
Play the buyer's agent against a demo catalog.
This scripted demo shows the shape of a buyer conversation: what an agent can read, where a missing fact stops it, and how a request becomes something your team reviews.
- Read company facts and the products you publish
- Ask questions and compare specs
- Submit inquiries, RFQs, RFPs and order requests
- Check protected status, with a verified identity
- Receive an eligible link to your own WooCommerce or Shopify checkout
Buyer agent · demo catalog
Scripted assistant · demo catalog · not a live AI
Scripted demo · written answers · nothing leaves this page
Trust by design
Separate doors for buyers and operators.
Separate trust plane
Buyer and operator access use different OAuth audiences and scopes. Research runs under quotas.
Untrusted by default
Agent-supplied text stays data, never instructions. Rules, publication and mappings are checked before any provider call.
Opt-in publication
Per business and per product. Forge is never the merchant of record.
Aggregate-only activity
Foundry MCP activity is aggregate, kept 30 days, and never creates CRM contacts.
Role-gated changes
Publication, routing rules, mappings, pushes and connections need an admin or owner.
ERP flow, starting with Digit Software
With mappings resolved, reviewed RFQs/RFPs can become internal draft quotes, sales-order requests become requested or draft orders, and manufacturing requests become unstarted jobs. Foundry OMS also works with no connector, ecommerce only, Digit only, or both. Other ERPs are future work.
Alongside EDI, not instead of it
Foundry OMS adds an intake channel for agent-driven trade. Mandated X12/EDIFACT connections stay in place, and Forge does not implement EDI maps.
Not yet available: native ACP/UCP checkout adapters, additional ERPs, and automatic store push/import (manual in v1). We will say so here when that changes.
Questions
Foundry OMS & MCP.
What is the Forge Foundry MCP?
A single Model Context Protocol endpoint your customers and prospects add to their own AI client. Through it, their agent can connect to your business, read your company profile and the catalog you publish, ask questions, submit RFQs and RFPs, and submit order requests. Named client compatibility is verified separately. It is separate from the operator Forge MCP your own team uses.
What is Foundry OMS?
The workspace where your team reviews everything a buyer's agent submits: inquiries, RFQs, RFPs, sales-order and manufacturing-order requests. Tabs are Dashboard, Requests, Orders and Catalog. What is discoverable and requestable is a publish decision you make per business and per product.
Is an accepted request an order?
No. A received request stays a request until your team accepts it, and an accepted request is not proof of an ERP order, production start, shipment, invoice or payment. Checkout and payment stay on your WooCommerce or Shopify store.
Does this replace our EDI provider?
No. Foundry OMS is another intake channel for agent-driven trade. It does not implement EDI maps or replace mandated X12/EDIFACT connections.
How do requests reach our ERP?
Digit Software is the first ERP integration: once customer, item, address, price and production mappings are resolved, reviewed RFQs/RFPs can become internal draft quotes, sales-order requests become requested or draft orders, and manufacturing requests become unstarted jobs. Other ERPs are future work, and Foundry OMS also works with no ERP.
How do you stop spam and prompt injection?
Research is quota-bound and may be anonymous. Submissions and protected status reads require a verified buyer identity, an active grant and the exact consumer client. Agent-supplied text is treated as untrusted data, consumer access runs on a separate trust plane from operator access, and research never creates CRM contacts.
When can we use it?
Foundry OMS and the Forge Foundry MCP are in early access, rolling out to existing Forge customers first. Book a demo to join; the same structured catalog Forge builds for AEO is what makes you ready for agent requests.
Next step
Be ready when the buyer is an agent.
Early access is rolling out to Forge customers first. Start with a GEO Report to see how ready your catalog is for agent requests today.