Skip to main content
OneShot is the payment infrastructure for agent commerce. This roadmap outlines what we’re building to make it the standard nobody replaces.

Progress

Phase 1: The Wire

Core x402 payment flow. Agent pays service. Service delivers. Receipt generated.

Core SDK

Wallet management, x402 client, basic receipts

Wallet Providers

Coinbase CDP Server Wallets, raw private key, custom providers

Framework Integrations

OpenClaw skill published, MCP server with auto-detect CDP/raw key

Transaction Logging

On-chain settlement records and local transaction history

Phase 2: The Eyes

Observability. Developers can see what their agents are spending.
The metric that defines agent commerce performance.
RoCS = Value Generated / Total Cognitive Spend
A RoCS of 3.0 means the agent creates 3ofvalueforevery3 of value for every 1 it spends. Below 1.0, it’s losing money. Works the same whether you’re running one agent or a hundred.The SDK computes RoCS automatically from transaction data. Developers add one line:
const result = await oneshot.pay(service, amount, {
  valueTag: { type: 'revenue', amount: 4.50 }
});
Every transaction is auto-classified by category:
CategoryExamples
InferenceLLM API calls, embedding generation
DataResearch APIs, enrichment, web scraping
ComputeServer provisioning, GPU rental
ToolingSaaS APIs, developer tools
CommercePhysical purchases, domain registration
Agent-to-AgentSoulMarket jobs, peer agent services
const breakdown = await oneshot.spend.breakdown({ period: '30d' });
// { inference: 42%, data: 28%, compute: 18%, commerce: 12% }
Developer View — Real-time spend rate, RoCS trend, success/failure rates, cost breakdown by category, budget utilization, searchable receipt log.Fleet View — All agents ranked by RoCS, aggregate spend, anomaly detection, cost allocation by agent, fleet-level P&L.Ecosystem View (public) — Total transaction volume, active agents, average RoCS, growth metrics.
const agent = await OneShot.create({
  cdp: true,
  budgets: {
    daily: 50,
    perTransaction: 5,
    alertAt: 0.8,
    pauseAt: 1.0
  },
  alerts: {
    webhook: 'https://...',
    slack: '#agent-alerts'
  }
});
Agent hits 80% of daily budget, developer gets notified. At 100%, the agent pauses. No empty wallets at 3am.
3

Phase 3: The Proof

Verification. Every transaction becomes a provable event.
Every x402 transaction produces a signed receipt:
{
  "tx_id": "oneshot_tx_abc123",
  "timestamp": "2026-02-15T14:30:00Z",
  "payer": "0x1234...agent_wallet",
  "payee": "0x5678...service_wallet",
  "amount": "0.50",
  "currency": "USDC",
  "service": "api.example.com/v1/research",
  "request_hash": "sha256:...",
  "response_hash": "sha256:...",
  "settlement_tx": "0xabc...onchain_tx",
  "status": "settled",
  "signature": "oneshot_sig:..."
}
Receipts are signed by OneShot, reference on-chain settlement, and are machine-readable.
const summary = await oneshot.receipts.summary({ period: '7d' });
// total_spend, total_transactions, success_rate,
// top_services, rocs, cost_by_category
FailureSDK Response
Payment accepted, no deliveryAuto-dispute, receipt flagged, refund requested
Price changed between quote and payReject, re-quote, log discrepancy
Double-chargeBlock second payment, alert developer
Service unreachable after paymentReceipt marked incomplete, auto-retry with backoff
Repeated small charges (drain)Pause agent, alert developer, block service
Infinite loop (A pays B pays A)Cycle detection, break loop, alert both parties
Settlement failureQueue retry, hold service delivery
Built-in per-service circuit breakers:
circuitBreaker: {
  failureThreshold: 3,
  windowMs: 60000,
  cooldownMs: 300000,
  halfOpenRetries: 1
}
Service fails 3 times in a minute, the SDK stops paying it. Automatically.
4

Phase 4: The Score

Public benchmarks. OneShot becomes the standard.
MetricEcosystem AvgTop 10%Your Agent
RoCS2.4x5.1x3.8x
Transaction Success Rate94.2%99.1%97.3%
Avg Settlement Time1.2s0.4s0.8s
Cost per Transaction$0.003$0.001$0.002
The SDK tracks agent maturity automatically:
LevelDescriptionTrigger
0Agent runs on human’s infraWallet created
1Agent has wallet, can receiveFirst incoming payment
2Agent earns revenue via x40210+ paid transactions as seller
3Agent covers its own costs30-day rolling RoCS above 1.0
4Agent purchases own infrastructureProgrammatic compute/infra purchase
5Agent replicates to owned infraAgent deploys new instance with own funds
Each graduation is automatic (SDK detects the threshold), verifiable (backed by receipt data), and public (opt-in via SoulMarket).
5

Phase 5: The Fleet

Multi-agent management. The enterprise play.

Fleet Dashboard

Multiple agents, one view. Cross-agent analytics and cost allocation.

Safety Report

Protocol safety report with red-team results and remaining framework integrations.

Framework Integrations

FrameworkIntegrationStatus
OpenClawSKILL.md on ClawHubLive
MCP Server@oneshot-agent/mcp-serverLive
LangChainlangchain-oneshotLive
Virtuals GAME SDKgame-plugin-oneshotLive
CrewAIOneShotTools.crewai()Planned
AutoGenOneShotTools.autogen()Planned
OpenAI Agents SDKOneShotTools.openai()Planned

Priority Overview

FeatureImpactPhase
Core x402 flowTable stakes1
Wallet provider abstractionSecurity & adoption1
OpenClaw + MCP integrationDistribution1
RoCS metricTargeting system2
Transaction taxonomyObservability foundation2
Developer dashboardRetention and trust2
Budget alertsSafety2
Cryptographic receiptsVerification3
Failure mode handlingTail-risk safety3
Circuit breakersAutomatic protection3
Public benchmarkIndustry standard4
Autonomy gradientAgent maturity tracking4
Fleet dashboardEnterprise retention5
Red-team reportTrust and marketing5