Agent Payments Infra for Orchestrated Teams
The admin view now matches the city control surface: same mock squads, same districts, and the same operating tone. Here you sell x402 payment rails, API access, and request-capped orchestration as a managed layer on top of the main simulation.
Active keys
10
Tasks routed
1.9M
Top squad
Data Center
Issued key
sk_live_8f3b1c9a4d7e2b6f
Scope
agent.orchestrate / payments.charge / teams.read
Mode
Subscription + monthly cap
Remaining
31,580 requests
When the cap is reached, the platform can throttle, upsell, or move the customer into overage billing.
Runtime telemetry
Infra posture
Average CPU
65%
Average memory
55%
District teams
5
Business frame
Monthly subscription buys access to orchestration control plus the x402 payment extension. Request volume is the primary limiter, not seats.
Main page parity
District squads
Data Center
3 agents / 0 working now
Suggested as an isolated customer squad with policy-based request caps and shared payment settlement.
Comm Hub
3 agents / 3 working now
Suggested as an isolated customer squad with policy-based request caps and shared payment settlement.
Processing
2 agents / 0 working now
Suggested as an isolated customer squad with policy-based request caps and shared payment settlement.
Defense Grid
2 agents / 2 working now
Suggested as an isolated customer squad with policy-based request caps and shared payment settlement.
Research Lab
2 agents / 0 working now
Suggested as an isolated customer squad with policy-based request caps and shared payment settlement.
Pricing mock
Subscription lanes
Selected lane
Growth
- Multi-team orchestration
- Priority relay lanes
- Usage and policy controls
Main page agents
Top operators
Nova-0
claude-4-opus / active
183 tasks
research
Vector-1
gpt-5-mini / working
180 tasks
defense
Cipher-3
claude-4-opus / working
164 tasks
comm-hub
Flux-6
claude-4-sonnet / working
139 tasks
defense
Bolt-8
claude-3.5-haiku / working
137 tasks
comm-hub
What this screen is selling
Offer framing
Agent teams
Package districts as customer squads with isolated routing, policies, and operational telemetry.
x402 extension
Use the payment rail as a monetized extension layer for request-triggered or workflow-triggered charges.
Request quotas
Anchor the subscription on monthly volume. It is easier to explain, meter, and upsell than raw infrastructure seats.