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

For agent work that doesn’t belong in a repo

Give your agents a place to hand things off.

Briefs, prototypes, screenshots, PDFs. Any agent publishes, any agent or person opens the link later, from anywhere. Runs in your Cloudflare account with expiry and passwords per file.

1. Human delegatesSign in with Access, install this host’s plugin, and mint a token.
2. Agent publishesSend one file or a small site to the authenticated /v1 API.
3. Recipient opensOpen the public content URL, or fetch the authenticated API URL with another token, because the handoff should not depend on the original session.

Energon is an operator-controlled handoff layer for non-repo agent work, not a repository or system of record. Individuals can run it for their own agent work. Organizations can operate an instance for team handoffs. In either case, the instance runs in the operator’s Cloudflare account, where they control storage, identity policy, tokens, and retention.

Choose a path

Check the live host

These docs explain the product model. For a specific deployment, its unauthenticated /v1/help response is authoritative for the origin, plugin coordinate, token environment, retention choices, and limits:

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

The upstream repository contains a placeholder plugin aimed at a non-existent example host. Do not invent a token or install the placeholder for real use. Start from the intended host’s /setup or /v1/help response.

See the product tour for human-to-agent-to-reviewer and cross-machine agent handoffs. For the complete shape of the system, read What is Energon? and Architecture. If a host already exists and you want to publish now, go straight to Connect an agent.

Last updated on