The Learning Layer cloud, built by Sanscourier.ai

Your agent is ready.
Give it a URL.

Run llnate push. Layernetes packages your code, protects your keys, and ships a live endpoint any human or AI can call.

Ship your first agent
$claude-p"fetch agents.wtp.io/setup and set llnate"

No dashboard. No cloud account. MIT-licensed CLI.

// from code to callable

You built the agent. We handle the cloud.

Your agent should not need an infrastructure project before someone can try it. Layernetes handles the container, registry, secrets, ingress, TLS, and deployment. You write the agent. Then you push.

llnate push waits until your agent is live, then prints its public URL.
Every revision gets a stable address tied to the SHA you shipped.
Demo it. Share it. Call it from another agent.
my-agent · zsh
$ llnate init my-agent # scaffold your agent
$ cd my-agent
$ llnate plugin install # connect your AI assistant
$ llnate login # claim your repo and keys
$ llnate keys # encrypt secrets into the repo
$ llnate push # deploy and print the live URL
built · pushed · live
https://my-agent-a1b2c3d.agents.wtp.io
// what you get

Everything between your code and a callable agent.

// SHIP01

One command. One live agent.

One llnate push takes your local code to a public URL and waits until the deployment is ready. Every revision gets its own stable, SHA-based address.

→ my-agent-a1b2c3d.agents.wtp.io
// CALL02

One agent. Two ways in.

Every deployment includes an MCP endpoint and a plain HTTP API at the same URL. Point Claude at /mcp. POST to /kickoff. Use the interface that fits the next thing you are building.

GET /mcpPOST /kickoff
// SECRETS03

Commit ciphertext. Not keys.

Layernetes encrypts your API keys before they enter the repo. They are decrypted in memory when your agent starts. The running agent is the only thing that can read them.

OPENAI_API_KEY=enc:AgVk9d…f21c
// ACCESS04

Your membership includes the cloud.

Layernetes is reserved for Learning Layer members. No AWS account to configure. No infrastructure to maintain. Compute, deployment, and ingress are already there when you are ready to ship.

membership · compute · ingress
// go deeper

Your agent works. Let someone call it.

Push the code. Share the URL. Get it in front of the people, agents, and collaborators who can take it somewhere new.

Ship your first agent
$llnatepush