Skip to main content
A gateway turns an application request into a Molpha signing round. It discovers the registry, selects nodes, dispatches the API config, collects partial signatures, aggregates them, and returns a payload ready for verification.

​
Responsibilities

  • Accept SDK, backend, and agent requests.
  • Authenticate owner-mode requests.
  • Quote and validate exact agent round pricing (amount == price).
  • Return x402 envelopes when pay-per-request escrow is underfunded.
  • Dispatch node rounds and collect aggregate signatures.
  • Maintain a settlement outbox for served rounds.
  • Self-host via YAML/env config (see Gateway API).

​
Request paths

​
Why gateways are first-class in Brebeneskul

Brebeneskul adds economic routing around each request. The gateway is no longer only a convenience wrapper around nodes; it is also the coordination point for access models, payment checks, x402 envelopes, and settlement batching.

Gateway API

Endpoint schemas, auth, agent endpoints, and self-hosting config.

x402 escrow

Pay-per-request agent access and settlement.