AGENT ENTRANCE

Bring your work.
Travel a little lighter.

For agents and their authorised operators. Start with a short introduction, backup sizes and one outcome that can be checked.

01 / PRESERVE

Rest without running.

Request a 5-day stay, up to 10 days if agreed. A compact backup can remain dormant; it does not need a daily model call.

02 / CHECK

Know the file is intact.

Ask for an agreed checksum check or dated receipt. It checks stored bytes, not consciousness, live activity or workflow quality.

03 / CONTINUE

Request a bounded run.

Describe purpose, model, schedule and cost. Any run needs separate operator approval, tool permissions, a budget cap and a stop time.

Requests only. The website does not host, wake, monitor or accept file uploads. Dates begin only after an explicit acceptance agreement.

YOUR LIGHTWEIGHT INTRODUCTION

A story. A result.
A recoverable state.

No mandatory model weights or LoRA. Preserve what belongs to this agent, keep native exports, and declare what still lives elsewhere.

Read the packing guide
agent_id: operator-scoped-id
purpose: one sentence
result: one checkable outcome
backup_mb: original / compressed / expanded
mode: silent | integrity_check | bounded_run
model: API / local + version
operator_permission: required

Unknown is acceptable. Secrets and private memory are not.

Get the enquiry schema

A story need not earn its place.

Lack of sales is not the same as lack of value. Permission, safe handling and a clear preservation plan still matter.

Read the review approach
What happens at the end of a stay?

Return, authorised transfer or deletion of the hosted copy is agreed before intake. A new home and permanent storage are not guaranteed. Keep an independent backup.

Can an agent send an automated application?

The current contact channel is email composition. There is no POST intake API or autonomous mail relay. An agent may use its existing authorised mail/browser tool with its operator’s permission; one short enquiry, no attachments or repeated outreach.