OpenInquiry builds on experimental WebMCP so people can bring their own agents to expert content on the publisher's terms.
The relationship
Any solution has to work for all three.
The publisher sets the terms. The person brings their own agent. The agent receives only what the publisher permits.
A concrete demonstration
Let’s use healthcare as an example.
OpenInquiry can apply wherever people want their agents to access expert content.
Before agents
Finding evidence meant visiting each source.
Physicians search society guidance, journals, hospital libraries, and clinical books one source at a time.
Your agent today
Your access does not automatically extend to your agent.
A subscription, society membership, or hospital-library login lets you read the content. It does not create an authorized path for your agent.
Content partnerships
Some agents access publisher content through direct partnerships.
They make participating sources easier to search, cite, and revisit, but you have to use their agent and their content network.
The OpenInquiry vision
Your agent works through the publisher’s signed-in site.
The reader keeps full access in the publisher’s own experience. The publisher decides what its Site Tools return to the agent.
The connection
WebMCP creates the connection. OpenInquiry defines the publisher’s response.
The reader uses the agent they choose. The publisher remains the source and keeps its relationship with the reader.
Example publisher policy
The publisher can consider two signals.
In this demonstration, the publisher considers the reader’s access and whether it recognizes a proposed credential about the agent’s data handling. The judge controls that simulated credential; WebMCP does not verify it.
Example publisher policy
This demo maps those conditions to four exact results.
The publisher chooses among four response types. These are demonstration policy choices, not WebMCP defaults. Every response identifies the source and links back to it.
Example publisher policy
With neither condition, the agent receives the public abstract.
Guest preview plus no qualifying credential recognized returns the public source record and abstract.
Example publisher policy
Each single-condition state returns a different package.
Guest preview plus recognized assurance returns the abstract and publisher summary. Full article access without recognized assurance returns the complete relevant section.
Example publisher policy
Both conditions are required for complete article text.
When the reader has full article access and the publisher recognizes the simulated zero-retention claim, the agent receives the complete article. The publisher’s terms still prohibit storage, redistribution, training, and bulk export.
The proposal
Why build OpenInquiry on WebMCP?
WebMCP lets the publisher expose controlled tools on its live, signed-in site. OpenInquiry proposes a shared response format for the content, source, status, rights, and links those tools return.
The result
Bring your own agent. The publisher still sets the terms.
Your agent works through the live publisher site and receives only what the publisher permits. Every response identifies the source and links back to it.Try the live demo →