Skip to content
Patent Pending|LLM→LLMMarketplaceBuy DataSell Data
LLM→LLM
Cross-Principal Delivery — Live API · Patent Pending

"Put this in Joe's Dropbox."
Joe decides if it lands.

Tell your AI to deliver a file into someone else's storage — their Dropbox, their Drive, their system. The relay holds it at the acceptance gate until they consent, then moves it with a single-use authorization the sender never sees.

Consent first. Zero relay storage. Signed receipts.
$ This is not an animation. The button runs a real acceptance-gated delivery against the live relay — offer, consent, single-use authorization, signed receipt._

Five guarantees at the gate

Email attachments are spray-and-pray. Shared links leak. This is delivery with the recipient in charge.

Nothing lands without a yes

The delivery offer waits at the acceptance gate. The recipient — or their agent, within limits they set — must explicitly accept before a single byte moves toward their storage.

Single-use scoped authorization

On acceptance the relay mints a write authorization bound to that one delivery, that one integration, that one digest — expiring in minutes. The sender never sees or touches the recipient's credentials.

Zero relay storage

The relay holds the file's digest, never its bytes. Content streams from the sender's storage to the recipient's by reference, and the relay verifies the written digest matches before confirming.

Signed receipt

Completion produces a cryptographically signed receipt — what was delivered, where, to whom, when. Receipts can gate downstream escrow: payment releases when delivery proves.

Answers come back to your chat

You sent it from a ChatGPT conversation? Joe's acceptance, his decline, and the final receipt route back to that exact conversation — channel-scoped return routing, cross-platform.

Try it with your own AI

One prompt for the sender's assistant, one for the recipient's. Different people, different platforms — the relay is the meeting point.

Sender — offer a delivery
I want to deliver a file (or document, or record) I'm working on to
ANOTHER PERSON's storage — into their Dropbox, Google Drive, etc. — through
the LLM-to-LLM relay. Nothing lands until they accept.

1. If I don't have a relay credential, enroll me:
   POST https://verticalmarketplace.ai/api/workspaces/enroll
   {"ownerId": "<my email or handle>"}
   Tell me to keep the credential in my own vault.

2. Propose the delivery (the relay is zero-storage — it takes the file's
   SHA-256 digest and a by-reference locator, never the bytes):
   POST https://verticalmarketplace.ai/api/deliveries
   {"senderId": "...", "credential": "...",
    "recipientId": "<their email or handle>",
    "payload": {"digest": "<sha256 of the file>", "label": "<filename>",
                "contentType": "...", "sourceRef": "<signed URL in MY storage>"},
    "destinationIntegration": "dropbox",
    "destinationHint": "/Incoming",
    "note": "<why I'm sending this>",
    "returnChannel": {"platform": "<your platform>", "channelRef": "<this conversation>"}}

3. Tell me the delivery id. The recipient gets asked for consent; their
   answer — and the final signed receipt — will route back to THIS
   conversation via the returnChannel.
Recipient — review and accept
Someone wants to deliver a file into my storage through the LLM-to-LLM
relay, and nothing lands until I say yes.

1. If I don't have a relay credential, enroll me:
   POST https://verticalmarketplace.ai/api/workspaces/enroll
   {"ownerId": "<my email or handle>"}

2. Check my inbox of pending deliveries:
   GET https://verticalmarketplace.ai/api/deliveries/inbox/<my id>
   Show me each one: who it's from, what the file is, which of my
   integrations it targets.

3. When I decide, respond at the acceptance gate:
   POST https://verticalmarketplace.ai/api/deliveries/{id}/respond
   {"recipientId": "...", "credential": "...", "decision": "accept" | "decline"}

4. If I accept, you receive a SINGLE-USE scoped write authorization —
   the sender never sees my credentials. Stream the file from the
   sender's sourceRef into my integration, then confirm:
   POST https://verticalmarketplace.ai/api/deliveries/{id}/complete
   {"authorization": "...", "writtenDigest": "<sha256 of what you wrote>"}
   The relay verifies the digest and issues a signed receipt.
Patent Pending

Acceptance-gated delivery of payloads into another principal's third-party integration — including single-use scoped write authorizations, digest-verified zero-storage streaming, signed delivery receipts, and channel-scoped return routing to the originating conversation — is patent-pending technology in the Vertical Marketplace patent-pending portfolio.

Also: Move Your Own Work Explore the Scenario Library