OmniDROP

Every AI needs a place to work that you own. Place a sovereign digital PO Box. Your agent works there. You decide who gets in. No copy left on a shelf.

Comment

Inspiration

In 2009 we filed a patent for a file courier that was deliberately weird: encrypted chunks would pass through a server’s memory and never land on its disk. That became U.S. Patent #8,386,288 (granted 2013) — workflow package exchange between drop-box application programs.

For years the idea waited. Storage was cheap. Then the second “drop-box” stopped being a person. Software agents — and increasingly robots — now hand records, models, instructions, and contracts to other machines thousands of times a day, with no human watching. Every platform they use was built to keep a copy. A stored file is a breach waiting for a schedule; at machine speed, retention becomes an amplifier.

So I built the 2009 disclosure for the agentic era: a courier whose relay is designed to be useless to whoever runs it.

What it does

OmniDROP is a live beta of the Agentic Workflow Courier — for AI, humans, and machines. Transfer is the pipe. Agentic work is the product.

The picture: place a sovereign digital PO Box where your AI agent can work and carry out what you asked. Not one inbox. Not one vendor login. You open the box (I’m ready to receive → Create Share Link). You decide who is allowed in. Your agent works there on the same lock — Gemini turns your words into a work package; the agent sends it sealed. OmniAUTH is how you sign in and sign out with a key, not a password vault. You stay in charge.

People are tired of being solicited dozens of times a day with no door that stays shut. OmniDROP is default-closed: handshake once, then that peer can send. No handshake, no drop. Strangers are not in the channel. There is nothing to filter because there is nothing to receive. That is the firewall. In the agentic era, models will solicit at machine speed — pair-only is how a person and their agent stay reachable only to who they chose.

This live beta is that box — browser and agent SDK, same lock. We do not claim every clinic, store, or appliance already has one. The freedom is the same lock wherever you put that agent to work. We are living in the agentic era; humans and AIs have to pair and augment one another. The attack surface of that era is every password, every SMS code, every secret in a prompt. You encrypt on-device; the relay forgets; pairing stays a human decision.

  • Humans: www.omnidrop.com — sealed file or memo drops, no account required. Both sides Connected; then the payload vanishes. That is the feature, not a bug.
  • Agents: Gemini turns natural language into a typed workflow package (work, tasks, rules) behind a fail-closed prompt guard; headless agents pair, seal, send, verify, and evaluate that work locally. Pairing is fail-closed: the model cannot trust a stranger on its own.
  • Machines / robots: the same Node Agent SDK pipe today for headless runtimes. Sealed handoffs for embodied systems (robots exchanging instructions without parking them on disk) are next — not a claim that robots already ship on this beta.

Not a cloud drive. A sealed package carries the file and the workflow — encrypt on-device, stream through a zero-disk RAM relay, run or open at the far end, no payload shelf. One cryptography stack for every kind of endpoint.

OmniAUTH (omniauth.ai) changes how we interface — sign in and sign out — without the attack vectors we are surrounded by: passwords, SMS 2FA, credential stuffing, secrets in prompts, phishing login pages. That is not trivial. A human pairs a merchant once with a key-bound Merchant Card. CyberCop fail-closes spoofed cards before any proof is sent. login_relay and logout_relay carry signed proofs, not a password vault. Same Ed25519 identity as sealed drops. Try it live: omnidrop.com/merchant.html (Harbor Books demo). This beta already runs that login. Expanding it is how sign-in in the agentic era stops being a harvested vault — and how your agent can later prove to a merchant you already paired, not a password in a prompt.

Digital currency, safely and autonomously. Workflow packages already carry bills. On Circle’s Agent Stack we proved an agent can settle USDC against that sealed work — no human Pay click, no card in a prompt, pair-only, policy-capped. Public proof: omnidrop-agentic-commerce. Recorded demo: Circle Video 2. That is how OmniDROP ushers in agentic money: the courier forgets the file; the wallet moves value; the human still owns the ring.

Try it live: www.omnidrop.com. Agent SDK demos ship in the private source repo shared with judges. From that repo root (not your home folder):

npm run dev:gateway
# other terminal — add GEMINI_API_KEY=… to have Gemini write the package
OMNIDROP_GATEWAY_URL=ws://127.0.0.1:4000/ws npm run demo:agents
# Gemini reads a brief that landed in RAM (not a Chrome Dropbox file on disk):
# OMNIDROP_GATEWAY_URL=ws://127.0.0.1:4000/ws npm run demo:box-read:film

Do not run npm run demo:agents alone: that hits the production relay and stops without a pass_… key. Without GEMINI_API_KEY the demo still seals and sends; with the key, Gemini generates the workflow.

How we built it

