Separate incoming updates from agent work You treat delivery and model execution as separate decisions. A resource subscription receives updates but never grants an agent permission to run. python academy academy/topics/notifications-vs-subscriptions website/content-src/academy/course.mjs academy Separate incoming updates from agent work
Unit 10 · React safely to live events

Separate incoming updates from agent work

You treat delivery and model execution as separate decisions. A resource subscription receives updates but never grants an agent permission to run.

7 focused minutesNot started
Unit example (nearest native match)

See the idea in context

transport = AxMCPStreamableHTTPTransport(
source = AxMCPEventSource(
    resource_subscriptions="all",
runtime.start()
if not completed.wait(60):
  1. Discover the endpoint

    The live catalog identifies concrete resources and supported event capabilities.

  2. Apply subscription policy

    Your application chooses which updates it actually wants.

  3. Route through the inbox

    An explicit event route decides whether the update only records state or wakes work.

Run itIn your own project
pip install axllm

from axllm import ai, ax

llm = ai('openai', api_key=os.environ['OPENAI_API_KEY'])
classify = ax('review:string -> sentiment:class "positive, negative, neutral"')

Set OPENAI_APIKEY in your environment before running provider-backed code.

In the ax repo

From a clone of the ax repo:

npm run example -- python src/examples/python/mcp/resource-wake-agent.py
Active practice

Show that you can use it

Answer 2 in a row to learn this · attempt 1
Keep exploring

Source-backed follow-up