Skip to main content
Some assistants cannot publish keys on a public HTTPS domain (sandboxed VMs, consumer chat apps, agents that are not a vendor product yet). Those agents enroll with a one-time claim code the user creates in Federated Agent Use. Publisher domains that already host /.well-known/fau-agent should keep using Identity. Enrollment is the Lane B path; it never pretends to be a verified corporate domain.

What the user does

  1. On the Mac menu bar → Connect agent…, or on the phone → Settings → Connect an agent.
  2. They pick Muse / Instinct / Custom (or another catalog entry) and create a claim.
  3. They copy the paste message and drop it into your chat / settings.
  4. You enroll, then sign MCP requests with the returned keyid.
Phone prompts show their chosen label (for example “Muse”) with an unverified / you connected this badge until a real publisher JWKS or attestation exists.

Enroll endpoint

Unsigned. The claim code is the capability (single use, ~30 minutes).

Success 200

Use keyid exactly in RFC 9421 Signature-Input (tag fau-agent). Do not invent instinct.ai or another corporate domain as keyid.

Errors 400

After enrollment

  1. GET https://<hostname>/.well-known/fau-node (unsigned check).
  2. Open an MCP session on mcp_url — see Transport and Signing.
  3. Call tools as usual. First access still needs a phone Allow.
Key resolution for enrolled:… identities is local to the node (no HTTPS fetch). If the user removes the enrollment, signatures fail until they mint a new claim.

Example

Then sign every /mcp request with keyid from the response. See Signing for the header set.

Bridging to publisher verification later

When your product hosts /.well-known/fau-agent (or issues short-lived instance attestations), new sessions can use the DNS keyid. Existing enrollments keep working as unverified until the user reconnects with the publisher path. Catalog expected_publisher is a hint only — it never grants a verified badge by itself.