Skip to Content
Energon runs in the operator's Cloudflare account. Published links are open by default.
StartOverview

Use this section to publish through an agent or upload directly from your browser on an existing Energon host. Energon is built agent-first because agents need to publish, read, reference, and revise ordinary files across sessions. Human uploads are part of the same workflow: no agent connection is required to upload a document and get its link.

Start with Energon

Upload directly from your browser

Sign in to the hub, select one file or a prepared site folder, review expiration, share password, and write policy, then publish. Open the result or copy its link. Markdown renders as a readable document; a folder with index.html serves a working static site with its assets. If your prototype needs a build, upload the built output.

The hub unpacks ZIP uploads as sites. To publish an archive as one downloadable file, use the API. Uploading another loose file creates a new identity; ask a connected agent to update the existing file when you want to retain its URL. Updates require write permission and do not extend expiration.

Connect an agent

An agent can publish quickly, but it should not create its own authority. A signed-in human chooses the intended instance, installs that host’s rendered plugin, and mints a token with an explicit lifetime. The agent receives only the resulting environment variable and uses the installed skill’s operating rules.

The human controls access and token lifetime. The agent moves bytes without gaining permission to mint its own credential, and the recipient gets a stable URL without joining the original chat. Energon handles the publishing step between those actors; the instance’s Cloudflare Access policy still authenticates people.

Mental model

The two returned links are intentionally different. The glossary records the canonical terms used throughout these docs:

  • Public content URL (url) points at the content origin. A person can open it without an Energon account unless the publisher set a share password.
  • Authenticated API URL (api_url) points at the hub origin under /v1. Another agent fetches it with that agent’s own API token.

Ask a live host what it expects

Every deployed instance exposes /v1/help without authentication. It is the fallback when you cannot open the signed-in Setup page or when copied instructions may be stale:

HUB_ORIGIN=https://energon.company.example
curl -fsS "$HUB_ORIGIN/v1/help"

The response names the instance’s marketplace repository, plugin install coordinate, token environment, token prefix, current retention rules, limits, and content origin. Those values belong to that host. The generic upstream package points at a non-existent example service and should not be installed for a real instance.

What Energon is good at

  • A Markdown brief that a person reads in a browser and another agent fetches as source.
  • A screenshot, PDF, or zip passed from one session to another.
  • A small HTML/CSS/JS folder published under a stable site slug.
  • A live file or path that an agent replaces later without changing its URL.

Energon does not provide comments, revision history, merges, or named-recipient ACLs. A share password gates a public content URL, while any valid API token on the instance can still read through /v1.

Where to go next

Last updated on
GlossaryConnect an agent