$GPS: Security Service Settlement Layer
$GPS is the economic coordination layer of the GoPlus Security Network. It aligns the parties that consume security services, the operators and contributors that produce them, and the ecosystem participants that govern the network.
As GoPlus expands from Web3 security intelligence into execution security for autonomous systems, the role of $GPS is intended to expand with it. GoPlus' long-term strategy is to position $GPS as the core settlement unit for security-service consumption across its ecosystem. Rather than functioning only as an ecosystem incentive or a traded asset, $GPS is designed to support the consumption of security intelligence, contract analysis, agent-security controls, software supply-chain verification, and other machine-accessible security services.
One Settlement Unit Across Two Directions
GoPlus' strategy covers two directions: AI for Security, where AI is applied to auditing, scanning, detection, and simulation, and Security for AI, where security is applied to the AI systems and agents that now act autonomously. Both directions produce security as a service, and both are settled in $GPS.
In AI for Security, the services consumed are DeepScan audits and monitoring, SafuSkill scans, GoPlus Intelligence checks, and transaction simulation. Consumers are projects, platforms, wallets, exchanges, and increasingly agents.
In Security for AI, the services consumed are Axora Router policy decisions, Axora AgentGuard runtime evaluations, Axora Arena red-team runs, SafuSkill trust verification, and AI Agent Security API calls. Consumers are developers, teams, enterprises, agent platforms, and agents themselves.
The two directions are connected through $GPS. AI for Security produces the intelligence that Security for AI enforces at runtime; Security for AI generates the high-frequency, machine-originated consumption that funds the contributors and operators producing that intelligence. A single settlement unit lets value move between the two without friction.
Why Security Is Becoming a Machine-Consumed Service
Traditional security is sold in fixed units. An enterprise buys an annual license, a human operates the software, and security spend stays roughly flat regardless of how much the protected system actually does.
Autonomous systems break this pattern. An AI agent may require a security decision every time it:
accesses a model, tool, or data source;
installs a skill, plugin, package, or MCP server;
reads untrusted web content or documents;
handles credentials or sensitive files;
prepares, signs, routes, or submits an on-chain transaction;
interacts with a new counterparty, token, or contract;
takes any sensitive runtime action that policy requires to be checked.
Rather than security being applied only at deployment or through periodic review, agents may require security decisions continuously as they access models, invoke tools, retrieve data, and execute actions. This creates the potential for security to become a machine-consumed service, with usage scaling alongside agent activity rather than only with the number of human users or enterprise seats.
This shift is the economic foundation of the $GPS model. Industry forecasts point to more than a billion actively deployed AI agents by the end of the decade, executing hundreds of billions of actions per day. Even a small fraction of those actions requiring a security check represents a security-consumption volume with no precedent in the seat-based security market.
The GoPlus Security Service Flywheel
The GoPlus strategy links AI-security expansion, service consumption, and $GPS into one chain:
More agents are deployed across development, enterprise, and financial workflows.
More actions are taken by those agents: tool calls, software installs, data access, transactions.
More security checks are required before those actions execute.
More security-service consumption flows through Axora, SafuSkill, DeepScan, GoPlus Intelligence, and the AI Agent Security API.
More $GPS-denominated settlement is generated as those services are consumed.
Stronger network economics fund operators, data contributors, and service providers, improving the quality and coverage of security intelligence, which in turn attracts more consumption.
The important property of this loop is that $GPS utility is designed to scale with actual security-service consumption, not only with secondary-market activity or with the growth of GoPlus as a company.
Role of $GPS in the GoPlus Security Network
$GPS is designed to serve four connected functions.
1. Security-Service Settlement
$GPS is the native unit in which security services across the GoPlus ecosystem are metered and settled.
Human-initiated consumption: GoPlus App users pay security gas in $GPS for transaction protection; business users can pay in $GPS for GoPlus Intelligence; projects can pay in $GPS for DeepScan audits, SafeToken Protocol, and Locker services.
Machine-initiated consumption: as AI agents consume security intelligence, runtime policy decisions, supply-chain scans, and contract analysis programmatically, GoPlus intends for $GPS to become the core settlement unit for that consumption.
Enterprise consumption: enterprise customers may continue to pay in fiat or stablecoins through invoicing or usage-based rails such as x402. GoPlus intends to route a defined share of this revenue into $GPS-denominated settlement, so that machine and enterprise usage contribute to $GPS demand regardless of the payment rail the customer uses.
2. Machine-to-Machine Security Consumption
The AI Agent Security API already gives autonomous systems programmatic, usage-based access to GoPlus security intelligence. GoPlus intends to extend this machine-to-machine model by using $GPS as a core settlement unit for security-service consumption. Under this model, autonomous systems consume security intelligence programmatically while settling for services through a standardized economic layer, linking machine activity directly with the underlying GoPlus Security Network.
Because agents can invoke security services at high frequency, this creates demand that scales with actions, transactions, and software interactions rather than only with the number of human users.
3. Network Participation and Incentives
$GPS coordinates the supply side of the network.
Security Compute Layer operators (including AVS operators and SecHub participants) stake $GPS to provide security analysis capacity and are rewarded in $GPS for verified work.
Data contributors stake $GPS to participate in the Security Data Layer and earn $GPS when contributed risk data is verified.
Security service providers that publish third-party services into the GoPlus ecosystem stake $GPS for accountability and receive $GPS when their services are consumed.
Settlement revenue generated by security-service consumption is the source of these rewards, which closes the loop between the consumers and the producers of security.
4. Governance
$GPS holders stake to obtain voting weight in GoPlus Network Governance, which sets the parameters of the security service economy: service pricing, the share of enterprise revenue routed to $GPS settlement, operator and contributor reward rates, and which third-party security services are admitted into the network.
Product Lines and $GPS
Every GoPlus product line is a source of security-service consumption. The table summarizes how each connects to $GPS.
Axora (Router, AgentGuard, Arena)
Router information-flow scans and policy routing, AgentGuard runtime action evaluations, deep scans and daily patrol, Arena red-team runs
Settlement unit for metered agent security; team and enterprise plans settle into $GPS
GoPlus SafuSkill (AI software supply-chain security)
Skill, script, and repository scanning, verification, ongoing monitoring
Settlement unit for scan, verify, and monitor services across the skill distribution layer
GoPlus DeepScan (AI smart-contract audit)
Token Security Self-Check, AI Contract Audit, Continuous Security Monitoring
Settlement unit for audits and monitoring subscriptions; deeper $GPS-settled tiers for continuous monitoring
GoPlus Intelligence and AI Agent Security API
Token security, malicious address, transaction simulation, rug-pull detection, phishing detection, signature and approval analysis
Settlement unit for usage-based access; x402 and API-key usage routed into $GPS settlement
GoPlus Web3 Security (App, extension, Security RPC, on-chain firewall, infrastructure integrations)
Transaction protection, wallet scanning, real-time alerts, chain- and RPC-level risk control
Security gas paid in $GPS; infrastructure partners settle protection volume in $GPS
SafeToken Protocol and Locker
Secure token issuance, liquidity locking, vesting, token management
Service fees and premium features settle in $GPS; $GPS usable in partner token-management platforms such as Custos
Security Data Layer and Security Compute Layer
Verified risk data and distributed security analysis
Staking and rewards in $GPS for contributors and operators
Mechanisms in Place and Planned Extensions
GoPlus distinguishes between mechanisms that operate today and extensions that are planned. This section is updated as new mechanisms ship.
Mechanisms in place
$GPS staking for network participants, governance voting weight, and Security Data Layer contributor participation.
$GPS rewards for verified security data contribution.
Security gas paid in $GPS for GoPlus App transaction protection services.
$GPS accepted for GoPlus security services including security intelligence, DeepScan, SafeToken Protocol, and Locker.
$GPS usable within partner ecosystems such as Custos for token-management workflows.
Usage-based, machine-to-machine access to GoPlus security intelligence through the AI Agent Security API built on x402.
Planned extensions
$GPS as the core settlement unit for the AI Agent Security API, so that machine-originated security consumption settles into $GPS.
$GPS-denominated settlement for Axora runtime security, SafuSkill scanning and monitoring, and DeepScan continuous monitoring.
A security-credit model in which fiat and stablecoin payments from enterprise customers are converted into $GPS-denominated settlement on the network side.
$GPS staking requirements and reward distribution for Security Compute Layer operators and third-party security service providers.
Public disclosure of $GPS settlement metrics alongside existing product metrics.
Measuring the Security Service Economy
Because $GPS utility is designed to track security-service consumption, GoPlus intends to report settlement metrics in addition to product and market metrics. The indicators that matter most are:
Security services settled in $GPS: total value of security services settled through $GPS in a period.
Share of ecosystem security consumption settled in $GPS: the proportion of all GoPlus service consumption, across human, enterprise, and machine channels, that settles in $GPS.
Machine-originated security transactions: the number of security checks invoked by autonomous systems.
Unique service-consuming agents: the number of distinct agents paying for GoPlus security services.
$GPS staked by operators, contributors, and service providers: the supply-side commitment to the network.
$GPS distributed as network rewards: the value flowing from settlement back to the producers of security.
These metrics, rather than price alone, are the measures by which GoPlus expects the economic development of the network to be evaluated.
Dependencies and Execution Risk
This model depends on execution. The extent to which AI-security adoption translates into $GPS utility will depend on the proportion of services settled through $GPS, the depth of integration across GoPlus products, and the adoption of machine-to-machine security consumption. Growth in GoPlus products does not automatically translate into $GPS demand today. The strategy described here is the mechanism through which greater usage of AI and Web3 security products is intended to translate into greater token utility over time, and the strength of that relationship will be determined by adoption of $GPS-denominated settlement across the network.
Conclusion
GoPlus protected Web3 users and transactions. GoPlus is now building execution security for AI agents and autonomous systems. AI agents create dramatically more software actions, API calls, tool interactions, and transactions than human users, which moves security from periodic, human-triggered protection toward continuously consumed, machine-native security services. $GPS is the settlement layer for consuming those services. More agents, more actions, more security checks, more security-service consumption, and more $GPS-denominated settlement together form the economic core of the GoPlus Security Network.
Last updated