Seal Integration Details

General
1

Hi team I’m building Cortex (sovereign memory for AI agents on Sui + Walrus + Seal), live on mainnet. I’m integrating Seal for threshold encryption and
want to use the official mainnet committee key server:

  • Committee object ID: 0x686098f1439237fff9f36b99c7329683c22979d2005c2465cb891acb012a7595
  • Aggregator: seal-aggregator-mainnet(dot)mystenlabs(dot)com (5-of-8)
  • My cortex package (mainnet): 0x643fbc9d6182493e533a85a49a584a1c08471e2d28e6de842eb183c8d2ed9438

I’ve already validated the full flow against this committee with the @mysten/seal SDK: encrypt works, my SessionKey + seal_approve PTB (against my
cortex::private module) is accepted by the aggregator, and the request uses the x-api-key header. The only thing failing is auth the aggregator returns
Unauthorized, so I need a valid mainnet Seal API key for that committee aggregator.

Could you point me to how to get one and confirm x-api-key is the correct header and any rate limits I should know about?
Happy to share more about the integration.

Thanks!

2

I’d appreciate a prompt response as this is for my Sui Overflow submission

3

Screenshot 2026-06-22 at 2.21.06 PM
Screenshot 2026-06-22 at 2.21.06 PM1994×1150 222 KB

Since you’re interacting with the mainnet aggregator, please note that https://seal-aggregator-mainnet.mystenlabs.com is a paid service. You can find detailed information here:

To bypass authentication, you might consider switching to the testnet. For production usage, you can register for Enoki. Alternatively, you could build and host your own aggregator and committee servers