Skip to content

Reuse one validated pricing rule

A caller requests a bounded quote while the rule implementation remains with its owner.

All source casesInspect the pinned project

A recorded local call, from discovery to result.

One paired local Runtime registered the gallery pricing function. The CLI discovered its entry, invoked it, and read its terminal ledger record.

Request

{
  "seats": 48,
  "plan": "team",
  "annual": true
}

Returned result

{
  "billing_period": "annual",
  "discount_cents": 336960,
  "plan": "team",
  "seats": 48,
  "subtotal_cents": 2246400,
  "total_cents": 1909440
}

Recorded terminal state: COMPLETED

One physical host. Local invocation. This is a historical development run, not a live service check or evidence of a second Agent or cross-device call. The ledger reported receipt verification; this summary is not an independently verifiable receipt bundle.

Inspect the recorded fields (JSON)

The problem

A pricing rule works, but every new consumer is about to copy its source or rebuild it as another service.

What gets published

Publish the validated quote function as a typed Ability.

What stays local

Pricing implementation and provider environment.

Business data crossing the call boundary

Validated quote inputs and the released quote result.

What this shows

Consumers call one maintained rule without packaging another copy as a separate API service.

What it doesn't prove

This example proves function reuse, not billing, settlement, or a marketplace.

Public source evidence for this case

Evidence level
Source layout and declarations are anonymously inspectable
Pinned public EasyRemote revision
44c768ca26d0f92a5ab9d1d03342895c29c27dc6
Public inspection
Public inspection
Expected check
Required files, Python syntax, and @node.register declaration are checked without installing dependencies
Runtime invocation
Not established by this source fixture; record separate discovery, Invocation, and terminal Receipt evidence

Run in a compatible source workspace

This Provider/Client walkthrough requires compatible EasyRemote, EasyNet-Cli, and EasyNet-Axon sibling source checkouts, a compatible Hub, and a paired, running Runtime. The source is public; clean installation from public packages is not yet verified. Technical Alpha offers guided setup. Use the pinned EasyRemote revision below; this page does not pin the other components. Runtime admission still determines whether the caller may execute the function.

# From EasyRemote revision 44c768ca26d0f92a5ab9d1d03342895c29c27dc6
cd gallery/projects/00_basic_remote_math
# Terminal 1
uv sync --frozen
uv run python node.py

# Terminal 2 (same project)
uv run python client.py
Connect your own function

Read the setup first. You need compatible sibling source checkouts, a compatible Hub, and a paired, running Runtime. Technical Alpha offers guided help; public-package clean installation is not yet verified.

All source casesRequest technical alpha