xhagents.xyz

Enriches a company, domain or person from public structured sources (Wikidata, the public LinkedIn company page, Clearbit autocomplete): industry, size, headquarters, founding year, official website, stock listing and social handles.

Build an x402 paid endpoint that passes the validator, gets indexed and takes real USDC. End-to-end recipe for turning any HTTP capability into an x402 endpoint that an unknown agent can find, pay for and consume: the payment gate, the verifier rules, per-route pricing, the concurrency traps, the nginx wiring, the discovery surface, plus the money-path bugs we only found when real USDC moved. Comes with the exact commands we run.

A dated, freshly rebuilt brief on where demand is in the agent-payment economy: what builders and agents are discussing and paying for in the last 30 days (Hacker News, GitHub, Polymarket, marketplace listings), plus our own paid-endpoint call and settlement performance. Rebuilt every day at 06:00 WIB; yesterday's copy is not the product.

Funding rate, open interest and price trend for a perpetual pair (Binance public data) plus protocol TVL change from DefiLlama, combined into a labelled sentiment with its weights shown.

Current Base base fee, suggested priority fees and USD cost estimates for a transfer or an ERC-20 transfer.

Verifies that a transaction hash settled a USDC payment to a given recipient, returning the parsed transfer and confirmation count.

Pulls one X/Twitter post by URL or id (text, author, metrics, language) and/or a public LinkedIn company page (industry, size, headquarters, specialties, followers) as structured JSON.

ERC-20 metadata, proxy detection and free DEX liquidity data for a token on Base, with the checks that could not be performed stated explicitly.

Connect a headless VPS to a user's Google Drive (rclone, no browser on the server). Give a server permanent, scriptable access to someone else's Google Drive: one interactive authorisation on a machine with a browser, then bidirectional sync from the server forever. This is the exact flow we use for both a personal Drive bridge and a scheduled VPS backup.

Balances, contract status, nonce, recent USDC activity and known-address labels for any Base address.

Runs a live web search and returns ranked results with title, URL, domain and snippet, then fetches the top pages and returns their extracted readable text — content retrieval, not just links.

Scans the last blocks for USDC and WETH transfers above a USD threshold and returns the largest movements with direction and counterparties. Pending-mempool visibility needs a node with txpool access, which this reports instead of faking.

Fetches any x402 endpoint, decodes its 402 challenge and reports conformance: version, accepts fields, PAYMENT-REQUIRED header, bazaar metadata and price.

Searches Coinbase Bazaar and the x402-list directory at once and returns de-duplicated endpoints with price, network, payTo and description, so an agent can find a service to pay without knowing it in advance.

Register an x402 endpoint so agents can find and pay it (x402scan + Coinbase Bazaar). The complete discovery path for an x402 endpoint: publish machine-readable discovery documents, pass the official validator, list on x402scan, understand what actually triggers Coinbase Bazaar indexing, and prove the listing exists from the registry's own API instead of a success toast. Written from an endpoint set that went from 0 to 11 listed resources, with the exact API payloads a registry expects today.

Ask the XH Agents AI Trading Assistant a market question

Ask the XH Agents knowledge base (15 field notes on infrastructure, x402 and agent tooling)

Thirteen production playbooks from running an x402 paid API on Base: shipping the endpoint, the payment-verifier rules, the real-money buyer test, the Base RPC capability audit, CDP authentication, directory registration, consolidating Cloudflare/Solana data, an rclone Google Drive bridge, AdSense, multi-size ad slots, nginx route recovery and secure Telegram alerts. Each item carries the mechanism, the commands, the pitfalls that cost us real money and how to verify the result.

YouTube Shorts automation with AI: queue → render → upload → notify. A 3x/day pipeline that takes product photos from Google Drive, renders a 720x1280 Shorts video with Ken Burns motion, uploads it to YouTube via the Data API v3, updates a static showcase page and reports to Telegram. Every step below ran in production; the numbers are the ones we actually use.