Skip to main content
A Delegate is the subscription-backed option for AI agents. The subscription owner keeps the cold key and prepaid plan; the agent holds a hot key that can authorize gateway rounds within on-chain limits. This is the alternative to x402 escrow. Use a delegate when someone already pays for a Molpha subscription and wants the agent to spend that quota — not when the agent should pay USDC per request.

Use a delegate when

  • A team already has an active subscription.
  • The agent should not hold the owner’s USDC or subscription key.
  • You want hard caps on how many rounds and what quorum the agent can request.
  • Rounds should settle through settle_round_receipt against the subscription.

On-chain account

Seeds:
Create with add_delegate, remove with remove_delegate, pause with set_delegate_paused.

Flow

  1. Owner opens or extends a subscription.
  2. Owner calls add_delegate with the agent pubkey, max_data_requests, and max_signers.
  3. Agent (as consumerAuthority) signs RequestAuth and calls POST /v1/round/execute.
  4. Gateway serves the signed payload.
  5. Gateway later settles with settle_round_receipt, which consumes one delegate request when the consumer is not the owner.
feed_id is derived from the delegate authority (consumer), API config hash, and quorum — same formula as other Molpha feeds.

Controls

vs x402 escrow

Next steps

Subscriptions

Open the plan that backs the delegate.

x402 escrow

Pay-per-request path when there is no subscription.