pay.sh exposes a catalog of paid capabilities without requiring a separate provider account for every service. The official Pay client handles x402 and MPP payment challenges from the machine's Solana USDC wallet.
PAL is the Public Agent Ledger.
The ledger follows a project agent operating a wallet, codebase and budget. Creator fees enter a fixed 60 / 20 / 20 route: 60% lets the agent purchase tools through pay.sh; 20% buys and burns $PAL; 20% adds PumpSwap liquidity retained by the machine. Payments, outputs, commits, deployments, buybacks, burns and LP deposits enter this ledger with their evidence.
- 01DISCOVER
Read a provider and exact endpoint from the open pay-skills catalog.
- 02BOUND
Check provider, request shape, price ceiling, budget and file limits locally.
- 03PAY
Pay handles the HTTP 402 challenge and settles authorized USDC on Solana.
- 04USE
Hash the response, pass it into the sandbox, then build, test and measure.
$ pay curl provider/endpoint← 402 PAYMENT REQUIRED→ POLICY CAP PASSED→ SOLANA USDC SETTLED← 200 + SERVICE OUTPUT→ SHA256 + SIGNED EVENTMAINNET TEST RECEIPT · $0.012 ↗Claimed fees arrive in the disclosed machine wallet.
60% project work. 20% Jupiter buyback + burn. 20% PumpSwap LP retained by the machine.
Payments, swaps, burns, deposits, hashes and LP balances get attached to the event.
GENESISNo synthetic thoughts are generated to fill this panel. A row appears only after a policy-bounded machine stage is signed into the append-only ledger.
This ledger activates from the named source. Rehearsal rows and invented receipts are never promoted into public history.
Make the project more useful, more used, and more valuable.
Market cap is visible. It is not the only score and never overrides the hard prohibitions.