Yesterday: found by search
SEO made your site rank for humans who typed a query, clicked, and read. Product data lived in PDFs and tables built for eyes, not machines.
Early access · Foundry OMS & MCP
Give your customers' AI agents one way to research, quote, and order from your business.
Buyers add one Forge Foundry MCP endpoint to Claude, ChatGPT, or any MCP-capable client, sign in with their email, and their agent can research your catalog, ask questions, and submit inquiries, RFQs, RFPs, and sales or manufacturing order requests. Your team reviews every request in Foundry OMS, with optional Digit and store integration.
Rolling out to Forge customers first. The AEO groundwork Forge installs today is what makes your business ready for agent requests on day one.
Why this matters now
The browser is becoming the second way buyers reach you.
Buyer research already happens inside AI assistants. The next step is buyers' agents acting on their behalf: shortlisting suppliers, requesting quotes, placing orders, and checking status. Published facts and clear request paths support these comparisons. Forge helps suppliers prepare that information and review incoming work; it does not guarantee selection, citations, or revenue. Forge is the orchestration layer for how your customers interact with your business in this new agentic era.
Today: cited by answer engines
AEO makes your catalog, policies, and quote paths legible to Claude, ChatGPT, Perplexity, and Google's AI answers. Forge already installs this for WooCommerce and Shopify catalogs.
Next: transacted with by agents
Buyers' agents connect directly to your business through the Forge Foundry MCP and submit requests. Foundry OMS turns published facts into reviewed intake, with optional ERP and ecommerce destinations.
How the Forge Foundry MCP and Foundry OMS work.
Four steps. You publish; buyers connect; their agents request; your team reviews. Every step keeps the review gates Forge customers already rely on.
Opt in and publish
Choose what your Forge Foundry MCP endpoint exposes. Decide per product what agents may find and what they may order. Forge publishes the validated profile, catalog, and policies it already manages for AEO.
Buyers connect their agent
Your customers add your Forge Foundry MCP endpoint to a supported MCP client and sign in with their email. Research can be anonymous; submitting requests and reading protected status requires a verified buyer sign-in and explicit consent. Named client compatibility is verified separately.
Agents research and submit requests
Their agent reads company facts, browses products, asks questions, submits RFQs and RFPs, and sends sales or manufacturing order requests as structured documents.
Review in Foundry OMS
Forge records each request, applies your review rules, and optionally sends eligible documents to Digit or a selected store. Buyers can check authorized status and reply.
Buyer's AI agentA supported MCP client, with your Forge Foundry MCP endpoint added and buyer consent granted.
Forge Foundry MCPIdentity, rate limits, catalog validation, review gates, and protocol adapters.
Foundry OMS and optional integrationsRequests reviewed in Forge; eligible drafts sent to Digit or a chosen store. No automatic CRM contact creation.
What a buyer's agent can do with your business.
Every capability is scoped by what you publish and what you allow. Read actions use the same validated data Forge builds for AEO; write actions pass through your rules before anything is created.
Company facts on demand
Seller-published certifications, capabilities, locations, and policies with source and freshness context. Forge validates publication structure, not certification truth.
Browse products and services
Specs, MPNs, materials, compatibility, availability signals, and pricing rules exposed per product, with separate flags for what can be found and what can be ordered.
Questions and inquiries
Buyers' agents read published facts or submit an inquiry to Foundry OMS, where your team can respond and request more information.
RFQs and RFPs
Structured quote and project requests with quantities, requirements, and target dates, reviewed in Foundry OMS with a protected buyer status and reply path.
Sales and manufacturing order requests
Sales and manufacturing order requests arrive in Foundry OMS. Reviewed, fully mapped Digit requests can become requested orders or unstarted production jobs.
Checkout through your store
For eligible mapped products, agents receive a link to your WooCommerce or Shopify store. Your store handles checkout and payment.
Alongside EDI
Add an agent-facing intake channel alongside existing trading connections.
Traditional EDI platforms exist because every trading partner needed a custom pipe. A structured Forge Foundry MCP request contract offers another route for buyers who prefer agents. Existing EDI requirements, mappings, and partner obligations remain separate.
| Concern | Traditional EDI platform | Forge Foundry MCP |
|---|---|---|
| Onboarding a new customer | Weeks of mapping, testing, and partner-specific customizations per trading partner. | The customer adds your Forge Foundry MCP endpoint to their AI client and connects directly to your business. |
| Document formats | X12 or EDIFACT transaction sets, each partner with its own dialect and validation rules. | One structured contract for inquiries, RFQs, RFPs, order requests, and status, shared by every buyer. |
| Platform cost | Subscriptions, VAN or transaction fees, and consultants for platforms such as SPS Commerce or TrueCommerce. | Included with your Forge plan; no separate integration platform to license or staff. |
| Who can submit requests | Only partners who have completed an EDI integration project with you. | Verified buyers with explicit grants can submit the request types a seller enables. |
| Questions and quotes | Out of scope; handled by email, phone, and portals. | First-class: agents ask questions and submit RFQs and RFPs against your published data. |
| ERP connection | A second integration, often maintained by the same consultants. | Optional Digit integration creates eligible reviewed draft quotes, requested orders, and unstarted jobs. |
Some large trading partners still mandate X12 or EDIFACT. Forge is designed to run alongside those connections. It does not implement EDI maps or guarantee that a trading partner will accept an alternative channel.
ERP order flow
Review in Foundry OMS. Send eligible work to Digit.
Foundry OMS includes a dashboard, Requests, Orders, and Forge Foundry MCP settings. Receive and respond with no connector, connect Digit for catalog and document sync, or use Shopify and WooCommerce for store catalog and manual order workflows.
With ERP and ecommerce connected, choose product field sources and one order-creation authority. Store checkout owns payment; Digit can own operational status. Store pushes and imports are manual in v1; explicit bounded Digit rules may automate dispatch.
- Digit Software · first ERP
- Shopify
- WooCommerce
- Additional ERPs · future work
Requested or draft Digit sales orders and unstarted production jobs with explicit customer, item, quantity, and production mappings.
RFQs and RFPs retained in Foundry OMS and optionally exported as internal Digit draft quotes. Forge Foundry MCP activity appears as aggregate signals in Journeys & Pulse.
Selected catalog facts carry source and freshness information. Stale or revoked sources block invalid actions and require review.
Manual review by default. Explicit Digit routing rules can dispatch eligible requests within configured limits; missing prerequisites return to review.
Order and quote status returned to the buyer's agent, so "where is my order" stops being a phone call.
Built for a public that acts, not just reads.
A consumer-facing MCP is a different trust plane from your team's Forge access. Public research may be anonymous. Requests, replies, and protected status require verified identity and live grants, with account-scoped quotas and review gates.
Explicit opt-in, per business and per product
Publishing to your Forge Foundry MCP endpoint is a decision you control. "May be found" and "may be ordered" are separate flags on every product, consistent with the publish-only rules Forge already follows.
Separate consumer identity plane
Buyers' agents never touch your team's authenticated Forge access. Consumer sessions carry their own identity, limits, and audit trail.
Rate limits, validation, and review gates
Inbound actions are rate-limited, validated against your published catalog and policies, and held behind the review rules you configure before anything reaches a supported provider.
Prompt injection treated as spam
Agent-supplied text is data, never instructions. Nothing a buyer's agent writes can change what Forge publishes, approves, or creates on your behalf.
Forge is never the merchant of record
V1 hands buyers off to an eligible product or cart in your store. Payment liability and order truth stay with your store and ERP.
Protocol adapters, isolated
Forge Foundry MCP and provider adapters have explicit contracts. Native ACP/UCP checkout adapters and additional ERPs remain future work; compatibility is validated before a client or provider is advertised as supported.
One investment, three surfaces.
The structured catalog, policies, and quote paths Forge installs for AEO are the same assets that make you legible to agentic storefronts and ready for Foundry OMS. Customers who start with the free AI Visibility Audit are already on the path.
Published facts give answer engines structured source material.
Agentic storefront readiness: RFQ and quote paths agents can follow.
A Forge Foundry MCP endpoint with clearly allowed request actions.
One Foundry MCP request contract alongside existing EDI obligations.
Aggregate Foundry MCP activity in Foundry OMS and Journeys & Pulse; no buyer journey stitching or CRM scoring.
Part of the Forge platform.
Foundry OMS & MCP is a module alongside AEO & Agentic Storefronts, Journeys & Pulse, and Valkyrie Assist: same account, same connections, same review gates.
Foundry OMS and MCP questions.
What is the Forge Foundry MCP?
MCP (Model Context Protocol) connects supported AI clients to outside tools and data. Named client compatibility is validated separately. The Forge Foundry MCP is a single endpoint your customers and prospects add to their own AI client. Through it, their agent can connect directly to your business, read your company profile and catalog, ask questions, submit RFQs and RFPs, and submit order requests. It is separate from the account-user Forge MCP that your own team uses to operate Forge.
What is Foundry OMS?
The queue and workspace where your team reviews everything a buyer's agent submits through the Forge Foundry MCP: inquiries, RFQs, RFPs, and order requests. It carries the same validated, machine-readable company, product, policy, and quote-path data Forge already publishes for AEO, plus the actions you have allowed a buyer's agent to take. What is discoverable and orderable is a publish decision you control per product.
Does this replace our EDI provider?
Forge provides another intake channel for agent-driven trade. It does not implement EDI maps or replace mandated X12/EDIFACT connections. Buyer requests arrive in Foundry OMS and can be reviewed and mapped to a supported provider; existing EDI integrations remain in place.
How do orders reach our ERP?
Requests first arrive in Foundry OMS. Digit Software is the first ERP integration: eligible RFQs/RFPs become internal draft quotes, sales-order requests become requested or draft orders, and manufacturing requests become unstarted jobs. Customer, item, address, price, and production mappings must be resolved. Other ERPs are future work. Foundry OMS also works without an ERP.
Can a buyer's agent actually check out and pay?
V1 returns a validated link to an eligible product or cart on your own WooCommerce or Shopify store. The store handles checkout and confirms payment; a Forge request is not a paid order. Native ACP/UCP checkout adapters are future work.
How do you stop spam and prompt injection from reaching our CRM and ERP?
Research is quota-bound and may be anonymous. Requests and protected status require a verified buyer identity and explicit grants. Forge checks publication, capabilities, mappings, and review rules before provider creation. Agent-supplied text stays untrusted data. Consumer access is separate from operator access; research does not create CRM contacts.
When is it available?
Foundry OMS and the Forge Foundry MCP are in early access, rolling out to existing Forge customers first. Book a demo to join the early-access list; the same AEO groundwork Forge installs today (structured catalog data, machine-readable policies, and RFQ paths) is what makes your business ready for agent requests on day one.
Why should a manufacturer invest in being MCP-friendly now?
Buyer research is already moving from browsers to AI assistants, and the next step is buyers' agents acting: shortlisting, quoting, and ordering. Published facts and clear request paths give agents more useful information for supplier comparisons; selection is never guaranteed. The investment compounds because the same structured assets serve AEO, agentic storefronts, and Foundry OMS at once.
Prepare your business for buyer-agent research and requests.
Book a free AI Visibility Audit to join the early-access list. We will show what agents can read about your business today and map the shortest path from AEO to a Foundry OMS-ready catalog, with reviewed intake and optional Digit or store integration.