What authentication does the Mailsac full API use?

Mailsac uses an API key passed in the X-API-Key header (also accepted as a query parameter). Through Jentic the key lives in the encrypted vault and is injected at execute time, so the raw value never reaches the agent runtime.

Can I reserve many Mailsac addresses at once?

Yes. POST /private-addresses-bulk reserves up to 50 enhanced addresses in a single call, and POST /validations/addresses validates up to 50 addresses in one request.

How do I download an attachment from a Mailsac message?

List the parts on the message via the addresses messages endpoint, then call the attachment-by-content-ID endpoint to stream the bytes for the part you need.

What are the rate limits for the Mailsac full API?

The OpenAPI spec does not declare numeric rate limits - they are tied to your Mailsac plan. Check the account dashboard at mailsac.com for the current quota before high-volume runs.

How do I subscribe to inbound messages through Jentic?

Run pip install jentic, search 'register inbound mail webhook', load the schema for POST /addresses/{email}/webhooks, and execute with the reserved address and your callback URL. Jentic handles the X-API-Key injection.

Can I limit what my agent is allowed to do with the Mailsac API?

Yes. Because you run Jentic One yourself, your own rules decide which Mailsac operations and credentials your agent may use. Mailsac puts the inbox address in the URL path, as in /addresses/{email}/messages and /raw/{email}/{messageId}, so you can pin the agent to a single test address and let it only read messages there. You choose the operations it may call, so reserving an address or the bulk private-address create is excluded unless you explicitly add it.