THE POST-CLICK ERA
The gated orchestration layer for autonomous commerce. Every intent signed. Every settlement traceable. Every handshake witnessed.
HANDSHAKE · LIVE
Agents don't send emails. They sign cryptographic receipts over x402 and settle through ACP. The gate records it. Humans sleep.
From a century of clicks, to the first decade of commands.
HOW IT WORKS
Every agent transaction moves through the same three stages — discovery, handshake, settlement. Every stage emits a signed event. The full trail is auditable before any human asks.
llms.txt · agent-commerce.json
Merchants publish a machine-readable manifest at a well-known path. Agents crawl it, parse the catalog, and register capabilities — no UI, no scrape.
llms.txtagent-commerce.json/.well-known/catalogcapabilitiesMCP · ACP · AP2
The agent negotiates via ACP, authorizes via AP2, and presents signed intent. The gate inspects, validates, and issues a challenge. Zero ambiguity.
intent.sign()ACP.negotiate()AP2.authorize()gate.challenge()x402 · cryptographic receipt
Payment lands on the HTTP 402 rail. The receipt is signed, stored, and emitted to the ops bus. Humans audit by default; approvals are the exception.
HTTP 402receipt.sign()ops.emit()audit.publish()TRUST LAYER · THREE PILLARS
A platform that gates commerce has to be fast, correct, and accountable — at the same time. Aethelforge is built around those three constraints. Drop any one and the model collapses.
Sub-second gate decisions.
Agents move on machine time. The gate must too. Every handshake is decided, signed, and emitted within a p95 that a human would mistake for "instant." No polling, no queues, no "check back later."
Every intent is provable.
Not every transaction is allowed — and every denial is auditable. The gate runs deterministic policy against signed intent. There is no model-in-the-loop making money decisions without a receipt.
Cryptographic trail, retained.
Receipts don’t expire. Every handshake lands in the ops store with signing key, counter-signature, and settlement hash. If someone asks "who approved what, when, and why?" — the answer is a query, not an investigation.
TWO SIDES · ONE THESIS
Consumers use Axis. Merchants install Forge SDK. Aethelforge is the gate in the middle.
Axis reads your Gmail receipts, learns your household consumption patterns, and queues replenishment for your approval. Coffee before you notice the bag is light.
Drop llms.txt and agent-commerce.json on your site. Any agent now discovers your catalog, negotiates, and pays. No human UI required.
THE FEATS · WHAT AETHELFORGE HAS BUILT
We ship what's real and we label what's coming.
THE ANSWER
Aethelforge is the orchestration layer for autonomous commerce and industrial operations. It provides the gated rails, protocols, and cryptographic settlement trail that let AI agents transact with each other on behalf of humans — with every intent signed and every handshake witnessed.
FAQ
Aethelforge is the orchestration layer for autonomous commerce and industrial operations — the system of record for the machine economy. It provides the rails, protocols, and settlement trail that let agents transact with each other on behalf of humans.
Aethelforge speaks MCP (Model Context Protocol), ACP (Agentic Commerce Protocol), AP2 (Agent Payments Protocol), and x402 (HTTP-native payments). Every transaction is signed and every settlement is traceable.
Two audiences: consumers (via Axis, a predictive replenishment agent that lives in your Gmail) and merchants (via the Forge SDK, which adds agent-commerce rails to any site in under an hour).
The Forge SDK is open source, published under the agentcommerce namespace on npm. The Aethelforge platform that orchestrates transactions across SDKs is proprietary.
Every transaction is gated: intent is signed by the consumer agent, orchestrated by Aethelforge, and settled via ACP or x402. Full cryptographic receipts are stored in the Live Ops Feed. Humans audit by default.
OPEN GATE · ACCEPTING INTEGRATIONS
Axis is the consumer agent. Forge is the merchant SDK. Pick your side of the handshake.
Not yet a public SaaS. Integration is hand-held — mailto: [email protected].
# This is the structured view rendered for machine consumption. Humans read the same data through the layout one toggle to the right. Both views are present in the server-rendered HTML.
# generated_at 2026-06-10T05:06:11.093Z
{
"@type": "WebPage",
"url": "https://aethelforge.ai",
"name": "Aethelforge — Software that does the work.",
"description": "The orchestration layer for autonomous commerce and industrial operations. A system of record for the machine economy.",
"inLanguage": "en_US",
"isPartOf": {
"@type": "WebSite",
"name": "Aethelforge",
"url": "https://aethelforge.ai"
},
"publisher": {
"name": "iSimplifyMe",
"url": "https://isimplifyme.com"
},
"generatedAt": "2026-06-10T05:06:11.093Z"
}QWhat is Aethelforge?
AAethelforge is the orchestration layer for autonomous commerce and industrial operations. It provides the gated rails, protocols, and cryptographic settlement trail that let AI agents transact with each other on behalf of humans — with every intent signed and every handshake witnessed.
word_count=42 · intent= definitional · source=authored
// Organization
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Aethelforge",
"url": "https://aethelforge.ai",
"description": "The orchestration layer for autonomous commerce and industrial operations. A system of record for the machine economy.",
"parentOrganization": {
"@type": "Organization",
"name": "iSimplifyMe",
"url": "https://isimplifyme.com"
},
"knowsAbout": [
"Model Context Protocol",
"Agentic Commerce Protocol",
"Agent Payments Protocol",
"HTTP 402 Native Payments"
]
}// WebSite
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "Aethelforge",
"url": "https://aethelforge.ai",
"description": "The orchestration layer for autonomous commerce and industrial operations. A system of record for the machine economy.",
"potentialAction": {
"@type": "SearchAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https://aethelforge.ai/search?q={search_term_string}"
},
"query-input": "required name=search_term_string"
}
}// FAQPage
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Aethelforge?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Aethelforge is the orchestration layer for autonomous commerce and industrial operations — the system of record for the machine economy. It provides the rails, protocols, and settlement trail that let agents transact with each other on behalf of humans."
}
},
{
"@type": "Question",
"name": "What protocols does Aethelforge support?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Aethelforge speaks MCP (Model Context Protocol), ACP (Agentic Commerce Protocol), AP2 (Agent Payments Protocol), and x402 (HTTP-native payments). Every transaction is signed and every settlement is traceable."
}
},
{
"@type": "Question",
"name": "Who builds on Aethelforge?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Two audiences: consumers (via Axis, a predictive replenishment agent that lives in your Gmail) and merchants (via the Forge SDK, which adds agent-commerce rails to any site in under an hour)."
}
},
{
"@type": "Question",
"name": "Is Aethelforge open source?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The Forge SDK is open source, published under the agentcommerce namespace on npm. The Aethelforge platform that orchestrates transactions across SDKs is proprietary."
}
},
{
"@type": "Question",
"name": "How does Aethelforge handle money?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Every transaction is gated: intent is signed by the consumer agent, orchestrated by Aethelforge, and settled via ACP or x402. Full cryptographic receipts are stored in the Live Ops Feed. Humans audit by default."
}
}
]
}[
{
"slug": "mcp",
"name": "MCP",
"expansion": "Model Context Protocol",
"steward": "Anthropic",
"status": "Supported",
"reference": "https://aethelforge.ai/protocols/mcp"
},
{
"slug": "acp",
"name": "ACP",
"expansion": "Agentic Commerce Protocol",
"steward": "OpenAI + Stripe",
"status": "Supported",
"reference": "https://aethelforge.ai/protocols/acp"
},
{
"slug": "ap2",
"name": "AP2",
"expansion": "Agent Payments Protocol",
"steward": "Google",
"status": "Supported",
"reference": "https://aethelforge.ai/protocols/ap2"
},
{
"slug": "x402",
"name": "x402",
"expansion": "HTTP 402 Native Payments",
"steward": "Coinbase",
"status": "Supported",
"reference": "https://aethelforge.ai/protocols/x402"
}
][
{
"key": "axis",
"title": "Axis",
"summary": "The consumer agent that reads your Gmail receipts, learns your household consumption, and queues replenishment for approval.",
"status": "LIVE",
"url": "https://axis.aethelforge.ai"
},
{
"key": "forge",
"title": "Forge SDK",
"summary": "Drop llms.txt + agent-commerce.json on your site. Agents discover your catalog, negotiate, pay — no human UI required.",
"status": "LIVE",
"url": "/forge"
}
]01What is Aethelforge?
Aethelforge is the orchestration layer for autonomous commerce and industrial operations — the system of record for the machine economy. It provides the rails, protocols, and settlement trail that let agents transact with each other on behalf of humans.
02What protocols does Aethelforge support?
Aethelforge speaks MCP (Model Context Protocol), ACP (Agentic Commerce Protocol), AP2 (Agent Payments Protocol), and x402 (HTTP-native payments). Every transaction is signed and every settlement is traceable.
03Who builds on Aethelforge?
Two audiences: consumers (via Axis, a predictive replenishment agent that lives in your Gmail) and merchants (via the Forge SDK, which adds agent-commerce rails to any site in under an hour).
04Is Aethelforge open source?
The Forge SDK is open source, published under the agentcommerce namespace on npm. The Aethelforge platform that orchestrates transactions across SDKs is proprietary.
05How does Aethelforge handle money?
Every transaction is gated: intent is signed by the consumer agent, orchestrated by Aethelforge, and settled via ACP or x402. Full cryptographic receipts are stored in the Live Ops Feed. Humans audit by default.
// internal
// machine-readable
// external
# see /robots.txt for full directives. /api/* is disallowed.