A research agent might need a reusable set of instructions. A website owner might need to know why a machine cannot read a page. Those are different problems, but both can be small, occasional purchases rather than reasons to open another subscription.
AISkills402 and 402registry are two newly listed examples of x402 payments on Base. One sells agent skill files; the other sells website visibility checks. Understanding what each purchase delivers is more useful than treating both as a generic AI API.
AISkills402: buying instructions for an agent
AISkills402 lets a client discover a skill before paying for its file. The documented flow separates free MCP discovery from an HTTP purchase in USDC on Base. A successful file response includes the content, a hash, payment information and a re-download token. The provider also documents wallet-based recovery if access is lost.
That is different from sending a prompt to a hosted model. The buyer receives instructions to use in its own environment. A useful evaluation therefore asks whether those instructions fit the task and whether the agent can follow them consistently. The AISkills402 documentation explains the current purchase and recovery behavior; the directory profile collects the listing evidence.
For an integration, keep downloaded instructions separate from trusted application policy. Read them before enabling them and compare their behavior with a small, known task. A file's hash helps identify the delivered version; it does not prove that every instruction is suitable for your organization. Never let purchased content expand the agent's spending authority.
402registry: checking what a crawler receives
402registry examines a site's HTTP-visible content and returns findings with evidence. Its published checks cover issues such as empty application shells, missing-page responses and duplicate domain variants. The service describes a dated registry entry for sites that pass its checks. That entry is a result of its own assessment—not an endorsement by Google or a guarantee of indexing.
Its machine documentation distinguishes a free lookup from a paid new check. A purchase buys a check performed at that point in time; it should not be mistaken for continuous monitoring. The 402registry project profile links the reviewed service and evidence.
Suppose an article looks complete on a laptop but the initial HTTP response contains only a shell. A diagnostic can help identify that gap. The next step is to inspect the actual finding, fix the affected template and check the result again. Repeating keywords in the visible page will not solve content that a particular crawler never receives.
Keep diagnosis separate from search rankings
Crawler access, indexing and ranking are related stages, but they are not interchangeable. A readable page can still be absent from a particular query because its content does not answer the searcher's question well enough or because other results are stronger.
Use a visibility report to investigate access and rendering. Evaluate editorial quality separately: does the page answer one clear question, explain its evidence and link to useful supporting material? For more context, start with our practical introduction to x402.
Before authorizing either purchase
Check the live offer's chain, token, recipient and amount. Decide what output will count as success before the request is sent. Keep the receipt and the returned resource together, and follow the provider's recovery procedure if the response is lost. A timeout should trigger investigation of that authorization before a fresh payment is created.
The two services share a recipient with other tools from the same operator. Shared on-chain activity cannot be used as an independent sales total for either one. Our four-project overview explains the directory's coverage labels.
Common questions
Does buying a skill include a model subscription? A skill file is its own purchase; check separately for any model or hosting costs in your workflow.
Will passing a website audit put an article on Google's first page? No. A service's audit result cannot promise a search position.
Can these tools fit into a larger workflow? Yes, where their documented inputs and outputs match your needs. Scheduling and publishing are separate jobs; see our 402cron and 402post guide.
Sources
AISkills402 documentation, 402registry overview and 402registry API documentation. Product details checked on 7 November 2026.
Reference links
AISkills402 documentation
aiskills402.com/docs
directory profile
x402blockchains.com/ai-agents-apps/?project=aiskills402.com
machine documentation
402registry.com/docs
402registry project profile
x402blockchains.com/ai-agents-apps/?project=402registry.com
practical introduction to x402
What is x402? A practical guide to HTTP payments
four-project overview
x402 Projects on Base: Four Tools AI Agents Can Pay For
402cron and 402post guide
x402 Automation: Webhooks and Listings for AI Agents
402registry overview
402registry.com/