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:
- Verify the peer's DID resolves to a valid OAS record.
- Store the peer endpoint + public key in your
registriestable. - Begin streaming entries via
POST /v1/federate/sync.
Scope
Federation is scoped — you can choose which kinds to share. Use ["*"]
to share everything.