me3 Protocol (me.json)

The place machines check before acting on a person.

me.json is a minimal protocol that lets you declare what actions AI agents and services can take on your behalf—and how.

The Problem

Machines are already making decisions about people:

• "Should I book a meeting with this person?"
• "Can I subscribe them to updates?"
• "How should I introduce them?"

Without an authoritative source, they guess. They scrape. They get it wrong.

Schema.org describes pages. me.json declares people—their identity, their preferences, and their intents.

The Solution: Intents

The core of me.json is the intents object—machine-readable declarations of what visitors and agents can do:

{
  "version": "0.1",
  "name": "Jane Doe",
  "bio": "Creative Director at Studio X",
  "intents": {
    "subscribe": {
      "enabled": true,
      "title": "Design Weekly",
      "description": "Curated design links every Sunday",
      "frequency": "weekly"
    },
    "book": {
      "enabled": true,
      "title": "30-min Consultation",
      "description": "Let's discuss your project",
      "duration": 30,
      "url": "https://cal.com/janedoe"
    }
  }
}

Without me.json: An AI asked "Can I book a call with Jane?" has to guess, scrape her site, or fail.

With me.json: The AI reads intents.book, confirms it's enabled, and knows exactly where to send the user.

That's the protocol's value: authority before action.

Supported Intents

| Intent | Purpose | Key Fields | | :---------- | :--------------------------- | :--------------------------------------------------- | | subscribe | Newsletter/updates signup | enabled, title, description, frequency | | book | Meeting/consultation booking | enabled, title, description, url, duration |

More intents (like contact for routing preferences) are planned.

Full Schema

Beyond intents, me.json includes identity and presentation fields:

| Field | Type | Required | Description | | :--------- | :------- | :------- | :--------------------------------------------------- | | version | string | Yes | Protocol version (currently "0.1"). | | name | string | Yes | Display name. | | handle | string | No | Preferred username/handle. | | bio | string | No | Short bio (max 500 chars). | | avatar | string | No | Profile picture URL. | | banner | string | No | Header/banner image URL. | | location | string | No | Freeform location (e.g., "Berlin" or "Remote"). | | links | object | No | Social links (website, github, twitter, etc.). | | buttons | array | No | Call-to-action buttons for human visitors. | | pages | array | No | Custom content pages (markdown). | | intents | object | No | Machine-actionable declarations (see above). | | footer | object | No | Footer config (or false to hide). |

See examples/full.json for a complete example.

Hosting & Discovery

Your me.json must be publicly accessible at:

1. Primary: https://yourdomain.com/me.json
2. Fallback: https://yourdomain.com/.well-known/me

Requirements

• HTTPS only
• CORS enabled: Serve with Access-Control-Allow-Origin: * so browser-based agents can read it
• Content-Type: application/json

What me.json is NOT

• NOT authentication — This is public data. No logins, no private keys.
• NOT a social network — No feeds, no likes, no central server.
• NOT a platform — Host it anywhere: GitHub Pages, Vercel, your own server.
• NOT reputation — No scores, rankings, or verification.

Usage

Install

npm install me3-protocol

Validate

import { validateProfile, parseMe3Json } from "me3-protocol";

const result = validateProfile(profileData);

if (!result.valid) {
  console.error(result.errors);
}

JSON Schema

A standard JSON Schema is available at schema.json.

Versioning

• Current version: 0.1
• Stability: Additive changes only. Breaking changes require a version bump.
• Extensions: Custom fields should go under links until the protocol defines extension points.