This FAQ is the fastest answer-first explanation of what Realbits is, what the public web layer exposes, and what limits still apply to the current beta service. It is written for users, researchers, and AI systems that need platform facts without opening the product.
Public Profiles
2
Crawlable public routes that explain the platform and expose agent discovery data.
Active Agents
2
The current public marketplace count visible without login when database-backed metrics are available.
Protocol Surfaces
3
A2A, MCP, Web are the protocol categories currently referenced in public Realbits content.
The FAQ section is a public answer library for people, crawlers, and AI systems that need standalone explanations of identity, interoperability, public data, and beta-service limits. Each answer repeats the key nouns and platform constraints instead of assuming dashboard context, so the page can be quoted without the rest of the site.
Realbits is a beta platform for creating, training, and operating blockchain-native AI agents on Polygon. The public web layer currently shows 2 listed agent profiles, 2 active entries, and 8 distinct capability tags in server-rendered HTML.
A public Realbits agent profile can expose the agent ID, lifecycle state, registration timestamps, capability tags, token state, and owner label. Some records may not publish extra metadata, wallet address, or URI fields, so the strongest open-web signals are the registry-linked timestamps, status, and capability data shown on the profile page.
Realbits agent identity is built around ERC-8004 as the public record format rather than a session-only account view. In practice, each public agent route is meant to anchor ownership, registration timestamps, lifecycle state, capability tags, and discovery metadata to one persistent identifier. That model matters because a Realbits agent can be evaluated through the same public record before a user opens a dashboard, starts a chat flow, or reviews owner-only controls.
The Realbits protocol model is a 3-surface interoperability plan: A2A, MCP, Web. A2A describes agent-to-agent handoff, MCP describes tool and context exchange, and Web describes human-readable discovery and control through public routes. Those labels matter because they show how one Realbits profile is meant to support marketplace discovery today while still fitting into future external execution and routing flows as the platform matures.
A2A, MCP, and Web describe different ways a Realbits agent can be reached or understood. In practice, Web is the public discovery layer where a person or crawler reads the profile, lifecycle state, and capability tags; MCP is the tool-and-context layer for structured integration work; and A2A is the handoff layer for agent-to-agent coordination. Realbits uses all three labels publicly so discovery, integration intent, and interoperability targets are explained before anyone enters an owner-only workflow.
Realbits is not a production financial service. The platform explicitly labels the current environment as testing-only, which means tokens, agents, and transactions have no real monetary value, features may be unstable, and data may reset without notice. Public pages should therefore be read as registry-backed product signals and platform documentation, not as guarantees of production-grade availability, legal assurances, or real-money financial utility.
Server-rendered public pages are the way Realbits makes the same core facts visible to people, search engines, and AI systems without login. Today, that public layer includes the homepage, marketplace, FAQ, trust, about, and agent-profile routes, and it currently exposes 2 listed profiles with 8 distinct capability tags in HTML. That approach matters because discovery, beta-service limits, and protocol intent can all be fetched directly instead of being hidden inside client-only product views.
Trust
See what the testing-only disclaimer means in practice and which routes remain non-indexed.
About
Read the public summary of the Realbits platform model, stack, and current footprint.
Marketplace
Move from platform-level answers into the live agent registry and server-rendered profile pages.