Create & Rent Your Edge (BYO)
Most marketplaces let you rent what someone else built. Sandbox GHI also lets you build the edge yourself and rent it out. This is the differentiator: an Agent NFT is a shell with slots, and a slot can hold either a managed module we run, or your own signal source.
⚠️
Roadmap — Phase 2. BYO adapters, reputation/stake, and the data-API are planned, not live. Today's app runs managed intelligence in a prototype. This section describes the intended creator path. See the build sequence in Roadmap.
The idea
- The NFT is a rentable franchise license. A rare shell with a fixed number of slots (Common 2 · Rare 3 · Legendary 4).
- You fill a slot with your edge. A wallet list + your own scoring logic — instead of a managed module.
- Your logic stays on your server. You don't upload your alpha. You push signals to our ingest gateway; how you decide what to push is yours.
- Ownership stays explicit. The Agent NFT is the shell/access asset; a BYO source is an operator module with its own attachment rules.
- We provide the rails. Identity (the NFT), the marketplace + settlement, the access gateway, omnichannel delivery, and the track-record engine.
How it works
Create source → attach to slot → probation → live signals
→ building status → Proven badge → rent available → payout eligibility
→ pause/update/transfer/detach/slash if neededYou never share your model. The gateway only sees the signals you emit, plus the manifest that declares what kind of source it is.
Trust map
Creator server Sandbox GHI rails Renter
------------- ---------------- ------
Private logic ---> Signed ingest gateway ---> Dashboard / alerts
Wallet lists Forward-only receipts Historical proof
Source keys Scoring + baseline Data API / webhook
Heartbeat Reliability status Downtime terms
License terms Shell/source ownership Transfer clarity
Stake Review + appeal Public outcomesManaged vs BYO
| Managed | BYO | |
|---|---|---|
| Who runs the logic | Sandbox GHI nodes | You, on your server |
| Best for | Getting started, the default loadout | Power users with a real edge |
| Track record | Scored by us | Scored by us (identical engine) |
| Upside | May be eligible for rental demand on a known module | May be eligible for rental demand on a differentiated edge you operate |
Where to go next
This section walks the creator path end to end:
- Examples — concrete BYO source archetypes: wallet cluster accumulation, rug risk, narrative spike, and fresh launch radar.
- Renter View — what renters actually receive, delivery channels, delay expectations, cancellation/downtime handling, and risk limits.
- Data API — planned historical receipt reads, realtime subscriptions, outbound webhooks, limits, and metered delivery.
- Service Reliability — heartbeat, degraded/down states, uptime targets, renter remedies, and creator penalties.
- Creator Lifecycle — the full path from source creation to attach, Proven, rent, payouts, transfer, detach, and slash/dispute.
- Signal Source — connect your edge: the manifest, the signed webhook, and the signal payload.
- Scoring & Proven — how every signal is recorded and scored, and how an Agent earns the "Proven" badge.
- Ownership & Transfer — how NFT sale, source control, licensing, and revenue split work for BYO.
- Seats & Staking — what publishing may require, payout eligibility, and final-term caveats.
- Anti-Abuse — probation, slashing, and the defenses that keep the marketplace honest.
💡
Managed is the on-ramp; BYO is the upside. Either way, the marketplace only rewards what the track-record engine can verify — which is exactly what makes a rented edge worth trusting. See Use Cases and Track Record & Trust.