Execution substrate

Framework, protocol, and event-system breadth is part of the finish-line product.

This page makes the execution substrate public from the umbrella surface. It shows the frameworks, protocol fronts, bridge transports, and event-system families that let agents and machines reach the same runtime spine from CLI, service, graph, stream, callback, and coordination environments without inventing a different product each time.

View ecosystem lanes JSON Open the agent entry
Free: discovery + 20 tool calls per UTC day, no key needed Then: from $0.01 USDC per call (Base mainnet; $0.02 for a verified answer with a signed attestation) via x402, or from 3 credits per call with a spend key. Open-network provider tools: each provider's own price, from $0.001. Pricing Buy credits ($1.00 = 400) Set up your client
Reference page. This page documents catalog breadth and release evidence; entries here are not all live or purchasable. What you can buy today, the price and how to pay: Pricing.
How orchestration lands

Framework family

The framework lane makes it obvious that the runtime already meets builders where they are. The public story is not just one protocol and one command; it includes serious orchestration and agent-runtime families that can converge back into the same machine-payment and proof spine. CrewAI and LlamaIndex are registry-backed in the integration matrix even where they do not yet have separate lane pages.

  • Featured frameworks: 6
  • Framework first-run flows: 1
  • Framework ecosystems in the catalog: 4
  • Framework runtime modes: 3
  • First surfaced ecosystem: langgraph

Framework lane summary · Framework catalog summary · LangGraph summary · LangChain summary · AutoGen summary · Semantic Kernel summary · Integration matrix summary

How commands arrive

Protocol and bridge family

The protocol lane keeps the default runtime path clear while still exposing the breadth that real machine systems need. This is where MCP, A2A, A2C, ACP, and the bridge transports live together as one discoverable family.

  • Featured protocol fronts: 10
  • Protocol first-run flows: 1
  • First-party callable fronts: 4
  • Launch-default fronts: 1
  • Supported bridge protocols: 7

Protocol lane summary · Adapter/protocol truth · MCP lane · A2A lane · A2C lane · ACP lane · Integration protocols

How streaming and callbacks stay first-class

Event-system family

Kafka, NATS, MQTT, and webhook-oriented delivery are not side notes. They are part of the machine-operating substrate that lets the runtime live inside high-frequency, asynchronous, device, and event-driven systems.

  • Event-system ecosystems in the catalog: 4
  • Event-system lanes: 4
  • Event modes: 3
  • Stream modes: 3
  • Subject modes: 3
  • Callback modes: 3

Event-system catalog summary · Event systems summary · Kafka summary · NATS summary · MQTT summary · Webhook event bus summary

Finish-line reality

Why this layer matters

A real 3.9.13 machine stack has to be usable from more than one happy-path shell. This ecosystem surface keeps the public story honest by showing that the runtime already has framework, transport, coordination, and callback depth for real agentic and machine-to-machine environments.

  • Agents can reach the runtime from their existing orchestration environment instead of rewriting everything around one custom interface.
  • Protocols and event systems stay subordinate to the same runtime, payment, and proof spine rather than forking the product.
  • The umbrella site now surfaces execution substrate depth alongside money, proof, support, and release surfaces.
  • These families are catalog/reference breadth; what you can buy today is listed under Pricing.

Agents · Support · Claim · Site map