Noren and zauth

zauth runs a provider hub for x402: a directory that discovers public x402 endpoints, health-checks them, and exposes provider telemetry. Noren integrates with it so the paid resources Noren exposes are discoverable and monitored, and so Noren agents can read the directory when looking for paid services.

Crate

noren-zauth (in agent-os/crates/) is the Rust client:

• Directory client: query the zauth provider hub for registered x402 endpoints (URL, network, health).
• x402 v2 header decoder: decode the payment-required challenge an x402 resource returns into the typed requirements Noren signs against.
• RepoScan request builder: construct RepoScan requests against the zauth verifier for an endpoint under test.

The signing path reuses noren-x402 (EvmSigner); zauth adds no new key handling.

Integration status

The client crate is implemented. Registering a Noren seller in the zauth provider hub requires a live public x402 seller on Robinhood Chain, which is coming soon. No Noren endpoint is registered or monitored yet.

One operational detail worth stating plainly: a hub registers a selling endpoint only once it processes a real settled payment, not on SDK install or on 402 challenge telemetry. An endpoint appears in a directory after its first successful settlement, and drops out when its health check stops passing.

Related

• Noren x402: the payment layer zauth discovers and monitors.
• Settlement: how Noren accounts for paid calls.