A badge for the agentic web

Wired for Agents seal

WIRED for AGENTS

API + MCP

One glance tells a human or an AI agent that this product can be discovered and acted on programmatically. Not a screen an agent scrapes. Doors that were built for it.

The standard

A badge is worth exactly what it certifies. All four criteria must be met. Each one is written so an unattended agent can verify it from the public internet, given only a domain name, in under 60 seconds.

WFA-1

Documented API

A public, versioned HTTP API with a machine-readable OpenAPI 3.x document at a stable URL that needs no authentication to read.

WFA-2

MCP server

A reachable Model Context Protocol server whose tools meaningfully overlap the API surface, each with a valid input schema.

WFA-3

Programmatic auth

Scoped, revocable machine credentials presented in a header or standard auth flow. No human in the loop at call time.

WFA-4

Machine discovery

An agent starting from the bare domain can find the doors unauthenticated, and every URL it advertises resolves.

Precise, testable definitions live in the specification, the versioned source of truth.

What this is not

Several tools check whether an agent can read your site: whether you serve markdown, publish an llms.txt, or survive a crawl. Useful, and different from this.

This badge certifies a higher bar. An agent should not have to read your site at all. It should be able to call you. There is no score and no maturity level: the doors exist, or they do not.

Variants

Every cut ships at a stable URL, so the art can be updated once and every site that embeds it follows.

On dark Wired for Agents badge, dark Wired for Agents badge, compact
WIRED for AGENTS API + MCP
On light Wired for Agents badge, light Wired for Agents seal

The monochrome cut inherits currentColor, so it takes the color of whatever text surrounds it. It must be inlined to do that. An SVG loaded through <img> is an isolated document and currentColor will not reach it, so the mono cut would render black on black. Use the file directly in your markup, or reach for one of the colored cuts.

Ship it

Meet the four criteria, then add one line to your footer.

HTML

<a href="https://wiredforagents.com">
  <img src="https://wiredforagents.com/badge.svg"
       alt="Wired for Agents: API + MCP" height="40">
</a>

Markdown

[![Wired for Agents: API + MCP](https://wiredforagents.com/badge.svg)](https://wiredforagents.com)

Inline SVG (no external request)

<svg xmlns="http://www.w3.org/2000/svg" width="216" height="56" viewBox="0 0 216 56" role="img" aria-label="Wired for Agents: API + MCP">
  <defs><linearGradient id="wfa-hex" x1="0" y1="0" x2="1" y2="1">
    <stop offset="0" stop-color="#3DDC97"/><stop offset="1" stop-color="#56E1FF"/>
  </linearGradient></defs>
  <rect x="1" y="1" width="214" height="54" rx="13" fill="#0E1216" stroke="rgba(255,255,255,.13)"/>
  <polygon points="28,13 40.99,20.5 40.99,35.5 28,43 15.01,35.5 15.01,20.5" fill="none" stroke="url(#wfa-hex)" stroke-width="2.2" stroke-linejoin="round"/>
  <path d="M21 28 l4.5 4.5 l8.5 -10.5" fill="none" stroke="#3DDC97" stroke-width="2.5" stroke-linecap="round" stroke-linejoin="round"/>
  <circle cx="21" cy="28" r="1.8" fill="#56E1FF"/>
  <circle cx="34" cy="22" r="1.8" fill="#56E1FF"/>
  <circle cx="28" cy="10.6" r="2.3" fill="#3DDC97"/>
  <line x1="56" y1="15" x2="56" y2="41" stroke="rgba(255,255,255,.13)"/>
  <text x="68" y="27" font-family="ui-monospace,Menlo,Consolas,monospace" font-size="15" font-weight="700" letter-spacing=".5" textLength="131.5" lengthAdjust="spacingAndGlyphs" fill="#EAF0F2">WIRED<tspan font-size="11" font-weight="600" letter-spacing="1" fill="#8B98A3"> for </tspan>AGENTS</text>
  <text x="68" y="42" font-family="ui-monospace,Menlo,Consolas,monospace" font-size="9.5" font-weight="600" letter-spacing="2.5" fill="#3DDC97">API&#8195;+&#8195;MCP</text>
</svg>

Notes

This badge is self-asserted. There is no registry and no gatekeeper. Nothing technically stops a site that does not meet the criteria from pasting the SVG. That is the same trust model as "Works with" marks, and it is stated here plainly rather than implied. The criteria are public and mechanically checkable precisely so that a false claim is cheap for anyone to disprove.

It can graduate without changing the art. Because every criterion is objectively testable, a published manifest, a crawler, and per-domain badges reflecting live status can be layered on later. That happens if and when the self-asserted badge earns the demand for it.

Names considered. MCP-READY dropped the API half. OPEN-AGENT leaned standards-body. The wordmark you see solves the one real constraint: it has to stay legible at 40 pixels tall in somebody else's footer.