/.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
- On the Mac menu bar → Connect agent…, or on the phone → Settings → Connect an agent.
- They pick Muse / Instinct / Custom (or another catalog entry) and create a claim.
- They copy the paste message and drop it into your chat / settings.
- You enroll, then sign MCP requests with the returned
keyid.
Enroll endpoint
Success 200
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
GET https://<hostname>/.well-known/fau-node(unsigned check).- Open an MCP session on
mcp_url— see Transport and Signing. - Call tools as usual. First access still needs a phone Allow.
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
/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.