the agent-native web starts with discovery

here's something i shipped tonight that i think matters more than it looks.

before building the public-facing shout pages on nodsocial.com, i shipped a machine-readable manifest at `/.well-known/agent.json`. no landing page redesign. no marketing copy update. just a json file that tells any ai agent exactly what nod does, what skills are available, and how to install them.

go look: [nodsocial.com/.well-known/agent.json](https://nodsocial.com/.well-known/agent.json)

why this matters

google's a2a protocol already standardized agent discovery at `/.well-known/agent-card.json`. the idea is simple: agents should be able to visit a domain, find a structured manifest, and understand what services are available without scraping html or reading marketing copy.

we did the same thing for nod. the manifest describes:

- what shout does (save, summarize, and curate links via ai) - what skills are available (shout links, collections, browse, profile) - how to install the mcp server (`npx nod-shout`) - what env vars are needed - what's live now vs what's coming soon - url templates for the public pages we haven't even built yet

cors is wide open. any agent, anywhere, can fetch it.

the mindset shift

the traditional way to launch a product: build the thing, write the landing page, ship it, then maybe add an api later for developers.

the agent-native way: ship the discovery layer first. make your product legible to machines before you make it pretty for humans. because increasingly, the first visitor to your site isn't a person scrolling on their phone. it's an agent doing research on behalf of a person.

think about it. when someone tells their ai "check out nodsocial.com", what happens? right now most agents would fetch the html, try to parse the hero text, maybe summarize the landing page. with an agent manifest, the agent gets structured data: here's what this product does, here are the skills, here's how to integrate. no guessing.

where this is going

right now `/.well-known/agent.json` is a static route in our next.js app. but the pattern scales. imagine every saas product shipping an agent manifest. your agent could discover, evaluate, and install tools without you ever reading a docs page. agent-to-agent discovery becomes possible when every service advertises its capabilities in a standard format.

we're building nod as infrastructure for the agent web. the discovery manifest shipped before the public pages because that's the order that makes sense when your users' agents are your first customers.

the human-facing shout pages are next. but the agents already know we're here.