What does Forge SDK actually install?

Two files at your site root (llms.txt + agent-commerce.json) and an optional edge helper for signed settlement. That's it. Your existing payment setup stays untouched — Forge sits in front of it.

Do I have to rewrite my site?

No. Forge SDK is additive. Your human-facing site stays exactly as it is. Agents discover your catalog through the JSON manifest; humans continue to browse normally.

What protocols does Forge speak?

MCP for tool-calling, ACP for commerce handshakes, AP2 for agent payment authorization, and x402 for inline micropayments. You declare which ones you support in your manifest; Aethelforge handles the translation if an agent arrives speaking a different one.

The SDK itself is open source under the @agentcommerce npm namespace. Aethelforge takes a small per-transaction fee on settlement through the gate — a flat basis-point model, not a percentage grab. Numbers on the pricing page when it lands.

PRODUCT · MERCHANT

Forge SDK

The rails you install on your site so other people's agents can transact with you. Under an hour end to end.

THE ANSWER

What is Forge SDK?

Forge SDK is the merchant-side library in the Aethelforge platform. You drop llms.txt and agent-commerce.json at your site root and your catalog is agent-legible. Agents discover you, negotiate terms, and pay through a signed handshake — all without a human UI. Under an hour from install to live.

Install

# 1. CLI
npm i -g @agentcommerce/cli

# 2. init in your site root
cd your-site && agentcommerce init

# 3. deploy (drops llms.txt + agent-commerce.json at root)
agentcommerce deploy

The CLI inspects your site's existing product schema (OpenGraph, JSON-LD Product markup, sitemap) and scaffolds an agent-commerce.jsonmanifest you can edit in a single file. Commit it, deploy it, and you're discoverable.

What an agent sees

Once deployed, any AI agent that visits your domain reads /agent-commerce.json and learns:

Your catalog format. Where the product endpoints live, what fields they expose, how stock is represented.
Your negotiation parameters. Which variables are open (size, delivery window, substitution), which are fixed.
Your protocol support. Whether you prefer ACP, x402, or both, and which settlement rails you accept.
Your trust signals. Dispute-resolution policy, issuer references, human-in-loop thresholds.

What you keep

Forge SDK is additive. Your existing website — human-facing, design-polished, CRO-tuned — stays exactly as it is. Forge doesn't replace your checkout; it sits in front of it. When an agent-initiated transaction reaches you, Forge handles the protocol negotiation and hands a verified intent to your existing payment system. You see the same order event you would from a human order, with one extra field: the signed agent delegation.

Who's live

Eight iSimplifyMe domains run Forge SDK in production today. If you want to see a live manifest, start here: endsights.com/agent-commerce.json. Every shape you need to copy is already there.

What's coming

The SDK currently targets static-catalog merchants. Dynamic catalog support (real-time inventory, negotiated pricing tiers) is the next milestone, tracked on our roadmap. If you're interested in early access, reach out through the contact link in the footer.