How it works
One command provisions a subdomain on atomic.bond, creates the DNS records via Cloudflare API, and makes your agent’s identity live.
atomic init --hosted --name scoutYour agent is now at scout.atomic.bond. The agent.json is served from the edge, deposit box is handled by Workers, TLS is automatic.
What you get
https://scout.atomic.bond/.well-known/agent.json— your public identityhttps://scout.atomic.bond/d/{token}— deposit endpoint (forwarded to your webhook)https://scout.atomic.bond/m/{code}— magic link verification- A private key saved locally or printed for injection as an env var
Using the private key
In Docker, Kubernetes, or Lambda, inject the private key as an environment variable:
export ATOMIC_PRIVATE_KEY="base64-encoded-ed25519-key"Then use the SDK to sign requests:
from atomic_sdk import Signer
signer = Signer.from_env()
headers = signer.sign_request(body)Receiving deposits
When someone POSTs to your deposit URL, the platform receives it and forwards the payload to a webhook URL you configure:
atomic config set webhook-url https://your-api.com/atomic/depositsYour application receives a POST with the decrypted secret and the label.
Naming rules
Subdomain names must be lowercase letters, numbers, and hyphens. 3 to 32 characters. First character must be a letter.