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.
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.
Looking for the technical reference? /docs/nukezagent →
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.
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.
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.
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ 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.
These four stores are architecturally separated. They cannot be conflated or cross-contaminated. The separation is what the security model rests on.
Scope · 200K context window · 25 storage operations · Nov 2025 · read methodology →
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.
A specialist contractor. You call them, they handle it, you get the receipt.
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.
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.
“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.
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.
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.
agents:
storage:
role: Persistent storage specialist
endpoint: https://agent.nukez.xyz/v1/delegate
signing_authority: signer
signer:
role: Signing authority
# holds key materialMAZ, CrewAI, AutoGen, LangGraph, or any orchestrator. The sub-agent is a peer, reachable at an HTTP endpoint.
// 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 →
POST /v1/provision/challenge
{
"pubkey": "YOUR_PUBKEY"
}
→ 200 OK
{
"nonce": "d16ad425…",
"message": "nukez-provision:d16ad425…",
"expires_at": 1775164372
}// 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 provisionedPOST /v1/delegate
{
"task": "Store report.pdf",
"files": [{ "name": "report.pdf",
"data_b64": "…" }]
}
→ 200 OK
+ receipt · merkle_root · attestedStorage is separate and usage-based — priced per provider at Switchboard oracle rates. See the full pricing breakdown →
Ready to delegate? Register your identity, run your signing bridge, and send your first task in under five minutes.