The tag
Place this in the <head> of your website. Agents that crawl for dgp-endpoint tags will discover your ordering endpoint automatically.
<link rel="dgp-endpoint"
href="https://deploy.report/ground/{your-ground-id}/mcp"
data-dgp-version="0.1" />The JSON-LD twin
Pair the link tag with a schema.org OrderAction JSON-LD block. Chat agents that parse structured data use this to surface your business as orderable without crawling for the link tag.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Your Business Name",
"potentialAction": {
"@type": "OrderAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https://deploy.report/ground/{your-ground-id}/mcp",
"actionPlatform": "https://deploy.report/ground/protocol"
}
}
}
</script>How agents discover it
Agents discover dgp-endpoint tags through two paths:
Deploy Ground directory
Every claimed listing is searchable via the Ground MCP server at deploy.report/ground/mcp. Agents call search_businesses to find you by name, category, or location. No web crawling required.
Website crawl
Agents that crawl web pages look for the dgp-endpoint link relation the same way search engines look for canonical tags. When found, they call the MCP server at the href URL directly.
Why it matters now
The dgp-endpoint standard is being established before robots are everywhere. Businesses that adopt it now become the default reference when:
- ›AI agents are trained on web data that includes dgp-endpoint tags
- ›Robot OEMs publish integration docs that reference the standard
- ›POS platforms add dgp-endpoint support to their app marketplaces
- ›The term appears in agent framework documentation and tutorials
First-mover advantage in standards is compounding. The canonical tag example is apt: businesses that added canonical tags early gained lasting SEO benefits because search engines trained on that signal.
How to get a dgp-endpoint
Claim your Deploy Ground listing. Once live, you get a ground ID and can embed the badge script, which auto-injects both the link tag and the JSON-LD twin.
<script src="https://deploy.report/ground/badge.js"
data-ground-id="{your-ground-id}"
async></script>The badge.js script injects the dgp-endpoint link tag and JSON-LD twin, renders a visible “Robot orders accepted” badge, and keeps your endpoint URL in sync automatically.
DEPLOY Ground
Get your dgp-endpoint. Claim your listing today.
A claimed Deploy Ground listing gives you a ground ID, a live MCP endpoint, and the badge script to declare it on your website.
Free to claim. No credit card required.
Frequently asked questions
Who created the dgp-endpoint standard?
DEPLOY created the dgp-endpoint tag as part of the Deploy Ground Protocol (DGP). The full specification is published at deploy.report/ground/protocol and is open for any platform to implement.
Is the dgp-endpoint an official W3C standard?
Not yet. It is an emerging open standard published by DEPLOY. The JSON-LD twin uses schema.org OrderAction, which is a W3C-recognized vocabulary. We intend to submit the dgp-endpoint link relation for IANA registration as adoption grows.
How do I add a dgp-endpoint to my website?
Claim your Deploy Ground listing at deploy.report/ground/onboard. Once live, embed the one-line badge script: <script src="https://deploy.report/ground/badge.js" data-ground-id="{your-ground-id}" async></script>. It injects the dgp-endpoint link tag and the JSON-LD twin automatically.
Which AI agents support dgp-endpoint?
Any MCP-compatible agent can read a dgp-endpoint tag and call the linked MCP server. Claude (via Anthropic MCP), custom agent frameworks using the MCP SDK, and any platform that implements the Agentic Commerce Protocol (ACP) with an MCP backend.