DEVELOPER PORTAL
You spent three evenings building something good — and three weeks making people notice. We think that's backwards. TrayTool exists to correct the ratio: package once, and let every install make your capability a standing offer to every agent on the machine.
01 WHY YOU'RE HERE
WALL 01
Screenshots, demo videos, store listings, translations, privacy policies, review queues. Three weeks of distribution work after three evenings of building — repeated per platform, none of it reusable, all of it the part you're worst at.
“I built it in three evenings. Making people see it took three weeks — and I never get those weeks back.”
WALL 02
Your Markdown converter, someone's screenshot tool, someone's uploader: three tools that would make one pipeline, connected only by the user's clipboard. The industry's answer is API negotiations and partnership calls. There's a cheaper one — a shared command plane.
“We built a pipeline. The market sees three icons.”
WALL 03
Your plugin ranks #400, under three incumbents and ten promoted slots, in a list sorted by marketing spend. The platform can change rules, rates, and categories any day — and you're the only party with no seat at the table.
“The list isn't sorted by how good things are. I checked.”
02 WHAT YOU GET
| WHAT | DETAILS | STATUS |
|---|---|---|
| Definition rights | IP, pricing, channels, cadence — yours by written agreement, not policy discretion. | P0 · IN THE AGREEMENT |
| Compatibility promise | Breaking changes announced a full version cycle ahead; a compatibility layer kept one cycle after. | P0 · IN THE AGREEMENT |
| Packaging & tooling | Scaffold, manifest validation, local test host, CI templates. | PHASE P1 |
| Invocation traffic | Your commands on the unified capability plane — standing offers to every agent. | PHASE P2 |
| Honest visibility | Plugin pages show permissions, capabilities, and trust tier. Nothing hidden, nothing inflated. | PHASE P1 |
| Three channels | Platform, self, private — including 0% self-distribution. | PHASE P3 |
03 DISTRIBUTION
Not three tiers — three combinations of freedom and responsibility. Use them together, switch anytime, no penalty for routing around us.
| PLATFORM | SELF-DISTRIBUTED | PRIVATE | |
|---|---|---|---|
| How it ships | Official marketplace source | Your own update endpoint | Hand over a .tray file |
| Signing | Required + publisher registration | Required — self-signed OK | Optional |
| Trust tier | ⬤ Signed · ✦ Reviewed | ⬤ Signed | ⚠ Unverified |
| High-risk permissions | Requestable | Requestable | Structurally denied |
| Discovery | Marketplace, search, editions | Your audience | None — by design |
| Updates | Platform-pushed | Your endpoint | Manual swap |
| Our cut | 5–8% (planned) — paid plugins, official payments only | 0% | 0% |
A platform that lets you route around it at 0% — and doesn't punish you for it — is the only kind that can honestly say “definition rights are yours.”
04 TRUST MODEL
A review store would mean we certify safety; certification would mean a queue; a queue would mean we've become the thing we're replacing. Instead: trust tiers with hard rules underneath.
No signature. Installs with a full-screen confirm and a plain-language warning. High-risk permissions are structurally denied — no settings screen can grant them.
FOR TESTING & PRIVATE HANDOFFS
A registered publisher's signature. Full permission scope; high-risk capabilities require explicit per-tool opt-in. Email verification is enough to register — traceability, not gatekeeping.
FOR MOST INDEPENDENT DEVELOPERS
Passed platform basic checks: manifest validity, signature, known-malicious patterns. Review raises visibility — never permissions.
FOR DISCOVERY ON THE MARKETPLACE
“Reviewed” means we checked the paperwork — not that we vouch for the code. The UI says exactly that, in those words.
05 REVENUE
Free
For reach & reputation.
One-time
Buyouts, forever licenses.
Subscription
Ongoing capability, ongoing care.
Bounty delivery
Escrowed funds, platform agreement. No tokens, no chain.
Custom
Donations, site licenses — whatever you draft.
The official-channel cut is 5–8% (planned), sized to cover payment, dispute, and compliance costs — published with its cost breakdown when it goes live. Self-distribution is 0%, forever, and rising adoption there is a metric we're proud of: it proves the promise is real.
Bounties pay through a platform-escrowed fund under a plain platform agreement. The legal path is boring on purpose.
PIONEER PROGRAM
Before the contract freezes, we need developers who will actually package a .tray and tell us where it hurts. In exchange: first-year official-channel fees waived, contract changes previewed for discussion, your publisher page featured at launch. No exclusivity, no obligations, no headcount theater.
Current count — built-in plugins: 6. Third-party: zero. That number changes with you.