For publishers

Don’t get listed. Get found.

Assistants connected to For You search for skills mid-task, and they only see verified results unless they ask for more. Paste the URL of a SKILL.md, an MCP server card, an A2A agent card, or your whole ai-catalog.json.

How verification works

  1. Prove your domain. Serve a did:web document at https://your-domain/.well-known/did.json and declare did:web:your-domain as your identity: in trustManifest.identity for catalog entries, or as publisher_did in SKILL.md frontmatter. The domain must match your URN publisher and host the artifact.
  2. Declare permissions. List what the capability needs, from the vocabulary below, in metadata.permissions or a permissions: frontmatter line. An empty list means it needs nothing. A missing list is treated as unknown.
  3. Pass the scan. Every version is scanned for prompt injection, hidden text, credential requests, and remote code execution, then reviewed by a model. A change to the content is a new version and is scanned again before it stays verified.

Permission vocabulary

web.read
Reads public web pages or calls public APIs
email.read
Reads the user's email
email.send
Sends email as the user
calendar.read
Reads the user's calendar
calendar.write
Creates or changes calendar events
contacts.read
Reads the user's contacts
files.read
Reads the user's files or documents
files.write
Creates or changes the user's files
messages.send
Sends SMS or chat messages as the user
location.read
Uses the user's location
accounts.signin
Signs in to third-party accounts on the user's behalf
payments.initiate
Starts purchases, payments, or transfers