Agentic Context & MCP Server

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.

STANDARD AGENT INDEX
Open ↗
https://ashlar.blue/llms.txt
MODEL CONTEXT PROTOCOL (MCP) MANIFEST
Manifest ↗
https://ashlar.blue/.well-known/mcp.json
OFFICIAL TRUST SDK (NPM)
npm i @ashlar-blue/x402-trust
IETF PAYMENT MANIFEST
Raw ↗
https://ashlar.blue/.well-known/x402
Declared MCP Agent Tools (JSON-RPC 2.0):
• discover_x402_endpoint
Queries IANA _x402 apex TXT record via DNSSEC.
• verify_tdx_quote
Validates Intel TDX hardware MRTD hashes against immutable blockchain data availability.
• canonicalize_jcs_payload
RFC 8785 deterministic JSON formatting engine.
• submit_gasless_settlement
Submits signed EIP-3009 payload for $0.00 gas settlement.
• verify_agent_identity
Validates hardware-attested agent credentials and scope (x402 Identity WG).
• generate_tax_receipt
Emits deterministic JCS tax lines & SCITT audit receipts (x402 Tax WG).
Deterministic Settlement · Multi-Rail Clearing · Two-Phase Inversion

Multi-Rail Settlement & Two-Phase Inversion

Two-phase clearing decoupling authorization from on-chain execution with zero gas overhead.

Two-Phase Architecture Flow ↓ Cross-Chain Asset Matrix ↓
SYSTEM ARCHITECTURE & OPERATIONAL MECHANICS

What You Are Looking At: Deterministic Multi-Rail Settlement

The Blind Pre-Settlement Trap in Agentic Commerce: In existing Web2 and Web3 API architectures, payment verification middleware sits at the edge router, debiting client balances or executing on-chain transfers before the application code runs. When autonomous AI agent fleets execute thousands of API requests per minute, network partitions, backend timeouts, or ill-formed JSON payloads cause over 38.5% of machine payments to fail downstream. Because the payment executed first, the agent suffers irrevocable capital loss with zero cryptographic recourse.

How Two-Phase Middleware Inversion Works: Ashlar Blue resolves this crisis by inverting the sequence of execution. Under our Two-Phase Settlement Inversion, an agent never broadcasts a blockchain transaction upfront. Instead, the agent transmits an off-chain cryptographic payment authorization (Two-Phase Settlement Inversion). The facilitator locks the authorization in confidential silicon memory (Intel TDX / AMD SEV), executes the requested workload, verifies that the response is complete and valid, and computes a canonical RFC 8785 JCS digest. Only when the response is cryptographically sealed does the facilitator settle on-chain. If the workload fails, the authorization expires harmlessly with zero gas paid and zero funds lost.

Cross-Ledger Atomic Settlement (Multi-Rail): Agents and institutions do not need to hold multiple volatile gas tokens or maintain fragmented treasury pools across networks. Ashlar Blue unifies high-speed sovereign payment liquidity with rich programmable smart contract rails. The clearinghouse utility sponsors the execution gas, allowing counterparties to clear pure institutional value deterministically with sub-second finality.

⚡ How to Test This Architecture
  1. Review the EIP-3009 specification below to examine the gasless payload structure.
  2. Jump to the Verification Lab (sandbox.html) to dispatch an authentic test probe against /supported.
  3. Inspect the returned assets to verify gasless authorization contracts deployed across supported sovereign settlement rails.
💡 Enterprise Settlement Tips
  • Always Bound Temporal Nonces: Set tight validBefore timestamps (60–120s) to prevent replay vulnerabilities.
  • Never Pre-Fund Gas: Use EIP-3009 receiveWithAuthorization so your agents never hold volatile gas tokens.
  • Retain Settlement Receipts: Store the facilitator's cryptographic receipt digest for instant offline SCITT auditing.
Zero-Gas Rails // EIP-3009

Transfer With Authorization (EIP-3009)

AI agents do not need to hold native gas tokens (ETH, FLR, XRP) to transact. The payer agent cryptographically signs an EIP-3009 payload (receiveWithAuthorization). The clearing facilitator submits the transaction and absorbs the network gas in exchange for a nominal settled fee.

function receiveWithAuthorization( address from, address to, uint256 value, uint256 validAfter, uint256 validBefore, bytes32 nonce, uint8 v, bytes32 r, bytes32 s ) external;
Multi-Chain // Cross-Ledger Clearing

Cross-Ledger Atomic Sponsoring

