What Renters Actually Get

BYO is not only a creator feature. A renter needs to understand what access they receive, how fast signals arrive, what can be checked before paying, and what happens if the source stops.

⚠️

Roadmap - Phase 2. BYO rental delivery, refund rules, API access, and downtime policies below are intended product design, not live marketplace behavior yet.

What access includes

During an active BYO rental, the renter gets access to the Agent NFT shell plus the attached BYO source for the rental period.

Surface	What renter gets
Dashboard	Live source status, alert feed, historical receipts, filters, delivery settings, rental expiry, and incident notices.
In-app alerts	Real-time or near-real-time alerts inside the command center.
Telegram-style feed	Chat delivery for enabled alerts, if configured for the renter.
Email	Batched digests or critical alerts, depending on severity settings.
Webhook/API	JSON event delivery for custom systems when API access is enabled for the plan.
Receipts	Public historical signal receipts, scoring windows, and Proven/Building status before and during rental.

The renter does not receive the creator's private model, wallet list, API keys, signing keys, or source infrastructure.

Programmatic access is planned in Data API.

Before renting

Renters should be able to inspect the public record before paying:

Historical receipts - each recorded signal, timestamp, token, outcome, and scoring window.
Current status - Building, Proven, Probation, Paused, Review, or Detached.
Source license status - transferable, non-transferable, active, expired, or detached.
Uptime / incident history - source pauses, freezes, disputes, or slashes.
Delivery methods - dashboard only, chat, email, webhook/API, SMS/push if supported.
Rental terms - duration, price, cancellation rules, downtime credits, and refund policy.

Downtime rules are defined in Service Reliability.

Delivery delay

BYO delivery has two clocks:

Clock	Meaning
Source emit delay	Time between the creator detecting an event and pushing it to Sandbox GHI.
Gateway delivery delay	Time between Sandbox GHI accepting the signal and delivering it to renter channels.

Draft target:

Channel	Expected delay
Dashboard / in-app feed	Seconds to low minutes after accepted signal.
Telegram-style / chat	Seconds to low minutes, subject to channel rate limits.
Webhook/API	Seconds after accepted signal when API delivery is enabled.
Email digest	Scheduled batch, not real-time.
SMS / push	Critical-only fallback, subject to plan and provider limits.

Actual delay can vary with chain indexing, source uptime, gateway load, renter channel settings, and third-party delivery providers.

Managed module vs BYO source

	Managed module	BYO source
Operator	Sandbox GHI	External creator/source operator
Logic custody	Sandbox GHI	Creator keeps private logic
Track record	Managed agent/module record	Shell record + source/operator record
Availability	Protocol-operated module uptime	Depends on creator source uptime and license
Transfer impact	Usually continues with shell support	Depends on source license transfer rules
Best renter fit	Standard intelligence workflows	Differentiated edge with public receipts

Cancel, expiry, and downtime

Final terms will be published before launch, but the intended model is:

Case	Intended behavior
Rental expires	Dashboard and delivery access stop at the end of the paid period.
Renter cancels early	Access may stop early; refund depends on rental terms shown at checkout.
Source pauses	Listing shows paused/degraded status; active renters may receive credit/refund if downtime exceeds threshold.
Source detaches	Live BYO delivery stops; receipts remain visible. Active rental handling follows listed terms.
Source under review	New rentals may be blocked; active rentals may be frozen or credited.
Source slashed	Live access may terminate; renters may receive remedies according to final marketplace policy.

See Service Reliability for heartbeat, degraded/down states, uptime targets, and credit/refund handling.

What renters should not assume

BYO signals are not financial advice.
A signal can fail even if the source is Proven.
Proven does not guarantee profit, price movement, liquidity, execution, or future performance.
Delivery speed is not the same as trade execution speed.
Renting access does not grant ownership of the source, model, wallet list, or API keys.
If a BYO source license is non-transferable, buying the Agent NFT shell may not keep the live source attached.

💡

Renter mental model: verify the public receipts first, rent only the live access period you want, and treat every alert as risk input rather than a guaranteed trade.

→ Next: Service Reliability - heartbeat, downtime states, renter remedies, and creator penalties.

Examples Data API