x402
x402 agentic payments (Coinbase's HTTP 402 protocol). Custody-free tools to pay x402-protected endpoints (build the EIP-3009 transferWithAuthorization the payer signs, assemble the X-PAYMENT header), call a facilitator (verify/settle/supported), and monetize your own API by generating PaymentRequirements. USDC on Base. Triggers: x402, HTTP 402, pay per request, agentic payment, machine payment, X-PAYMENT, transferWithAuthorization, EIP-3009, facilitator, monetize API, pay for API, agent pays.
git clone --depth 1 https://github.com/internet-court/internet-court-skill /tmp/x402 && cp -r /tmp/x402/vendored/chaingpt/x402 ~/.claude/skills/x402SKILL.md
# x402 Payments skill x402 turns HTTP `402 Payment Required` into a real payment rail for agents: a server replies `402` with what it wants paid; the client signs an off-chain authorization and retries with an `X-PAYMENT` header; a facilitator broadcasts it. Settlement uses EIP-3009 `transferWithAuthorization` (e.g. USDC on Base) — the facilitator can only broadcast the signed authorization, never alter the amount or destination. **Custody-free:** the plugin builds the EIP-712 the payer signs and assembles the header; it never holds a key. ## Tools | Tool | Purpose | |---|---| | `chaingpt_x402_decode` | Decode a 402 body or X-PAYMENT header into human terms (amount/token/recipient/expiry) before paying. | | `chaingpt_x402_build_payment` | Build the UNSIGNED EIP-3009 typed data; pass a signature back to get the final `X-PAYMENT` header. | | `chaingpt_x402_facilitator` | Call a facilitator: `supported` / `verify` / `settle`. | | `chaingpt_x402_create_requirements` | Server side: generate the `PaymentRequirements` + 402 body to monetize your endpoint. | | `chaingpt_x402_fetch` | The whole client loop in one tool: fetch a URL; on 402 it decodes the challenge and (given `from`) emits the unsigned typed data; re-call with `xPaymentHeader` to complete the paid request. | ## Pay an endpoint (client flow) Fast path — one tool drives the loop: 1. `chaingpt_x402_fetch url=<resource> from=<payer>` → on 402 you get the decoded price/payee AND the unsigned EIP-3009 typed data. 2. Sign the typed data in the payer's wallet. 3. `chaingpt_x402_build_payment from=<payer> requirements=<from step 1> signature=0x…` → the `X-PAYMENT` header. 4. `chaingpt_x402_fetch url=<resource> xPaymentHeader=<header>` → the paid response. Manual path (same primitives, finer control): `_decode` → `_build_payment` → sign → `_build_payment +signature` → retry yourself. ## Monetize your endpoint (server flow) `chaingpt_x402_create_requirements network=base amount=0.01 payTo=<you>` → serve the returned JSON with HTTP 402. Verify/settle incoming payments via a facilitator (`chaingpt_x402_facilitator`). Known EIP-3009 tokens: USDC on `base` and `base-sepolia`. For other tokens pass full `PaymentRequirements` (with `asset` + `extra.name`/`extra.version`). 0 ChainGPT credits.
0G Compute Network guide for decentralized AI inference, fine-tuning, and GPU services. Covers chatbots, image generation, speech-to-text, SDK integration (0g-serving-broker), processResponse API, broker.inference methods, CLI commands (0g-compute-cli), and account management. Use this skill for any 0G compute, 0G AI, or decentralized GPU question.
Give the AI agent its own EVM wallet with admin-controlled policies the agent CANNOT bypass even under prompt injection. Encrypted keystore (AES-256-GCM, scrypt KDF), policy file the agent has no tool to write, deterministic policy gate on every signing operation, optional local HTTP dashboard. Triggers: agent wallet, give the agent a wallet, agent address, fund the agent, agent autonomy, policy gate, kill switch, agent permissions, bounded autonomy, ERC-4337 alternative, session-key alternative.
Crypto wallet operations via the awal CLI — sign in, check balances, send USDC/ETH/POL/SOL, trade tokens, fund the wallet, and use the x402 payment protocol to discover paid services, pay for API calls, monetize an API, or query onchain data. Use whenever the user mentions signing in, login, authentication, wallet status, balance, address, sending money, paying someone, transferring tokens, ENS names, swapping/trading/converting tokens, funding/topping up/onramp, USDC, ETH, POL, SOL, the x402 bazaar, paid APIs, monetizing an endpoint, or querying onchain data on Base.
Help developers write code that interacts with Alkahest escrow contracts using the TypeScript, Rust, or Python SDK
Interact with Alkahest escrow contracts as a buyer, seller, or oracle using the CLI
Use this skill when the user asks to list, create, inspect, update, disable, re-enable, or revoke AltLLM Portal API keys for external agents or applications. Do NOT use for wallet login, billing history, or payment links.
Use this skill when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login for the local altllm CLI. Do NOT use for API key management, billing history, or payment links.
Use this skill when the user asks to inspect AltLLM Portal balance, redeem a promo code, review billing transactions, or view usage analytics by period, model, or API key using the local altllm CLI. Do NOT use for API key lifecycle management or payment-link execution.