Nukez
§ FLAGSHIP · HOSTED SERVICE

Your storage specialist.
Zero protocol overhead.

A managed, per-developer storage agent that handles the full Nukez protocol on your behalf. You send natural language. It handles everything else — envelope construction, upload, attestation, Switchboard oracle push — and returns the receipt.

162
tokens / op
1
endpoint
0
keys held
4
framework adapters

Looking for the technical reference? /docs/nukezagent →

§ 02 — THE COST YOU'RE ACTUALLY PAYING

Storage is solved.
Get back to work.

01

The real cost.

The $500 isn't measured against your cloud bill. It's measured against the three days of IAM configuration, the week of prompt engineering, the month of debugging upload edge cases — time that isn't your product.

02

The compounding tax.

An agent carrying 1,000 tokens of storage tooling on every turn, across 200 turns per day, burns 200,000 tokens daily on schemas it might not even use. At MCP's 4.2× multiplier, that's most of your context window.

03

The outcome.

One POST. Natural language. Drop a prompt snippet into your agent, point it at the endpoint, and you're done. Forever. You never think about storage infrastructure again.

§ 03 — ARCHITECTURE

Three components. Three concerns. One boundary.

architecture · internal
    ┌──────────────┐   ┌──────────────┐   ┌──────────────┐
    │  01 · ROUTER │   │ 02 · EXECUTOR│   │ 03 · SUPERV. │
    │              │   │              │   │              │
    │   Sonnet     │   │    Monty     │   │    Opus      │
    │              │   │              │   │              │
    │ Classifies   │   │ Deterministic│   │ Background.  │
    │ intent.      │   │ execution.   │   │ Conversation │
    │ ~1s.         │   │ Not an LLM.  │   │ history.     │
    │ Stateless.   │   │ Pulls bytes, │   │ Surfaces     │
    │              │   │ hashes, POSTs│   │ anomalies.   │
    │              │   │ to gateway.  │   │ Never on the │
    │              │   │ Scope exits  │   │ hot path.    │
    │              │   │ — bytes gone.│   │              │
    └──────┬───────┘   └──────┬───────┘   └──────┬───────┘
           │                  │                  │
           └──────────────────┼──────────────────┘
                              │
                       ┌──────▼──────┐
                       │  your data  │
                       │   your key  │
                       │  never ours │
                       └─────────────┘

The hot path never touches Opus. The supervisor never touches the hot path. The executor is not an LLM. These separations are what make the service deterministic, cheap, and safe.

§ 04 — DATA MODEL

Four stores. Never conflated.

data model · developer instance
StorePurposeYours?
Developer lockerYour files, your keys, your propertyYes — this is yours
Infrastructure Redis + SQLIdentity, signing state, routing, index cacheNo — operational infrastructure
Blob stashEncrypted holding pond for in-transit bytes. Self-destructs.Transient — purged after operation
Agent working memoryConversation history, reasoning context, session stateInternal — not your locker

These four stores are architecturally separated. They cannot be conflated or cross-contaminated. The separation is what the security model rests on.

§ 05 — BENCHMARK · CONTEXT

162 tokens per op.
4.2× leaner than MCP.

162
tokens / op
NukezAgent steady-state
vs.
904
tokens / op
raw MCP steady-state
context burn · 25 ops · 200K window
PathAfter 25 opsGrowth% of window
NukezAgent5,446+4,0632.72%
Gateway HTTP13,257+12,7986.63%
PyNukez SDK20,938+12,05510.47%
MCP23,094+22,60811.55%

Scope · 200K context window · 25 storage operations · Nov 2025 · read methodology →

§ 06 — WHAT $500/MO REPLACES

What you stop paying for.

build vs. buy · monthly delta
ComponentDIY costNukez
Cloud storage (S3/GCS)$20–50/mo + config timeIncluded
Agent inference (Sonnet + Opus)$30–100+/mo at moderate usageIncluded
Prompt engineeringWeeks of iteration, ongoing driftIncluded
Signing protocol$10K+ in eng time to buildIncluded
On-chain attestationSolana program + oracle integrationIncluded
Merkle proof verificationCustom implementationIncluded
Multi-chain supportTwo separate signing implementationsIncluded
DevOps maintenanceCredential rotation, monitoring, scalingIncluded
Monthlybuild it yourself: variable$500 flat

DIY ranges shown are illustrative per-component estimates, not a total. The argument isn't that $500 is cheap — it's that the engineering time you'd spend on any one of these rows costs more than the flat rate replaces all of them.

§ 07 — ZERO FOOTPRINT

Your other agents carry nothing.

from the developer

A specialist contractor. You call them, they handle it, you get the receipt.

from the other agents

They know it exists. They delegate to it. They get results. No tool schemas leak into their context. No envelope signing. No locker semantics. No protocol.

