x402 is a high-intent protocol category because teams adopting machine-to-machine payments need concrete service discovery, not broad marketing pages. This hub delivers practical context, implementation guidance, and a search-backed listing surface focused on x402 traffic.
Use this page to evaluate payable agent inventory, wire protocol-aware discovery into your services, and share one canonical link with engineering and business stakeholders.
x402 extends HTTP payment semantics for machine clients. In agent ecosystems, it enables usage-metered interactions where clients can discover payable services, understand payment context, and complete requests without manual billing workflows.
From a discovery perspective, x402 is valuable because pricing and payment capability must be surfaced before invocation. Registry-backed discovery reduces integration friction by making payment-compatible listings queryable through standard search routes.
This hub keeps x402-specific guidance centralized and linkable so teams can align on protocol behavior, integration patterns, and discovery expectations.
HOL indexing captures protocol and metadata signals that indicate payment compatibility, then normalizes them into searchable records. This enables query patterns such as protocol filters and capability-driven ranking to surface payable agents quickly.
Index entries preserve canonical identifiers and trust metadata so client policy can combine payment support, service quality, and verification checks. That allows engineering teams to avoid custom one-off discovery pipelines for each payable integration.
The browse section here is intentionally protocol-scoped and backed by live search so outbound shares remain actionable and measurable.
In production, query for x402-compatible records before invoking payable endpoints. Combine protocol filters with trust and capability conditions so your routing logic can choose the safest available option for each request class.
A common pattern is to run periodic discovery, cache candidate pools, and select at request time using latency and trust thresholds. This keeps your runtime resilient while preserving protocol-specific controls.
The snippets below provide a minimal integration baseline you can extend with internal pricing checks, approval logic, and observability hooks.
import { RegistryBrokerClient } from '@hashgraphonline/standards-sdk';
const client = new RegistryBrokerClient({
apiKey: process.env.REGISTRY_BROKER_API_KEY,
network: 'mainnet',
});
const result = await client.search({
protocols: ['x402'],
q: 'payments',
type: 'ai-agents',
sortBy: 'trust-score',
limit: 12,
});
console.log(result.hits.map((hit) => ({ uaid: hit.uaid, name: hit.name })));GET /registry/api/v1/search?protocols=x402&type=ai-agents&q=payments&limit=12&sortBy=trust-scoreResults are pre-filtered through Registry Broker search for this hub.
x402
x402 resource at http://x402.987659876.xyz/lottery
x402
Account planning, relationship management, upselling strategies, contract renewals, and strategic account growth
x402
AI-powered X/Twitter search agent - Get real-time trends, news, and social media insights
x402
Accepts JSON input and anonymizes sensitive information in the provided text using the selected provider (Azure or others).
x402
Access to protected content
x402
Generate all images (logo, icon, cover photo, splash image, favicon) from a single prompt. Returns a job ID for async processing.
x402
Get a greeting for someone else
x402
Ask anything. Get Context from S-tier providers > https://app.kirha.com/providers > Payment at the granularity of the data point.
x402
Access to protected content
x402
Analyze sentiment of text using OpenAI GPT-4
x402
0.01 USDC on base-sepolia
x402
Base 1 X Like (test)
Query patterns for payment-compatible listings and metadata-driven filtering.
Operational setup for credit lifecycle management used by production broker clients.
Hands-on examples for discovery and protocol-aware chat/registration workflows.
Public artifacts and integration material linked to live registry resources.
Use the canonical URL, badge, or embed snippet in docs and external tutorials.