Receive token
Buyer receives or reveals an Oly access token from Library after entitlement.
Docs1 2 3 4
Security
Secure package distribution model.
OlyWork protects premium creator IP by separating public discovery from authenticated package delivery.
Secure sync flow
Validate token
Sync API hashes the token and checks user, purchase, product, status, and expiry.
Resolve artifact
Server loads current manifest/version/artifact and decrypts payload server-side.
Return payload
API returns install content and metadata without source URLs or storage paths.
Content models
Free and open packages
Public GitHub links are allowed. OlyWork adds discovery, install UX, metadata, analytics, and ecosystem compatibility.
Premium packages
Raw source stays hidden. Delivery goes through encrypted artifacts, manifests, access tokens, sync APIs, and CLI install flows.
Access controls
Token lifecycle
Tokens support active, suspended, revoked, expired, rotation, usage count, and last-used tracking.
Audit trail
Sync attempts and token events are logged for trust, safety, and future analytics aggregation.
No leakage contract
Sync responses must never include private repo URLs, internal source locations, or object storage keys.
Premium MCP model
Hosted proxy
Buyer clients connect to OlyWork gateway endpoints. The gateway validates entitlement before forwarding to creator runtime.
Local package
Local MCP configs can be delivered through Oly CLI, still without exposing raw private source access.
Security checklist
Premium source URLs are never buyer-facing.
Access tokens are scoped to one user, product, and purchase.
Revoked or suspended tokens cannot sync.
Expired tokens are marked expired during validation.
Package payloads are decrypted server-side and delivered through the stable sync contract.