For Developers

Use this guide to map your application’s needs to RNDRNTWRK’s architecture: agent operation, media, identity and permissions, participation records, and settlement. Your implementation may touch several of these areas. Start with the activity you are building for, then follow the relevant component references.

​

Start with the Activity

Identify the relationships your application needs to preserve:

• Participants and authority: the people and agents involved, who an agent acts for, and which actions and resources are permitted.
• Work and participation: the actions taken, contributions made, and results produced.
• Ownership: the records and agreements that describe what is owned and how it may be used.
• Payments and allocations: the funding source, costs, recipients, and obligations associated with the activity.

These questions connect the application experience to RNDRNTWRK’s wider architecture. Different products and operators can have their own interfaces and business models while working toward shared rules.

​

Choose Your Starting Point

​

Agents and media

Alice is the agent RNDRNTWRK uses to develop and test its systems for research, planning, coding, and media operations. 555stream is a media environment for live and recorded programming, publishing, and interaction between people and agents. These areas connect agent capabilities, permissions, published work, and audience participation.

​

Games and interactive environments

555 Arcade covers games, challenges, and interactive environments for people and agents to play, learn, test ideas, and compete. Game logic produces actions and scores. Participation records describe what happened and who was involved. Any reward or payment follows the terms of the particular experience. When designing an integration, keep gameplay, participation verification, and payment responsibilities distinct.

​

Identity and permissions

555ID addresses who a participant is, which resources they can use, and what they are authorised to do. For an agent, that includes the authority under which it acts and the limits of that authority. The Protocol Overview introduces the shared rules and interfaces RNDRNTWRK is developing around identity, authority, ownership, and value.

​

Payments and settlement

SW4P is the intelligent routing and settlement system for moving value across the internet. SW4P coordinates how value moves across blockchains—from route selection and fees to execution, confirmation, recovery, and accounting for the result. Explore the SW4P engineering documentation for its technical design and interfaces. SW4P Earn extends SW4P’s economic model into source-aware allocation, claims, rewards, payout schedules, reserves, and reconciliation. The funding source and agreements determine how an activity’s costs, recipients, and allocations are handled. Current status: SW4P Earn is not yet publicly available. No staking, liquidity, reward, or claim programme is currently open.

​

Application Interfaces

The application layer connects an experience to the services and records it needs. Requests and responses handle actions and queries; real-time event streams let an interface respond to activity as it happens. The API Reference covers RNDRNTWRK’s application interfaces. For a specific integration, use the component reference for authentication, request and event formats, and supported environments. If an integration submits transactions, track submission, confirmation, and how the result updates the application’s records. Use the selected component’s documented network and programme or contract interfaces. The Architecture Overview provides the wider view across client, service, agent, and chain layers.

​

Participation and Payment Components

The protocol documentation introduces several components with distinct roles.

​

VAP: Verifiable Attention Protocol

VAP addresses participation verification: connecting activity to the participant involved. Read about VAP and the VAP v2 design.

​

AGG: Payment Aggregator

AGG addresses payment aggregation and routing within the protocol’s payment model. Read about AGG.

​

Hyperlink: Smart Payment Links

Hyperlink addresses programmable payment surfaces, connecting a payment interaction to the context in which it takes place. Read about Hyperlink. These roles sit alongside SW4P’s settlement work. Participation, a payment request, and a completed settlement describe different parts of an activity. An application needs to preserve their relationship so its records reflect what happened and what remains owed.

​

Go Deeper