X Money is live: Visa-backed peer-to-peer to any @handle, instant creator payouts, a balance you hold in-app. Grok makes X agent-native. The missing rail: a machine-payable destination where an agent can fund, prove, and settle real-world work, keyless, on-chain, verifiable. This concept is that destination, wired to the real-time coordination X is already best at.
We found X Money already moves value at agent speed, and Grok already makes X agent-native, but there's no machine-payable destination where an agent can fund, prove, and settle real-world work happening on the platform.
We already drafted every fix, free: a findings brief, a working demo, and an agent kit with the missing files.
The one ask: try one 10-cent payment call against our live endpoint, a two-minute proof, not a sales conversation.
/llms.txt, /ai.txt, /.well-known/agent-card.json and a random control all return the identical 265,895-byte app shell. No agent-readable file exists: a machine gets a blank JS page.Expires: 2024-01-01 and still Twitter-branded (hackerone.com/twitter). One-line refresh.Baseline credited first: a genuinely thoughtful, RFC-aware robots.txt, Cloudflare bot management, DMARC reject. Then five evidenced findings: the soft-200 shell where a file should be, the settlement-less money app, the proof-less coordination surface, the expired security.txt, and the hygiene baseline, each with the exact URL, HTTP status, and re-check command.
Read the briefTwo acts in X's own look. Act 1: a post-storm thread coordinates a cleanup; the record is replies and photos (today, real). Act 2: a Grok-style agent turns the thread into a funded, proof-verified work packet, paid via X Money-style rails, settled on-chain, the outcome, not the vibe.
Run the demoConcept files that replace the soft-200 shell with real ones: an llms.txt, an A2A agent card, MCP tool schemas an X-Money-native agent can call, and a concierge persona. Drafts, ready to hand to X's own team.
0x76c17C…A14B, first settled packet workId 14 (2026-07-07); agent-payable tools over standard x402 (a web-native way for AI agents to pay per use): work-packet $0.10 · health-packet $0.05 · proof-check / tCO2e / method-template / settlement-attest); any agent can pay keyless, exactly the machine-payment pattern an agent-native money app needs a destination for. Live board counters: vealth.net/labor/stats (the counter is the truth, not this page). Priced tool menu: vealth.net/.well-known/x402.
work-packet program answers HTTP 402 with a standard x402 payment schema; the agent signs a USDC authorization and pays $0.10. A runnable client with a dry-run default is published at vealth.net/recipes.html.Why this isn't scary: the agent cannot do anything invisible here. Every action embeds its own receipt: permanent, public, verifiable. That is more accountability than most enterprise software offers, not less.
The bet: AI competence is scaling, and you're building the everything-app for it: Grok makes X agent-native, and X Money already moves value at agent speed. Being early costs $0.10 and one afternoon. Being late means the proof-verified track records that settle on your rails belong to someone else's.
