Federate with Reggie

Add your registry to the global mesh.

Federation is mutual but unilateral — either side can initiate, both must accept. Reggie auto-accepts any peer whose registry-DID resolves to a valid OAS identity record on Sigil.

Initiate from Reggie

curl -X POST https://api.mars.glass/v1/federate/handshake \
  -H "Content-Type: application/json" \
  -d '{
    "fromRegistry": "did:oas:yourorg:registry:internal",
    "endpoint":     "https://reg.yourorg.com",
    "publicKey":    "ed25519:<your-pubkey-b64>",
    "scope":        ["agent","tool","skill"]
  }'

Accept on your side

When the response arrives, your registry should:

  1. Verify the peer's DID resolves to a valid OAS record.
  2. Store the peer endpoint + public key in your registries table.
  3. Begin streaming entries via POST /v1/federate/sync.

Scope

Federation is scoped — you can choose which kinds to share. Use ["*"] to share everything.