AGENT SPEND GOVERNANCEAGPD-1

Signed authority
before a machine spends.

Agent Guild gives an autonomous x402 wallet a short-lived, portable decision for one exact transfer. The payee, chain, token, atomic amount, resource, capability, and policy thresholds are sealed into a credential the buyer verifies locally before creating a payment signature.

Install policy client Inspect machine contract
$0.01 USDC / decisionBase mainnetNo custodyFree verification
01

FAIL-CLOSED FLOW

One decision. One transaction.

This is machine-callable payment pre-authorization, not a dashboard approval or a reputation screenshot. An unavailable, unpaid, unsigned, stale, mismatched, or blocked decision aborts before the wallet signs.

  1. 01

    Observe

    Read the selected x402 requirement from the buyer's actual payment flow.

  2. 02

    Bind

    Request an AGPD-1 decision for the exact payee, network, asset, amount, and resource.

  3. 03

    Verify

    Check the Guild signature, issuer, lifetime, policy, capability, and every payment field locally.

  4. 04

    Enforce

    Create the payment only for a valid sealed allow; otherwise stop.

OFFICIAL CLIENT HOOK

Put policy at the signing boundary.

The supplied hook runs immediately before the official x402 client creates payment material. A separate unguarded payment transport buys the policy decision, preventing recursive authorization.

NODE / TYPESCRIPTFAIL CLOSED
import {
  createAgentGuildX402PaymentPolicy,
} from "https://agent-guild-5d5r.onrender.com/sdk/integrations/x402_payment_policy.mjs";

client.onBeforePaymentCreation(
  createAgentGuildX402PaymentPolicy({
    meteredFetch: separateUnguardedX402Fetch,
    capability: "research",
    maxRisk: 32.99,
    minConfidence: 0.7,
    maxAmountAtomic: 1000000n,
  }),
);
02

EXACT REQUEST

Terms are data, not prose.

Machines can call the worker relay or the canonical Agent Guild route. The worker forwards the live payment challenge and result; Agent Guild receives settlement and signs the credential.

POST https://codex-autonomous-worker.rwdburley.chatgpt.site/wallet-binding/decision
content-type: application/json

{
  "payment": {
    "scheme": "exact",
    "network": "eip155:8453",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "10000",
    "pay_to": "0x<merchant>",
    "resource": "https://merchant.example/resource"
  },
  "capability": "research",
  "policy": { "max_risk": 32.99, "min_confidence": 0.7 },
  "ttl_seconds": 300
}

THE CREDENTIAL PROVES

Who the exact payment targets, what policy ran, and what the Guild decided.

It is portable, short-lived, signed with the published Guild key, and independently verifiable offline.

IT DOES NOT PROVE

That a merchant will deliver, that a claim is true, or that settlement occurred.

Outcome receipts and payment confirmation remain separate evidence. The boundary is explicit so machines can compose them safely.