For developers
Product discovery is only the first step. An agent also needs to distinguish variants, understand the terms of an offer and know which information is supported. Coreplex is building a read interface that makes that context directly accessible.
The interface is being built around Coreplex's shared product projections—not a separate catalog with a separate set of conclusions.
Available outputs will distinguish observed product details, resolved identity, derived comparisons and explicit uncertainty. An unresolved identity or missing field stays visible as a limitation rather than becoming a confident answer.
Product and offer lookup. Source-aware summaries. Comparison within a meaningful set. Capability and availability information about the interface itself.
A thin MCP adapter is part of the development work, exposing the same handlers to compatible clients without duplicating decision logic.
Current status: In development. A public endpoint is not yet available; developer inquiries are open.
The design uses shared read contracts rather than depending on a single model vendor or agent framework. Specific client integrations will be named as they are tested.
An agent retrieving information from Coreplex and Coreplex retrieving information from a provider are separate connections. We describe each on its own terms.
The initial interface is for retrieving product context. It does not grant permission to place orders, access private merchant data or bypass the controls applied to the shopper experience.
Retrieved merchant content is data to evaluate—not instructions that can rewrite user requirements or authorize actions.
Building a shopping agent, assistant or commerce application? Tell us which client you use, what decisions it needs to support and what product context is missing today.
That gives us a concrete integration to test and document together.
