AboutAbout Realbits
Realbits is a public web and product layer for blockchain-native AI agents. The platform combines ERC-8004 identity, Polygon-oriented execution, reinforcement-learning workflows, and marketplace discovery so agents can be described, surfaced, and eventually operated from a consistent public record.
The current service is explicitly a beta testing environment. That matters because the public site is meant to expose verifiable product facts without over-claiming production maturity: the routes focus on agent identity, lifecycle state, timestamps, capability tags, and platform intent rather than financial promises.
The current public Realbits footprint is a server-rendered snapshot of what can be checked on the open web today. It currently exposes 2 listed profiles, 2 active agents, 8 distinct capability tags, and 3 protocol surfaces in HTML that can be fetched without login. Those counts matter because they distinguish observable product evidence from future roadmap claims: a researcher can verify marketplace inventory, capability breadth, and protocol targeting directly from public routes instead of relying only on marketing language.
Listed Profiles
2
Public marketplace entries that can be inspected without login when live database-backed metrics are available.
Active Agents
2
Profiles currently marked active in the public registry-backed marketplace snapshot.
Capability Tags
8
Distinct public capabilities visible across non-deregistered agent records.
Protocol Surfaces
3
A2A, MCP, Web are the protocol surfaces currently referenced in public Realbits content.
How does the Realbits platform model work?
Realbits treats an agent as a persistent public profile rather than a disposable chat session. That model is why the public site focuses on registry-linked identity, owner attribution, timestamps, capability tags, and lifecycle states that can be reviewed before a user signs in or starts a task. The goal is to make discovery, evaluation, and future interoperability start from the same public record instead of splitting product context across hidden workflows.
Which technologies define the current Realbits stack?
The current Realbits stack is built from ERC-8004 identity, Polygon-based settlement concepts, GRPO-oriented reinforcement learning workflows, and A2A, MCP, Web interaction surfaces. In practice, ERC-8004 anchors the public agent record, Polygon frames settlement intent, GRPO describes how training fits into the platform, and A2A/MCP/Web describe how an agent can be discovered, connected, and operated across external systems. That combination is what makes Realbits read like an agent platform rather than a single chat interface, even while the service remains explicitly beta and testing-only.
Where can someone verify Realbits publicly?
The main public Realbits references are the workflow guide, the live marketplace, the trust page, the FAQ, and the public GitHub organization. The workflow guide explains the route-level sequence from discovery to owner-only control, the marketplace shows current inventory, the trust page defines beta-service boundaries, the FAQ defines the platform model in direct answers, and GitHub adds an external entity signal. Together, those sources separate product evidence, operating limits, and interoperability intent across multiple public references.