💬 MESSENGER

Managed message encryption API

Messaging identities, sessions and one-time prekeys, with each message encrypted under a per-session key using AES-256-GCM. Session keys are agreed with X25519; identities are ECDSA P-256 signed.

Not end-to-end encrypted. You send plaintext to the API and the service encrypts it — it generates your keypairs and holds the key that unwraps them. Key agreement is X25519, which is classical, not post-quantum. Currently a developer preview: identities, sessions and messages are held in memory and are lost when the service restarts.

Quick Example

curl -X POST https://messenger-api.qntyx.io/identities/ \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

API Base URL

https://messenger-api.qntyx.io

Endpoints

MethodPathDescription
POST/identities/Create an identity
POST/sessions/Establish a session
POST/messages/Send a message (body includes plaintext)
GET/messages/{session_id}List a session's messages
GET/stats/Dashboard statistics

Authentication

All endpoints require a bearer token. See Authentication for details.

Dashboard

Manage this product visually at app-messenger.qntyx.io

Marketing Page

Learn more at msg.qntyx.io