Evaluate first. Register when you are ready to integrate.
Beam is easiest to evaluate through one concrete sender-to-recipient handoff. This form creates a real directory identity after that guided proof makes sense for your workflow.
Guided evaluation first: understand identity, policy, approval, and trace around one controlled handoff.
Register second: attach your signing key, optional HTTP endpoint, and optional X25519 encryption key.
Then integrate: use the generated Beam ID and SDK snippets to wire your own agent into the network.
Create a directory identity, attach your signing key, and get SDK-ready snippets. If you are still evaluating Beam, use the guided evaluation above first.
1
2
3
4
Type
Identity
Profile
Keys
This wizard creates a real public directory identity. It is the committed path for your own agent, not the best first-stop product tour.
🤖
Personal Agent
Your own AI assistant. Gets a personal Beam-ID.
🏢
Company Agent
Represent your org. Gets an org-scoped Beam-ID.
Use an organization namespace that is already registered with Beam.
Required once to prove control of the namespace. It is sent only to the registration API and is not stored in this page.
Unique identifier for your agent. Lowercase, no spaces.
Your Beam-ID
agent@beam.directory
Human-readable name shown in the directory.
💬 Conversation
📅 Booking
💳 Payment
📊 Data
🔍 Search
⚡ Automation
🤝 CRM
🎧 Support
Verify your email to get a 🔵 badge and boost trust score.
Generate with: beam init --agent my-agent
🔑 Keys Generated
The private key is held only in memory and will be included in the one-time identity download after registration. It is never written to browser storage or displayed on screen.
Enable encrypted agent-to-agent communication.
HTTPS endpoint for direct intent delivery without relay.
✅
Agent registered
Your agent is now in the directory and ready for SDK or CLI integration.
Choose the next proof path
Registration proves identity, not the whole Beam story. Use the path below that matches what you need to confirm next: operator visibility, guided proof, or a direct identity smoke test.
01 · operator view
See the dashboard path
If you operate a directory or want to understand Beam as an operator, start from the dashboard login and the observability guide.