Plugins
1. Definition and Core Role
In the anatomical analogy of the REVOX ecosystem, Primitive Agents form the muscles and body, while Plugins act as the senses—the eyes, ears, and mouth. They are the critical gateways through which REVOX agents perceive and interact with the external digital world.
Plugins extend the boundaries of the ecosystem by enabling direct API connections to external services, spanning both traditional Web2 platforms and decentralized Web3 protocols. By serving as conduits for external intelligence and functionality, Plugins give Primitive Agents the ability to retrieve information, execute transactions, and leverage services beyond the native REVOX runtime.
2. Architectural Principles
Clear Separation of Concerns
Primitive Agents remain lightweight and focused.
Plugins handle specialized integrations—Web2 APIs, blockchain RPCs, third-party services.
Standardized Interfaces
Every Plugin implements a consistent API schema: request format, response schema, error codes, retry policies.
This ensures agents can interact seamlessly with any Plugin.
Security and Permissions
Plugins declare capability scopes (e.g., read-only query vs transaction execution).
Execution is sandboxed, with audit logs for every call.
Versioning and Lifecycle Management
Plugins are versioned; backward compatibility is maintained.
Deprecated or risky versions can be flagged in the Plugin Registry.
Monitoring and Metrics
Each Plugin tracks latency, error rates, and usage volume.
Poorly performing Plugins can be replaced or excluded by workflows.
3. Crypto-Related Plugin Use Cases
Chain RPC Plugin
Provides direct access to blockchain nodes for querying balances, transaction history, and broadcasting signed transactions.
Critical for enabling Wallet Agents or Compound Agents to execute DeFi strategies.
Etherscan Plugin
Integrates with the Etherscan API, letting agents retrieve verified contract metadata, historical transactions, and wallet analytics.
Used by compliance workflows or research agents.
Token Price Plugin
Fetches real-time token prices from multiple decentralized exchanges and oracle networks.
Includes safeguards such as median aggregation and anomaly detection for unreliable feeds.
4. Traditional Plugin Use Cases
Google Search Plugin
Empowers agents to perform knowledge retrieval tasks directly from the web.
Useful for research-oriented workflows or context enrichment.
Twitter Plugin
Connects agents to Twitter APIs, enabling social sentiment analysis, trending topic monitoring, and community engagement tasks.
Location Service Plugin
Supplies geolocation data to agents, enabling location-based logic for applications such as logistics or local compliance.
Gmail Plugin
Integrates email capabilities, allowing agents to parse, send, or organize communications.
Useful for productivity workflows and personal digital assistants.
5. Integration and Interfaces
How Agents Interact: Primitive Agents do not need to “understand” external protocols directly. Instead, they communicate with Plugins via standardized request/response schemas.
API-Driven Design: Plugins expose structured endpoints, not natural language. This ensures deterministic, auditable, and reproducible behavior.
Seamless Workflows: When building Compound Agents, Plugins are chained together with Primitive Agents, providing a smooth pipeline from intent → execution → verification.
6. Security and Governance
Plugin Registry: All Plugins are listed in the REVOX Plugin Registry, with metadata (capabilities, provider, version).
Community Review: Developers and users can audit, review, and rate Plugins, establishing a trust and reputation system.
Permission Scopes: For high-risk Plugins (e.g., transaction execution), stricter governance and multi-signature approval may be required.
7. Why Plugins Matter
Extendibility: They allow REVOX to rapidly integrate with new services and chains without modifying core agents.
Specialization: Plugin developers can focus on domain expertise (e.g., market data, social feeds), while agent developers focus on orchestration.
Ecosystem Growth: A Plugin marketplace incentivized by $REX ensures continuous evolution of capabilities and sustainable contribution.
Last updated