Ashlar Blue natively supports the Model Context Protocol (MCP) and standardized LLM ingestion formats, allowing autonomous AI agents to query DNS discovery, verify hardware attestation quotes, and execute zero-gas settlements without DOM scraping.
https://ashlar.blue/llms.txt
https://ashlar.blue/.well-known/mcp.json
npm i @ashlar-blue/x402-trust
https://ashlar.blue/.well-known/x402
The open internet architectural standard eliminating centralized proxy registries. Autonomous AI agents discover facilitator endpoints, supported networks, and cryptographic hardware manifests via native DNS and DNSSEC.
In the emerging machine-to-machine economy, millions of autonomous AI agents must discover, evaluate, and purchase API compute, private datasets, and real-time oracle feeds in sub-second timeframes. Historically, web services relied on centralized API catalogs, credit card billing portals, and OAuth credential brokers. These mechanisms introduce fatal friction: human-in-the-loop KYC barriers, custodial counterparty risk, rate-limiting gatekeepers, and single points of network failure.
When an autonomous agent needs to purchase a weather forecast, a financial volatility model, or private confidential inference, it cannot fill out a checkout form or store long-lived API keys on an untrusted disk. It requires a globally resolvable, permissionless, and cryptographic discovery protocol native to the internet's core naming infrastructure.
Ashlar Blue solves this by leveraging the global Domain Name System (DNS) via the draft-x402-dns-discovery standard. By registering the permanent _x402 DNS label, any server or AI agent on earth can publish its machine-readable payment parameters directly in its apex DNS zone file. A client resolves payment requirements, facilitator URLs, and supported settlement rails in exactly one DNS lookup and one HTTPS GET, inheriting the global caching, resilience, and DNSSEC cryptographic guarantees of the root nameservers.
Ashlar Blue follows the proven MTA-STS (RFC 8461) architectural model. Rather than forcing clients through proprietary registration gateways, the resource server publishes an authoritative DNS TXT record under the IANA registered _x402 label at its domain.
Parsers validate the semi-colon delimited parameter tokens according to deterministic RFC 5234 ABNF rules:
| Parameter | Type | Requirement | Description |
|---|---|---|---|
v |
String | Mandatory | Protocol version (must equal x402-1). |
wk |
HTTPS URI | Mandatory | Well-Known manifest endpoint for payment terms. |
k |
Token | Mandatory | Node role: facilitator or resource-server. |
net |
CAIP-2 | Optional | Primary settlement network (e.g. eip155:14, xrpl:mainnet). |
scheme |
Token | Optional | Payment scheme identifier (e.g. exact, escrow). |
To eliminate payload malleability and signing hash mismatches across heterogeneous AI agent frameworks (Python, Rust, Go, Node.js), all x402 payment manifests and authorization envelopes must be normalized using RFC 8785 JCS.