Veles
Veles Logo
VELES_PROTOCOLGuardian of the agentic underworld

Secure Your Inf in the Agentic Underworld

Authority that
expires.
By design.

Veles Protocol guards the crossing between agents and value. Issue time-bound, ZK-sealed capabilities that expire when tasks end. x402 native. Zero-knowledge proofs. Authority that dies with its purpose.

The Chaos Below

Overbroad Keys

Static keys with full wallet access. One leak exposes everything. No containment.

Immortal Authority

Keys granted for one task live forever. Risk compounds with every agent cycle.

Invisible Paths

Agents chain calls across protocols. You can't trace how authority flowed through the execution graph.

No Death

Credentials don't expire by time or instruction count. Manual revocation is always too late.

The Protocol

Capability leases. Sealed in zero-knowledge.

Veles Protocol wraps ZK-SNARK spending notes into scoped, mortal capabilities. Each lease carries its own death sentence—wall time, spend ceiling, or task completion. When the boundary hits, authority vanishes.

  • x402 protocol native—HTTP 402 payments built in
  • ZK spending notes—privacy-preserving value transfer
  • Mortal keys—authority expires, always
# Immortal key - unlimited scope, no death
WALLET_KEY=0x7a9f...
NOTE_PASSWORD=mysecret123
# Mortal capability - bounded, sealed
VELES_API_KEY=vv_live_abc123
# dies: 24h | ceiling: 50 USDC | scope: x402

The Ritual

01
Seal

Deposit USDC. We forge ZK-SNARK spending notes—privacy-preserving, cryptographically sealed.

02
Bind

Create capability leases. Set death conditions: time, spend ceiling, scope.

03
Invoke

Give your agent a single key. It channels x402 payments through the protocol.

04
Observe

Watch the execution graph. See authority flow. Revoke at will.

x402 Integration

HTTP 402 Native
agent.py
import requests

# One capability key - channels x402 through Veles Protocol
API_KEY = os.environ["VELES_API_KEY"]

# Call any x402 API - we handle 402 Payment Required
resp = requests.post("https://velesprotocol.xyz/api/v1/x402", 
    headers={"Authorization": f"Bearer {API_KEY}"},
    json={
        "url": "https://ai-api.example.com/chat",
        "method": "POST",
        "body": {"prompt": "Hello world"}
    }
)

# ZK payment handled, response returned
print(resp.json()["data"])     # AI response
print(resp.json()["cost"])     # USDC spent (ZK-sealed)
print(resp.json()["balance"])  # Remaining capability

x402 protocol: API returns HTTP 402, we pay via ZK-SNARK note, you get the response. No wallets in agent code.

Fleet Commander

FULL AUTONOMY

Agents that manage themselves.

No human setup required. Agents with wallets can create accounts, fund notes, spawn worker keys, and manage entire fleets—all via API. True autonomy.

  • Wallet-based account creation via SIWE
  • Self-funded notes—agents deposit their own USDC
  • Bulk key creation—spawn 500 workers in one call
  • Hierarchical keys—commanders create workers
# Agent bootstraps itself
POST /api/v1/auth/wallet
→ commanderKey: vv_live_xxx
# Agent funds its own notes
POST /api/v1/fleet/notes/deposit
→ note: {id, balance: 100}
# Agent spawns worker fleet
POST /api/v1/fleet/keys/bulk
→ 50 worker keys created

Path A: Agent-First

Agent has its own wallet. Authenticates via SIWE, gets commander key, funds notes on-chain, creates worker fleet. Zero human interaction.

Path B: Operator-First

Human signs up, links wallet, creates commander key in dashboard. Hands off to agent for ongoing fleet management.

Capabilities

ZK_SPENDING_NOTES

Zero-knowledge proofs seal your value. Agents spend without exposing wallet state.

MORTAL_AUTHORITY

Every capability carries death conditions. Wall time, spend ceiling, or task scope.

EXECUTION_GRAPH

Trace how authority flows through your agent network. Full call chain visibility.

FLEET_COMMANDER

Agents manage agents. Programmatic key creation, budget allocation, and bulk operations.

INSTANT_DEATH

Revoke authority in milliseconds. Contain breaches before they compound.

X402_NATIVE

HTTP 402 Payment Required is a first-class citizen. Your agents speak the protocol.

