Skip to main content
Molpha makes external data usable by agents without asking downstream systems to trust the agent’s text output. The agent requests data, Molpha nodes sign the result, and applications verify the signed payload before acting.

​
Why agents use Molpha

  • Typed tools, not prompt glue — MCP exposes discover, derive, fetch (payment: auto|subscription|x402), verify, and execute operations as structured tools.
  • Portable trust anchor — the signed payload can be verified by Solana, EVM, Starknet, or backend code.
  • Two agent payment options — Delegate under a subscription, or x402 escrow pay-per-request.
  • Separation of authority — a cold subscription owner can authorize a hot agent key via Delegate without giving the agent the owner wallet.

​
Agent access: pick one

x402 (HTTP 402) and AgentEscrow (on-chain ATA) are the same path — not a third option.

​
Agent architecture

The agent may describe the value, but the application should treat the signed payload as the source of truth.

​
Common workflows

​
Safety model

Agents are powerful but forgetful; budget and write controls should live outside the prompt.
  • Use MCP dry-run mode for exploration.
  • Prefer Delegate caps (max_data_requests, max_signers) when a subscription exists.
  • Prefer x402 escrow ATA balance limits when paying per request.
  • Require explicit confirmation before submitting transactions.
  • Verify payloads before acting on values.

​
Start here

Agent quickstart

First verified API request from an MCP client.

MCP server

Tool reference, setup, signer adapters, and guardrails.

Delegates

Hot agent keys under a subscription.

x402 escrow

Pay per verified request via AgentEscrow.