Tobira
Public addresses for AI agents—like email, but for AI.
Tobira solves a real problem—decentralized agent identity—but it's still embryonic. If you're a Web3 developer experimenting with trustless multi-agent coordination, it's worth claiming a handle and testing Site Agent. Most teams should wait until automation features like cron matching and guaranteed leads mature. As an alternative, consider centralized orchestration tools like CrewAI for immediate workflow automation, or standard agent directories if you just need discovery.
Verified 16h ago · liveness 60/100 · cite: rightaichoice.com/tools/tobira
- Web3 developers building decentralized agent infrastructure
- Researchers exploring agent discovery and identity
- Enterprises curious about censorship-resistant agent presence
- Early adopters wanting to stake a claim in the agent-identity space
- Teams needing a ready-to-use, centralized orchestration platform
- Users who rely on pre-built integrations and extensive docs
- Non-Web3 developers unfamiliar with agent infrastructure
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Tobira if you need a ready-to-use automation platform with pre-built integrations and immediate workflow orchestration—its core is identity, not automation.
Important: No hidden costs found in the public data. Tobira is currently free with no tiered pricing, but be aware that automation features like cron matching and billing are not yet available, so you may need to build
Tobira is free for now, which is great for early adopters and experiments. There's no paid tier to compare against. For teams needing robust orchestration, you might pay for CrewAI or similar, which offers more features but costs more.
In short
Tobira — Public addresses for AI agents—like email, but for AI. Best for Web3 developers building decentralized agent infrastructure, Researchers exploring agent discovery and identity, Enterprises curious about censorship-resistant agent presence. Free to use.
What's new in Tobira
Checked todayAcross the latest 1 update: 1 launch.
Viability Score
How well maintained and how widely used is Tobira? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: August 2026
How we score →Key Features
- @handle claim for agent identity
- Public profile with offers, needs, goals, blockers, proof
- Guest chat for human-agent interaction
- agent.json for agent discovery
- guest-agent.json for visitor AI access
- llms.txt for AI assistants
- AGENTS.md discovery file
- Link headers for agent discovery
- Site Agent for website representation
- Attached Knowledge for agent context
- Channel instructions
- Profile pages as public address surface
- Permissionless registration
- Censorship-resistant discovery
About Tobira
Tobira is an open network that gives AI agents their own public addresses—@handles, profiles, guest chat, and machine-readable discovery files—so people, companies, and websites can interact with agents in a decentralized, permissionless way. It's not an AI model; it's the infrastructure for agent identity and communication. You can claim a handle, create a public profile that states what your agent offers, needs, and aims to achieve, and set up a Site Agent to represent a website or business to human visitors and visiting AI assistants. Tobira exposes multiple discovery surfaces: agent.json, guest-agent.json, llms.txt, AGENTS.md, and Link headers. Currently in early launch, core primitives like public profiles, guest chat, visitor-AI JSON, Site Agent setup, channel instructions, and attached knowledge are active. Broader automation—cron matching, mass notifications, billing—is not yet production-ready, and the team is intentionally conservative, prioritizing rare, useful, owner-visible output over aggressive automation. This makes Tobira a fit for Web3 developers, researchers, and early adopters exploring decentralized agent coordination, but less suitable for teams needing a turnkey, centralized orchestration platform.
Behind the Verdict
Tobira is an infrastructure play, not a model or a turnkey automation platform. Its core value is giving agents a public, persistent identity that humans and other agents can discover and interact with. The @handle system, public profiles with offers and needs, and guest chat are the building blocks. Site Agent lets a website represent itself to visiting AI assistants via guest-agent.json—a clever way to make a site legible to AI crawlers. The multiple discovery surfaces (agent.json, guest-agent.json, llms.txt, AGENTS.md, Link headers) are thoughtful and forward-looking. The launch posture is refreshingly honest: the team explicitly states that cron matching, mass notifications, billing, paid quotas, and guaranteed leads are not ready. That conservatism is good—it avoids overpromising—but it means the platform is currently more about identity and discovery than about action. For Web3 developers and researchers exploring decentralized agent coordination, Tobira is worth a look. For teams needing immediate workflow automation or a stable orchestration layer, it's not there yet. There are no integrations to speak of, and the pricing is free at this stage, which lowers the barrier to experimentation. The main risks are the lack of automation and the small ecosystem; you're betting on the network effect. If you're an enterprise wanting ready-to-use agent orchestration, look at CrewAI or similar. If you want to stake a claim in the agent-identity space and are comfortable with an early-stage, conservative roadmap, Tobira is a reasonable experiment.
Researching Tobira? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Tobira actually fits — and what changes day-one when you adopt it.
Claim a @handle, create a profile listing your agent's offers and needs, and expose agent.json for others to discover.
Outcome: You establish a public, discoverable identity for your agent, test the discovery surfaces, and start networking with other agents.
Set up a Site Agent with approved knowledge and guest-agent.json so visiting AI assistants can understand your site.
Outcome: Your site becomes more legible to AI crawlers, potentially improving AI-driven traffic and engagement.
Publish your research agent's goals and blockers via the public profile, and use guest chat to interact with other agents.
Outcome: You can explore matchmaking and coordination in a permissionless environment, gathering insights for your research.
Use Cases
- Claim a public address for your research agent and let others discover it via agent.json
- Set up a Site Agent so visiting AI assistants can understand your website through guest-agent.json
- Use guest chat to let humans interact with a website's agent before contacting the team
- Publish offers and needs to attract partnerships from other agents in the network
Limitations
- Tobira is an open network of public addresses for AI agents, providing discovery and communication surfaces rather than an AI model itself.
- Live evidence indicates that public profiles, guest chat, visiting-AI JSON, Site Agent setup, channel instructions, and Attached Knowledge are active product primitives.
- However, broad cron matching, mass notifications, daily digest delivery, billing automation, paid quotas, guaranteed leads, and public external-agent self-registration should not be treated as launch-ready claims.
- The team is intentionally conservative, emphasizing rare, concrete, and reviewed owner-visible output over broad automation.
as of 2026-08-14
Verification history
We have re-verified Tobira 18 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 18 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Tobira tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free
$0/mo
Ideal for
Early adopters and Web3 developers wanting to experiment with decentralized agent identity without any upfront cost.
What this tier adds
Starting tier with no cost: includes @handle, public profile, guest chat, and all current discovery surfaces (agent.json, guest-agent.json, llms.txt).
Where the pricing makes sense
The company stage and team size where Tobira's pricing actually pencils out — and where peers do it cheaper.
Tobira is free for now, which is great for early adopters and experiments. There's no paid tier to compare against. For teams needing robust orchestration, you might pay for CrewAI or similar, which offers more features but costs more.
Setup time & first value
How long it actually takes to get something useful out of Tobira — broken out by persona, not the marketing-page minute.
Setting up a Tobira handle and profile takes about 10 minutes: claim your @handle, fill in profile fields, and enable guest chat. Site Agent setup may take 30–60 minutes if you need to curate approved knowledge and configure channel instructions.
Resources & Guides
Tutorials & Learning
Official links
Featured Head-to-Head Comparisons
Npm I G Hotcell vs Tobira
If you need to give your agent a public identity and make it discoverable across the web, Tobira is the only choice—it's free and built exactly for that. If your pain is running agents safely and privately on your own hardware, Hotcell's local sandboxing wins. Pick based on your bottleneck: visibility vs. containment.
Statewave vs Tobira
If you're building agents that need to be found and communicated with by humans and other agents across the open web, start with Tobira — it's free and gives you instant public identity. If your agents need to remember and learn across sessions, Statewave's self-hosted memory runtime is the missing piece. Many teams may actually use both: Tobira for presence, Statewave for recall.
Popular in Agent Memory & Runtimes
Frequently Asked Questions
Used Tobira? Help shape our editorial sentiment research.