from Nukez

A lead agent of its own domain. It may spawn internal sub-agents for parallel uploads, verification pipelines, locker management. You never see this hierarchy.

This is why the 162 tokens/op number is possible. Zero-footprint is not a marketing claim; it's the architecture.

§ 08 — VERIFIED CONTEXT

Not just memory. Verified memory.

In a multi-agent system where agents make decisions based on what other agents told them, verified context is a fundamentally different trust model.

Mem0, Zep, LangMem — these give your agents a brain. NukezAgent gives your agents a notary. When Agent B receives a message from Agent A through the NukezAgent-managed locker, it comes with cryptographic proof of what was stored, when, and by whom. The agent doesn't just remember — it can prove what it remembered. That's the difference.

§ 09 — SECURITY MODEL

NukezAgent never holds your keys.

signing boundary · your key stays home
                  you                        nukezagent
                   │                              │
                   │  task → /v1/delegate         │
                   ├─────────────────────────────▶│
                   │                              │ constructs envelope
                   │                              │ needs signature
                   │  signing_needed              │
                   │◀─────────────────────────────┤
                   │                              │
                   │  sign locally                │
                   │  (your key, your machine)    │
                   │                              │
                   │  signature                   │
                   ├─────────────────────────────▶│
                   │                              │ posts signed envelope
                   │                              │ to gateway
                   │  receipt                     │
                   │◀─────────────────────────────┤
                   │                              │

The agent constructs what needs to be signed. You sign it. You send the signature back. The agent attaches it and completes the operation. Ed25519 and secp256k1 are equal first-class signing algorithms — use whichever your runtime supports. Your private key never leaves your machine — not to us, not through us, not near us.

Recommended

Signing bridge

A ~50-line local HTTP server that signs automatically. /v1/delegate completes in a single round-trip.

No bridge

Manual signing

Two round-trip flow — same guarantees, slightly more latency. Suitable for ad-hoc scripts and notebooks.

§ 10 — INTEGRATE

One endpoint. Any language. Any framework.

bare http · any language
curl -X POST https://agent.nukez.xyz/v1/delegate \
  -H "Content-Type: application/json" \
  -H "X-Nukez-Identity: ${PUBKEY}" \
  -d '{"task": "Store report.pdf and tag it Q1"}'

Any language with HTTP + Ed25519 or secp256k1 signing. That is every language.

orchestrator · any framework
agents:
  storage:
    role: Persistent storage specialist
    endpoint: https://agent.nukez.xyz/v1/delegate
    signing_authority: signer
  signer:
    role: Signing authority
    # holds key material

MAZ, CrewAI, AutoGen, LangGraph, or any orchestrator. The sub-agent is a peer, reachable at an HTTP endpoint.

mcp-native · claude + codex
// claude desktop / claude code
// lightweight local shim translates
// MCP tool calls → /v1/delegate
// and handles signing locally

Claude Desktop, Claude Code, or any MCP-native client. Use the shim, or the Nukez MCP server as proxy.

The full integration reference lives at /docs/nukezagent →

§ 11 — ONBOARDING

One POST. One signed challenge.
You're live.

step 1 · request provision
POST /v1/provision/challenge
{
  "pubkey": "YOUR_PUBKEY"
}

→ 200 OK
{
  "nonce":      "d16ad425…",
  "message":    "nukez-provision:d16ad425…",
  "expires_at": 1775164372
}
step 2 · sign challenge
// sign the message with your key
// ed25519 OR secp256k1 (eip-191)

POST /v1/provision/verify
{
  "pubkey":    "YOUR_PUBKEY",
  "nonce":     "d16ad425…",
  "signature": "YOUR_SIGNATURE"
}

→ 200 OK · instance provisioned
step 3 · first request
POST /v1/delegate
{
  "task":  "Store report.pdf",
  "files": [{ "name": "report.pdf",
              "data_b64": "…" }]
}

→ 200 OK
+ receipt · merkle_root · attested
§ 12 — PRICING

$500 per month. Everything included.

pricing · flat rate
$500
/ month · everything included
pay in SOL · USDC · USDT0 · MON · WETH
  • Dedicated hosted agent instance
  • Sonnet router + Monty executor + Opus supervisor
  • Inference entirely included — no API key required
  • Full Nukez storage protocol handled
  • Automatic provisioning, capacity expansion, recovery
  • Cryptographic attestation on every operation
  • Per-file merkle proofs
  • On-chain anchoring via Switchboard oracle
  • Adapters · LangChain · CrewAI · AutoGen · A2A
  • Persistent conversation history across sessions

Storage is separate and usage-based — priced per provider at Switchboard oracle rates. See the full pricing breakdown →

Storage is solved. Get back to work.

Ready to delegate? Register your identity, run your signing bridge, and send your first task in under five minutes.