Skip to content
Docs / Connect a function

Docs

Connect a function

Expose an existing function through EasyRemote. The current implementation uses Python; the connection model is function-level, not Python-only.

Register one owned Python function as a typed provider binding. Its implementation and dependencies stay with the Provider; declared inputs and returned output cross the call boundary.

Source workspace · paired Runtime

Live function setup needs a complete, compatible source workspace, a paired Runtime, and a compatible Hub. Technical Alpha offers guided help, not permission to read the public repositories.

Request Technical AlphaCheck the setup requirements
All connection paths

Step 0

Prepare the Runtime first.

A function Provider depends on a paired, running Runtime. Complete the Runtime preflight before installing or starting EasyRemote on the provider machine.

Open the Runtime guide

Run this guide

Outcome
Register one owned Python function as a typed provider binding. Its implementation and dependencies stay with the Provider; declared inputs and returned output cross the call boundary.
Before you run it
Prepare compatible EasyRemote, EasyNet-Cli, and EasyNet-Axon sibling source checkouts, a compatible Hub, and a paired, running local daemon. Technical Alpha provides guided setup. Reading public source does not install the required SDK dependency chain or prepare this runtime environment.
zsh · provider preflight
easynet runtime status
cd "/absolute/path/to/easynet-workspace/EasyRemote" &&
  uv sync --frozen &&
  uv run easyremote doctor
provider.py · save this function boundary
from easyremote import ComputeNode

node = ComputeNode()

@node.register
def quote(quantity: int) -> dict:
    return {"quantity": quantity, "total": quantity * 19}

node.serve()
zsh · start the Provider
# Save the previous block as provider.py, then keep this terminal open.
uv run python provider.py
zsh · verify from a second terminal
# In a second terminal:
easynet ability list --node local --format json

Verify the result and boundary

Success looks like
`easyremote doctor` first confirms the local transport. While `provider.py` remains running, `ability list --node local --format json` must show the Provider binding in the local catalogue.
Still separate
This guide assumes a complete, compatible development workspace; a clean-machine install from public package registries has not been verified. Local activation is not Realm visibility; the owning Runtime/product must still confirm directory publication before another Agent can discover it.
Request guided function setup