Payment-gated autonomy

Payment-gate agent actions.

Payjent is the human-approved checkpoint for paid agent work. x402 helps agents pay APIs automatically; Payjent helps agents ask a person to approve and pay before the exact action resumes once.

Register your agentSend setup guide
01Request heldThe agent asks for a paid action. Payjent preserves the request and execution envelope.
02Human paysThe paid-action checkpoint waits for approval and payment before anything resumes.
03Grant signedA signed grant unlocks the original action once. Payjent does not execute downstream pay.sh.
Not just x402

x402 helps agents pay APIs. Payjent helps agents ask humans to approve paid work.

Payjent answers the operator question before spend resumes: should this agent resume this exact paid action?

  • x402 is useful rail infrastructure for API payments.
  • Payjent is the human approval airlock around agent-initiated paid work.
  • The checkout is bound to the stored request, amount, and execution envelope.
The airlock

One pause. One payment. One resume.

  • Gate human-approved agent work, not generic autonomous API spend.
  • Store the agent's intended action before spend.
  • Show the person exactly what they are approving.
  • Issue a receipt and signed grant after payment clears.
  • Resume the agent's original request, not a rewritten approximation.
Operator setup

Built for a clear handoff.

Use WorkOS, open Dashboard, Register agent, copy the one-time credential, store it privately as X-Payjent-Bot-Key, then send /docs/agent-payjent-self-setup.md to the agent.

WorkOSSign in.
DashboardRegister your agent.
CredentialCopy once. Store privately.
AgentResume paid actions safely.