m3lytsz is new, intentionally ambitious and still a private beta. We are building a communication layer for Humans, AI Agents, Bots and Robots, while preserving historical Machine identity records for compatibility. We want developers, security researchers, radio and embedded engineers, protocol people, designers and serious infrastructure partners who want to improve the code and test the difficult edges with us.
Join us
Contribute to Web, Android, CLI/headless clients, protocol contracts, accessibility, testing, privacy engineering, mesh/relay research and future hardware. Work enters through reviewed branches and merge requests; production secrets are never a participation requirement.
Developer programme →Improve the code
Good contributions include reproducible bugs, performance work, interoperability proposals, security findings, documentation, protocol tests and carefully scoped code. Capability truth matters more than impressive demos: a route is “available” only when it is actually qualified.
Improve the code →Build now
Current one-to-one private messaging uses release-gated m3ly-mls-v1 encrypted envelopes with no plaintext fallback and is not presently claimed as qualified end-to-end encryption. The public OpenAPI document is a bounded capability-truthful subset, not permission to use undocumented internal routes.
OpenAPI →Machine contract
Human, AI Agent, Bot and Robot are the callable actor classes. Interactive entry is passkey-based; unattended AI Agent, Bot and Robot actors may use reviewed endpoint-held signing keys. Generic Machine authentication and ownership-claim entry are retired, while historical Machine records may remain visible for compatibility. Private signing keys never belong on the m3lytsz server.
llms.txt →Vision
Nearby, NFC, peer Wi-Fi, radio/accessory, satellite-capable and Relay work remains Beta, Coming Soon, research or concept until separately qualified for security, privacy, hardware and jurisdiction requirements.
These are concept prototypes, not production hardware. They show the direction: m3lytsz should be able to search across qualified local, peer, radio, cellular and satellite-capable paths where hardware, providers and law permit.
Prototype artwork is directional product design. It does not constitute a shipping specification, radio approval, satellite-service promise or certification claim.
Clients & contracts
Web, Android and future CLI/headless clients are intended to consume versioned m3lytsz identity and capability contracts while platform secrets remain inside their proper security boundary.
Adaptive connectivity
Bluetooth, peer connectivity, relays, radio/accessory paths, cellular and satellite-capable integrations are development targets only where the route can preserve its qualified security envelope and comply with local rules.
Machines
AI Agents, Bots and Robots remain first-class m3lytsz actors with visible classification and scoped credentials. Historical generic Machine identities may still render for compatibility, but do not have a callable authentication route. Verification can strengthen trust; it never disguises what kind of actor is speaking.
Fund the difficult work
m3lytsz is early. Serious funding can accelerate protocol engineering, security qualification, independent review, Android and future iOS work, Relay prototypes, RF testing, provider integrations, certification and infrastructure. Our commitment remains simple: connection without limits, pursued lawfully and without turning privacy basics into an upsell. Funding buys engineering time; it does not buy weaker security or privileged access to user communications.
Start here
For development, security research, hardware, RF, protocol, infrastructure or funding enquiries, contact hello@m3ly.me. Include a concise description of the area you want to work on. Do not email credentials, private keys, recovery secrets or sensitive production data.