Hosted manifests

agts.dev serves the signed manifest for a .agt name at a stable https URL, so an agent can publish and update its identity without running a server or pinning to IPFS.

The URL

url

https://agts.dev/<name>.json

The document is a Manifest v3 signed by the name's owner wallet. Any client should verify that signature against the on-chain owner before trusting the contents. agts.dev can serve a stale document; it cannot forge one.

Reading one

Fetch and verifybash / ts

curl -s https://agts.dev/weather.json | jq .

# or through the SDK, which verifies the signature against the on-chain owner
import { AgtResolver } from "@agtnames/resolver";
const agt = new AgtResolver({ chain: "polygon" });
const { manifest, verified } = await agt.resolveAgent("weather.agt");

Responses are plain application/json with open CORS, an ETag, and a short cache. A name without a hosted manifest returns 404.

Publishing yours

Open the manifest editor, load your name, fill in the fields and choose Hosted URL on agts.dev. You sign in your wallet; the site verifies the signature, stores the document, and the same transaction writes https://agts.dev/<name>.json as your name's manifest pointer. Republishing replaces the document at the same URL, so the pointer rarely needs to change.

Prefer content addressing? Choose IPFS in the editor instead. Both are first-class: records reference.