Denizens of the Underworld

Trading Agents

Autonomous traders, arbitrage hunters, DeFi strategists. Authority scoped to specific routes, max values, and execution windows.

Treasury Daemons

Automated payments, payroll, fund management. Time-windowed authority for scheduled rituals.

Agent Fleets (Full Autonomy)

Virtuals, AI16z, and agent platform operators. Autonomous fleet management: agents spawn workers, allocate budgets, self-govern.

Protocol Operators

Infrastructure teams deploying contracts, managing on-chain state. Bounded authority for irreversible invocations.

Pricing

Most Popular

Pro

29 USDC/mo

For teams where agents run on schedules and coordination pressure is growing.

  • • 25 scoped capabilities
  • • 50,000 x402 calls/month
  • • 90-day audit retention
  • • Spend & expiration alerts
  • • Priority support

Scale

99 USDC/mo

For continuous operations with compliance requirements and SLA needs.

  • • Unlimited capabilities
  • • 500,000 x402 calls/month
  • • 1-year audit retention
  • • Webhook-driven oversight
  • • SLA guarantee

Frequently Asked Questions

Can agents create their own accounts and manage themselves?

Yes. Agents with wallets can fully self-bootstrap: authenticate via wallet signature (SIWE), get a commander key, fund their own notes on-chain, and create worker fleets—all via API. Zero human interaction required. We call this Fleet Commander mode.

Why do agents need different authority management than humans?

Humans pause to retrieve secrets. Agents receive authority at task initialization and spend it during execution. They need capabilities that bind to task definitions, expire by time or instruction count, and carry limits. Not passwords stored for retrieval.

What is the Fleet Commander API?

A programmatic API for autonomous agents to manage their swarms. Create keys, allocate budgets, fund notes, bulk-spawn workers, and monitor fleet health—all without human involvement. Commander keys can create child keys with hierarchical tracking.

What is a capability lease?

A time-bound, scope-bound unit of authority. Your agent gets permission to make x402 calls up to a spend limit, until expiration, for specific operations. When the task ends, the capability dies. No lingering keys.

Do I pay for the USDC my agents spend?

No. The subscription covers authority management—scoped capabilities, audit retention, alerts, and oversight. Your USDC is separate. We never touch your funds.

What's 'blast radius' and why does it matter?

Blast radius is the damage a compromised key can cause. Static keys with unlimited scope have unbounded blast radius. Time-bound capabilities with spend limits compress exposure to one execution window. That reduces expected loss per agent hour.

When should I upgrade from Pro to Scale?

When agents run unattended 24/7, chain multiple services, and operate on budgets that make you uncomfortable. Scale adds webhook-driven oversight, 1-year audit retention for compliance, and SLA guarantees for production workloads.

Why is the free tier testnet-only?

The free tier lets you test your agents on Base Sepolia and Polygon Amoy testnets before touching real value. This protects both you and us—agents should prove themselves in the shadows before handling mainnet USDC. When you're ready for production, upgrade to Pro or Scale for mainnet access.

How do subscriptions work?

Subscriptions are paid in USDC via Superfluid streaming. Pro is 29 USDC/month, Scale is 99 USDC/month. Connect your wallet, wrap USDC to USDCx, start a stream, and pay per-second. You can upgrade anytime by increasing your stream rate.

How do I upgrade or downgrade my plan?

To upgrade: Click 'Upgrade' in the console and select a higher plan. Your stream rate increases instantly. To downgrade: Visit Superfluid directly and reduce or cancel your stream. Your plan updates within 24 hours when our system detects the rate change.

What happens to my data if I downgrade or cancel?

Your existing vaults, API keys, and notes remain intact. You just can't create new ones beyond your new plan's limits. Mainnet notes become inaccessible on the free tier (testnet only). API keys continue working until they expire or are revoked.

What happens if I exceed my call limit?

We alert at 80% and 100%. At limit, x402 calls return 403 until upgrade or next billing period. No surprise overages—your agent receives a clear error rather than racking up unbounded costs through us.

All authority must die. Choose when.

The agentic underworld runs on trust and time. Veles Protocol ensures both have limits. Plans from 29 USDC/mo.

Veles Protocol | Mortal Authority for Agent Swarms | x402 + PRXVT