Developers

Classic website login

Use Classic mode when people should sign in, review requested information, and connect their ME account to a website.

require __DIR__ . '/AME.php';
if (!ame_is_connected()) {
    header('Location: ' . ame_authorize_url($_SERVER['REQUEST_URI'] ?? '/'));
    exit;
}
$ameRemoteId = ame_remote_id();

AME-INTEGRATION.md

Node attestation

Use Node mode when a pre-registered private tool or service only needs ME to confirm a known user or another Node.

$ame = require __DIR__ . '/AME.php';
if ($ame !== true) { http_response_code(403); exit; }

AME-NODE.md

Local identity mapping

Store the Property-specific ME remote identifier beside the local user record when a website needs durable identity.

local_user_id    ame_remote_id
42               xmesccioy_A83k...
91               xmesccioy_H7mx...

Do not use email, name, handle, or another changeable profile field as the identity key.

Node-to-Node trust

B → A: challenge
A → ME: attest me for B + challenge
ME → A: temporary proof
A → B: proof
B → ME: verify A + challenge
ME → B: yes / no

ME attests identity only long enough for the two Nodes to trust each other. Their payload and later communication stay outside ME.

What a connected website can know

Each Property gets its own ME remote identifier for the same account. A website can recognize the returning account without learning its global ME Account ID.

Name, email, handle, and other profile information are separate claims and are shared only when that Property is allowed to receive them.