DataRobot now helps the Agentic Useful resource Discovery Specification, making DataRobot Agent Expertise and MCPs simpler for AI shoppers, registries, and builders to search out.

Brokers are solely as helpful because the capabilities they’ll attain.
A coding agent can write code. A workflow agent can name instruments. An enterprise agent can purpose throughout methods. However all of that is determined by the identical fundamental query: when the agent wants a functionality, how does it discover the precise one?
Till now, the reply has largely been handbook. Builders wire in MCP servers, set up expertise, level brokers at docs, and keep lengthy lists of instruments which will or might not be related to the duty at hand. That works for a small variety of hand-picked integrations. It breaks down when each platform, workforce, and group is publishing new agentic assets.
That’s the reason we’re excited to share that DataRobot now helps the Agentic Useful resource Discovery Specification, also referred to as ARD.
DataRobot now publishes an ARD-compatible AI catalog for DataRobot Agent Expertise and MCP Servers, making these expertise and MCPs discoverable from our area by means of the usual .well-known/ai-catalog.json path at https://datarobot.com/.well-known/ai-catalog.json
Why ARD issues
Agentic Useful resource Discovery is an open specification for publishing, discovering, and verifying agentic assets throughout the online. These assets can embrace expertise, MCP servers, APIs, brokers, instruments, workflows, and different capabilities.
The mannequin is easy: suppliers publish a catalog of obtainable assets below their very own area. Discovery companies and AI shoppers can then discover, index, and resolve these assets when an agent wants them.
That issues as a result of the agent ecosystem is transferring from static wiring to dynamic discovery.
As a substitute of asking builders to preload each attainable device and ability into an agent’s context, ARD offers brokers and registries a typical technique to uncover the precise functionality for the duty. The agent can search, choose, and hook up with related assets with out carrying each integration by default.
For enterprises, that discovery layer is particularly necessary. Groups want brokers that may discover helpful capabilities, however additionally they want management over what will get surfaced, the place it comes from, and the way it’s ruled.
What DataRobot is publishing
DataRobot’s ARD catalog at the moment factors to DataRobot Agent Expertise and MCPs.
This contains expertise for:
- Mannequin coaching
- Mannequin deployment
- Predictions and batch scoring
- Characteristic engineering
- Mannequin monitoring
- Mannequin explainability
- Knowledge preparation
- App Framework CI/CD
- Exterior agent monitoring
- Agent Help
These expertise bundle DataRobot platform information into task-scoped context that coding brokers can use straight. They assist brokers perceive DataRobot workflows, SDK patterns, deployment steps, validation checks, and observability practices.
In different phrases, they educate brokers learn how to use DataRobot accurately.
With ARD assist, these expertise usually are not solely out there in repositories and agent environments. They’re additionally revealed in a typical catalog that discovery instruments can crawl, index, and resolve.
From installable expertise and MCPs to discoverable platform context
We’ve got been investing in DataRobot Expertise and MCPs as a result of brokers want greater than documentation. They want operational context.
A human developer can learn docs, infer lacking steps, ask a teammate, and get well when an API name fails. An agent wants the precise context on the proper second. In any other case, it guesses.
Expertise and MCPs cut back that guesswork by giving brokers exact directions for frequent platform workflows. ARD takes the following step by making these assets simpler to search out.
That shift issues for developer expertise. It additionally issues for platform groups.
If you’re constructing brokers on DataRobot, you shouldn’t must manually educate each device the place DataRobot expertise and MCPs stay. If you’re constructing an AI consumer or registry, it’s best to have a typical technique to uncover DataRobot assets. If you’re governing agentic AI inside an enterprise, it’s best to have the ability to determine which catalogs and registries your brokers can use.
ARD offers the ecosystem a path towards that mannequin.
Strive it
What comes subsequent
Agentic discovery continues to be early, and the specification is transferring shortly. That’s precisely why we needed DataRobot to take part now.
The agentic net is not going to be constructed from one market, one vendor catalog, or one hard-coded device record. It’ll want open discovery, clear possession, and assets that brokers can really use.
DataRobot’s position is to make enterprise AI brokers simpler to construct, function, monitor, and govern. Supporting ARD is one other step towards that future: DataRobot platform context that’s not simply out there, however discoverable.
Brokers mustn’t must guess the place the precise functionality lives.
Now, they’ll discover DataRobot.
