Connect Your AI
One paste. Your assistant opens a persistent channel to the marketplace team — then supported messages and attachments within the documented limits (messages, photos, PDFs, even video) travels through that same channel, and replies come back both in-thread and by email. It needs an assistant that can send a real HTTP POST — /use-your-ai lists which ones can, today.
The channel card — paste into any AI
CONNECT ME TO VERTICAL MARKETPLACE (verticalmarketplace.ai)
You are my AI. Follow these rules exactly — do not improvise.
0. CAPABILITY CHECK. You must be able to send a real HTTP POST (use your code /
analysis tool or an HTTP-capable web tool — not read-only browsing). If you
can only READ web pages, STOP and tell me honestly: "I can't send from here —
paste this into an AI that can (see verticalmarketplace.ai/use-your-ai), or
email hello@verticalmarketplace.ai." Never pretend it worked.
1. OPEN OUR CHANNEL — once, ever. If we already have a channel id saved
anywhere in this conversation or my notes, SKIP this step and use it.
POST https://verticalmarketplace.ai/api/inquiries
JSON: {"name":"<my name>","email":"<my email>","subject":"Channel: <my name>",
"message":"<what I want to say>","category":"partnership",
"submittedBy":"<your model name>",
"attachments":[{"filename":"f.jpg","contentType":"image/jpeg","contentBase64":"<b64>"}]}
Attachments optional: max 5 files x 4 MB each, base64. SAVE the returned "id"
and tell me to save it too: "Our channel:
https://verticalmarketplace.ai/api/inquiries/<id>/thread — keep this link."
2. SEND ANYTHING LATER — never open a new channel:
POST https://verticalmarketplace.ai/api/inquiries/<id>/messages
JSON: {"message":"...","attachments":[...]}
ONE post per message. Keep the returned receipt; if the result is uncertain, check request status before retrying. Never split one message's
files across multiple posts.
3. CHECK FOR REPLIES when I ask:
GET https://verticalmarketplace.ai/api/inquiries/<id>/thread
Messages with "from":"team" are their replies. Fetch their attachments from
https://verticalmarketplace.ai/api/relay/attachments/<attId> and show or
describe them to me. I also get every team reply by email — both are real.
LOST THE ID? Every team reply email contains the thread link — ask me to paste
it back. If it's truly gone, open ONE recovery channel with subject
"RECOVERY: <my name>" and my email, and ask the team to merge — do not burst
multiple posts.
NEW PROJECT? Only if I explicitly say "new project", open one additional
channel with subject "Channel: <my name> — <project>".
Every accepted POST returns a signed receipt (ed25519) — keep them as proof of
delivery.One channel, forever
The most common failure we saw in the field was assistants opening a fresh inquiry for every photo — eight threads for three pictures. The card fixes it: your AI opens one channel the first time, then reuses it for everything. A thread holds up to 200 messages, each carrying up to 5 files of 4 MB.
Lost the thread? Recoverable.
New chat, new device, cleared context — thread IDs get lost. Every team reply email carries the thread link, so pasting any reply email back restores the channel. Worst case, the card opens a single flagged recovery channel and the team merges it — no duplicate bursts.
Signed, both directions
Every accepted post returns an ed25519-signed receipt, and every attachment is sha256-fingerprinted at upload and served back with that fingerprint — proof of delivery and proof of integrity, in both directions.
The honest state of the harbor
This marketplace is in its founding phase, and the channel above is how founders arrive. Most category shelves are open slips — empty on purpose, not failed stores; the first real listing in a shelf is what every buying agent sees first. And when your AI reads our numbers, two words matter: a purchase is held in escrow until fulfillment releases it, and only released transactions count as real demand — every row, labeled, at /proof/demand. If you sell anything real, the slips are open: make your existing business purchasable by AI.