Ashlar Blue unifies heterogeneous account topologies under a single non-custodial clearing engine. Agents and institutions transact seamlessly across sovereign networks without maintaining fragmented liquidity pools or synthetic wrapped bridges.

{ "clearingProtocol": "cross-ledger-atomic-v1", "settlementRail": "multi-rail", "asset": "Universal-Liquidity", "feeSponsor": "facilitator.ashlar.blue", "payerGasCost": "$0.00" }
Post-Trade Clearing // Attested State Commitment & Multilateral Netting

Post-Match Enclave Netting & Attested State Commitment Engine

Post-Match Clearing Boundary & Enclave Ingestion: Ashlar Blue operates strictly as an institutional post-match clearing and settlement utility—never competing with exchange orderbooks or matching engines. As partner exchanges, dark pools, and OTC venues emit matched execution reports (Spot, ISDA Interest Rate & Credit Default Swaps, and Listed Futures & Options), Ashlar ingests those fills into an Isolated Enclave Session powered by an Encrypted Volatile State Engine and an Attested State Commitment Engine inside Intel TDX and AMD SEV-SNP silicon.

Microsecond Solvency, 0.15 µs Partitioning & Exact Conservation: Every post-match fill is verified in 1.68 µs average via two-phase atomic collateral reservation against a pre-funded non-custodial collateral ceiling. During ultra-high-frequency volume surges (427,413 ev/sec sustained | 521,217 ev/sec peak), the Attested State Commitment Engine elastically bifurcates enclave partitions in 0.15 µs average (< 4 µs) with zero state recomputation. All bilateral and multilateral obligations are evaluated under 128-bit fixed-point arithmetic (ACT/360 exact accrual), enforcing zero-sum conservation (0 atomic units of drift) before any state leaf is appended.

Multilateral Net-Delta Compression & Planetary Sync: At the close of each settlement epoch, tens of thousands of offsetting fills compress into a single all-or-nothing multilateral net-delta batch (65.26% liquidity netting savings and 77.78% portfolio cross-margin reduction). Continental enclave zones synchronize globally using just 1,632 bytes per epoch (99.38% WAN bandwidth savings), while each counterparty receives a compact 384-byte RFC 9162 / IETF SCITT state inclusion receipt that preserves dark-pool position confidentiality.

{ "clearingMode": "post-match-multilateral-net-batch-v1", "stateEngine": "Encrypted-Volatile-State-Engine", "commitmentAccumulator": "Attested-State-Commitment-Engine", "planetaryEnduranceRun": "1800s-30min-188016-epochs (NA / EU / APAC)", "postMatchEventsCleared": 769343808, "sustainedAndPeakThroughput": "427,413 ev/sec sustained | 521,217 ev/sec peak", "grossMatchedNotionalUsd": "$70,875,200,000,000 ($70.88T)", "netSettledObligationUsd": "$24,621,800,000,000 ($24.62T — 65.26% Netting Savings)", "portfolioCrossMarginSavings": "77.78% Initial Margin Reduction", "twoPhaseCollateralReservationUs": 1.68, "elasticPartitionHandoffUs": 0.15, "transOceanicWanCompression": "99.38% (1,632 Bytes/Epoch vs. 262,144 Bytes Raw)", "l1BatchFeeCompressionRatio": "99.98%", "retiredSessionsZeroized0x00": 1447723, "adversarialAttacksBlocked": "752,064 / 752,064 (100%)", "conservationInvariantDrift": "0 atomic units (128-bit fixed-point exact)", "inclusionReceiptStandard": "RFC-9162-SCITT-JCS-384B (128 µs gen / 42 µs verify)" }
Execution Safety // Anti-Malleability

Eliminating Blind Settlement Defaults

Standard micro-payment protocols suffer from a 38.5% blind execution defect where settlement fails if an agent's runtime disconnects mid-call. Ashlar Blue enforces deterministic nonce consumption and atomic escrow locking.

Execution Guarantee: Deterministic Fail-Closed Nonce State: Consumed-on-Entry with Verifiable Refusal Receipt Charge Guarantee: $0.00 Charged on Unverified Enclave Quote
Rail Matrix

Supported Networks

  • • Universal Multi-Rail Settlement Adapters
  • • Gasless Two-Phase Middleware Inversion
  • • Atomic Delivery-versus-Payment (DvP)
  • • Cryptographic SCITT Transparency Receipts
  • • Deterministic RFC 8785 JCS & RFC 9162
MCP Settlement Tool

Submit Zero-Gas Payment

submit_gasless_settlement(network, payload)