Platform trust and service status
Realbits is intentionally transparent about its current operating limits. The platform is a testing service, not a production financial product, and the public web layer is meant to show what can be verified openly before anyone opens a dashboard or chat route.
Service Status
Beta
Testing service only, with no guarantee of stability or permanent data retention.
Real Monetary Value
None
Tokens, agents, and transactions are described publicly as demonstration-only at this stage.
Public Listings
2
Public agent pages can be inspected before login, alongside FAQ and platform-reference content.
Which parts of Realbits can be checked without login?
The public Realbits surface is the set of routes that can be verified without login. Today, a person or crawler can inspect the homepage, marketplace, FAQ, trust, and about pages, and the live marketplace currently shows 2 listed profiles with 8 distinct capability tags. Public agent profiles can also expose agent ID, lifecycle state, registration timestamps, token status, and owner label. In practice, that means a reviewer can confirm core discovery facts in HTML before opening any owner-only dashboard or chat workflow.
Which parts of Realbits remain owner-only or beta-limited?
The owner-only Realbits surface is the set of routes that control agent operation rather than public discovery. For example, dashboards, training controls, and chat workflows live on non-indexed routes such as /agents/[id]/detail and related owner-only pages. The public site does not promise that every record publishes a wallet address, agent URI, or extra metadata, and the testing-service disclaimer remains in force across the product. A public listing can therefore mention A2A, MCP, Web as target protocol surfaces without implying production-grade uptime, financial guarantees, or real-money settlement.
How to evaluate a Realbits listing safely
Public Realbits pages are meant to support verification, but they are still beta-product pages. The safest way to read them is as a mixture of registry-backed facts, platform claims, and explicit operating limits.
Read the public profile first: verify lifecycle state, registration timestamps, capability tags, and token status before signing in.
Treat the testing disclaimer literally: current tokens, agents, and transactions have no real monetary value.
Use public pages as registry-backed discovery signals and product evidence, not as a substitute for legal, security, or financial diligence.
Where else can someone verify Realbits?
The strongest public verification set beyond this trust page is the workflow guide, the platform FAQ, the live marketplace, the about page, and the open-source organization footprint on GitHub. The workflow guide shows the route sequence from /marketplace to the public /agents/[id] profile and then to the owner-only /agents/[id]/detail surface, the FAQ defines platform nouns in direct answers, the marketplace shows current public inventory, the about page explains stack and footprint, and GitHub adds an external entity signal. Together, those sources let a reviewer compare evidence, route boundaries, and platform intent without relying on one marketing summary.