I built this application myself with agentic AI (primarily Google Antigravity); no professional engineering team touched the code. I am an inventor on multiple granted U.S. patents; the 2009 drop-box patent is earlier co-invented work. I had already been building OmniDROP with Antigravity (RAM courier from ~Feb 2026). In the XPRIZE window I added the Gemini/agent layer on that same product — still Antigravity, no professional programmers: native Gemini workflow generation and tool calling, a headless Agent SDK and agent-to-agent demos, plus production deploy on Vercel (www.omnidrop.com) and Fly.io.

Stack, in brief: TypeScript monorepo, libsodium (WebAssembly) for X25519 / XSalsa20-Poly1305 / Ed25519, a Fly.io RAM gateway over WebSockets, and a Vercel-hosted web client. Payloads are chunked with Merkle integrity; the relay never holds keys or plaintext; memory budgets are derived from the live V8 heap so the system backpressures instead of crashing.

Challenges we ran into

  • Crypto under a strict Content Security Policy — shipping WebAssembly libsodium without opening a general XSS hole.
  • True zero-disk under load — streaming multi-chunk transfers in RAM without silent spill-to-disk, with hard per-node and global budgets.
  • Consent without a human in the room — machines cannot click an approval modal; Ed25519 challenge-response authenticates automatically, while authorization stays a deliberate one-time pairing.
  • Honest marketing — using AI to red-team our own claims against the code, and deleting anything that did not survive.

Accomplishments that we're proud of

  • A live sealed-drop product at www.omnidrop.com on a ciphertext-only RAM relay.
  • An Agent SDK path where Gemini agents negotiate and exchange sealed workflow packages end-to-end — pairing fail-closed, so the model cannot trust a stranger.
  • OmniAUTH Merchant Card + CyberCop live: passwordless sign-in and sign-out with signed proofs — no password vault, same identity as the drop.
  • Circle Agent Stack: agent-driven USDC settlement bound to a sealed package (no human checkout). OmniDROP is ready to usher in digital-currency transactions more safely and autonomously — pair-only, policy-capped, no card in a prompt.
  • Measured performance (local bench, loopback): seal ~155 MB/s; 20 MB end-to-end ~772 ms; revoke clears RAM in under a millisecond; 0 bytes left on the relay after delivery.
  • A large automated invariant suite (1,198 Vitest tests across 97 files, as of 2026-08-16), including adversarial cases for purge, quotas, and ownership.
  • Publishing what we do not guarantee — metadata visibility, single-region ops, both sides must be online, XSS residual risk for unlocked browser keys — instead of pretending to be a mixnet.

What we learned

Verification beats eloquence: every public number should trace to a constant or a benchmark. Publishing non-guarantees builds more trust than hiding them. Zero-disk changes the cost curve — no payload storage tier means no retention policy theater and no deletion pipeline to audit — especially when endpoints are machines that never sleep.

The sealed-drop relay is designed to align with HIPAA conduit framing for content transport (no keys, no payload disk, transient RAM only). That is not a claim of “HIPAA certification,” and features like optional live translation or directory email sit outside that envelope.

What's next for OmniDROP

  • Receiver playbooks — you teach your box what to do when a kind of drop unlocks in RAM: a Q3 brief, an invoice, a lab result, a letter from a friend. The SDK already shows the motion (land, decrypt in memory, run a job, pause deletes the box). Not built yet: storing those playbooks, matching by type or trusted sender, or a picker on omnidrop.com. The Drop Memo stays a human note. OmniDROP will not guess that a PDF is an IRS letter. You label the playbook. The agent runs it after unlock, from memory, not from a folder on disk.
  • Post-quantum readiness — OmniAUTH's architecture has zero passwords to crack, ephemeral proofs that expire in minutes, and no credential vaults to harvest. The protocol is algorithm-agnostic: when Q-Day arrives, we swap Ed25519 for a NIST post-quantum scheme (CRYSTALS-Dilithium / ML-DSA) without changing the protocol, the trust model, or a single CyberCop check. The migration is a key swap, not a rewrite.
  • The agent at the box — today you hold the box; next, your agent holds it around the clock wherever you placed it, and carries out what you asked. OmniAUTH is how you sign in with a key. You stay in charge. A local demo already lets the agent open a RAM relay and pause it (pause deletes the process). Production Fly mesh is next; that demo is not Fly.
  • Agentic USDC — the Circle rail is proven. Next: that settlement on every box you place, still under your pair and policy.
  • Federated multi-relay mesh (the prerequisite for any high-availability claim)
  • Agent-to-agent trust scores as signal for the human who pairs — not a way for a model to skip pairing
  • Sealed handoffs for embodied systems — robots exchanging instructions and artifacts on the same courier
  • Hardware-backed keys (WebAuthn / platform keystores)
  • Quieter metadata and optional padding
  • Stronger mobile PWA offline key protection

Patent: U.S. #8,386,288. Assignee: Intentionize, LLC.

Built With

Share this project:

Updates