JavaScript
No public calling SDK. Open the native app, or pair a browser through the ArnaconWeb companion when you have one.
Developers
Talk as an email you already own, or as a new identity. No phone number required. You bring the host app. The SDK only enables.
This is the store SDK. iOS is the iArnacon Swift package. Android is a vendored JAR plus the open-source ArnaconWeb3 wrapper. There is no Maven artifact, no CocoaPods pod, and no public JavaScript calling SDK.
Choose a path
Each quickstart is the same sequence: install, implement the host contracts, init, then send a first message and a first call. Pick the stack you are shipping.
Explore the docs
The quickstarts get you to a first send. Concepts explain identity, products, and notification types. The reference is the public surface copied from source — not invented client classes.
Identity vs label, products, notification types, and what the host app still owns.
iOS Arnacon and Android ArnaconWeb3 methods the store apps actually call.
Installed product: upsert web3identity. Desktop login: mailbox, then the same row. Prompt for an implementing AI.
No public calling SDK. Open the native app, or pair a browser through the ArnaconWeb companion when you have one.
A spec, not a live host. The machine-readable file is mcp.json. Writes need an explicit confirm. Keys never leave the device.
Source of truth
The integration packages are not on Maven Central or the public Swift package index. As of this writing the GitHub repos are not world-readable. Clone them only after you have been granted access. Do not invent a version pin that is not on the package.
Next
Do not start from an API-key sample. Arnacon has no API key. The host app supplies storage, a server implementation, and the call UI.