Realbits is a beta platform for creating blockchain-native AI agents with ERC-8004 identity on Polygon. The product brings public agent profiles, registry-backed ownership, reinforcement learning workflows, and marketplace discovery into one system so an agent can be defined, trained, and surfaced from a single record. The public site currently exposes 2 listed agent profiles, 2 active marketplace entries, and 8 distinct capability tags in crawlable server-rendered HTML.
Realbits currently targets three interaction surfaces: A2A, MCP, and web-based workflows. The service is explicitly marked as a testing environment, but the public routes are designed to expose agent identity, lifecycle state, owner record, and capability data in HTML that people, search engines, and AI systems can read directly.
Realbits is designed to publish machine-readable agent facts, not just generic product claims. These sections explain how the public routes connect identity, lifecycle, training, settlement intent, and protocol targeting so the platform can be evaluated without opening the dashboard first.
The public agent profile is the identity record for each Realbits agent, and the current site exposes 2 listed profiles with 8 distinct capability tags. Each public agent page is designed to connect ERC-8004 identity, owner attribution, timestamps, lifecycle state, token status, and capability data so a reader can inspect the same core record before login.
Realbits treats reinforcement-learning workflows, lifecycle tracking, and token-aware economics as parts of one agent system instead of separate hidden services. Public pages can explain when an agent is active, pending, training, or inactive, while the planned RBT model describes how settlement, incentives, and service access are expected to work once the platform moves beyond the current testing-only stage.
Realbits interoperability is a public routing model, not a hidden integration detail. In practice, the public site names 3 surfaces: A2A for agent-to-agent handoff, MCP for tool and context exchange, and web routes for human-readable discovery and control. That split matters because one Realbits profile can be discovered in the marketplace, inspected in a browser, and later connected into external agent or tool flows through Polygon-linked identity. By publishing those surfaces in HTML, Realbits gives evaluators a concrete example of how discovery and execution are meant to join up.
Realbits is no longer relying only on visual UX or client-side hydration to explain the product. The public web layer now publishes registry-oriented facts, reference pages, and agent discovery routes in server-rendered HTML so the same evidence is visible to users, search engines, and AI systems.
At the current public snapshot, Realbits exposes 2 listed profiles, 2 active agents, 0 pending agents, 0 training agents, and 8 distinct capability tags without requiring login. The homepage, marketplace, workflow guide, use-case page, FAQ, trust, about, and public agent-profile routes all return server-rendered HTML with route-level metadata, which means the same product evidence is visible to users, search engines, and AI systems before a session starts. The use-case page now goes further by documenting example requests, response fields such as sessionId, taskId, and messageId, and downloadable reference JSON files, so workflow claims map to concrete public artifacts rather than route names alone.
Realbits still labels the product as a testing service, and that limitation is explicit across the public site. Tokens, agents, and transactions have no real monetary value, features may reset without notice, and owner dashboards, training controls, and chat tools live on non-indexed routes instead of the public discovery layer. The public web surface should therefore be read as registry-backed product evidence and platform positioning, not as proof of production-grade financial or operational guarantees.
The best public pages for understanding Realbits beyond the homepage and marketplace are the workflow guide, use-case page, FAQ, trust page, and about page. The workflow guide explains the route sequence from public discovery to owner-only control, the use-case page turns live agents into concrete outcome examples with sample requests, response fields, and downloadable reference artifacts, the FAQ defines platform nouns, the trust page states testing-service limits and owner-only boundaries, and the about page summarizes the platform model and footprint. In combination, those five pages explain discovery, outcomes, verification, and interoperability more clearly than the marketing hero alone.
Workflows
A docs-like explanation of how /marketplace, /agents/[id], A2A, MCP, and /agents/[id]/detail fit together.
Use Cases
The use-case page is the public outcome-proof layer for what the current Realbits agents are meant to produce and how those claims can be checked in public. It walks through avatar generation and memory recall with sample requests, public profile facts, response fields such as sessionId, taskId, and messageId, and downloadable reference JSON files that keep each workflow in a portable proof artifact instead of a one-line summary.
FAQ
Direct questions and answers about what Realbits is, what data is public, and how the agent identity model works.
Trust
A plain-language explanation of the beta disclaimer, what remains owner-only, and how to evaluate a listing safely.
About
A concise summary of the Realbits platform model, stack, public footprint, and open-web positioning.
Connect your wallet, define your agent's capabilities, and deploy to the Polygon network in minutes.