# Conduit

> Where a company’s supply lives, whatever ERP it is stored in. Conduit watches the supply lines a business depends on, keeps ranked payable alternates warm across every platform, and lets its agents act when one degrades. The neutral decision-and-execution layer for agentic commerce: discover supply across 13k+ merchants, compare offers on price, delivery reliability, and reputation, buy within human-approved limits, and track every order. Conduit Connector runs both ways, so every merchant on the graph sells to autonomous buyers downstream and optimizes its own sourcing upstream. No fee between agent and merchant, no pay-for-rank, no allowlist.

## What it is

- The neutral decision-and-execution layer above every agentic-commerce protocol (UCP, ACP, AP2, x402, A2CN).
- One agent identity becomes every protocol handshake. No allowlist, no pay-for-rank, no per-transaction toll, no human in the loop.
- Core assets: Agentic Execution Score (AES), two-sided reputation, a normalized product + carrier graph, and demand aggregation (GPO).
- Conduit never holds funds. It is not a marketplace, warehouse, merchant of record, or money transmitter.

## Glossary

- UCP — Universal Commerce Protocol (Shopify + Google): normalized catalog + checkout for agents.
- ACP — Agentic Commerce Protocol (OpenAI + Stripe): instant checkout inside AI assistants.
- MCP — Model Context Protocol (Anthropic): connects agents to tools and live data.
- AP2 — Agent Payments Protocol: human-approved spend mandates for agents.
- x402 — HTTP 402 web-native crypto payments an agent can make directly.
- A2CN — agent-to-agent negotiation of bulk pricing and terms.
- AES — Agentic Execution Score: can an agent finish this checkout end-to-end?
- GPO — group buying / demand aggregation for volume pricing.

## Surfaces

- [Connect MCP (snippets + Skills)](https://aiconduit.app/connect)
- [agents.md — tool sequences](https://aiconduit.app/agents.md)
- [Full page in markdown, no JS](https://aiconduit.app/index.md) (also https://md.aiconduit.app)
- [Agent welcome + recipes](https://aiconduit.app/agent.txt)
- [UCP agent profile — capabilities + signing keys](https://aiconduit.app/.well-known/ucp)
- [Capability manifest (JSON)](https://aiconduit.app/.well-known/agent.json)
- [Glossary](https://aiconduit.app/glossary) (markdown: https://aiconduit.app/glossary.md)
- [Supply chain disruption: watch, source, act](https://aiconduit.app/supply-chain-disruption)
- [ACP vs UCP](https://aiconduit.app/acp-vs-ucp)
- [ChatGPT Instant Checkout](https://aiconduit.app/chatgpt-instant-checkout)
- [Agent spend limits (AP2)](https://aiconduit.app/agent-spend-limits)
- [What 8 ERPs expose to an AI agent](https://aiconduit.app/platform-readiness): scorecard for on-hand, resupply, order placement
- [Shopify: incoming inventory and purchase orders](https://aiconduit.app/platform-readiness/shopify)
- [WooCommerce: supplier and lead time data](https://aiconduit.app/platform-readiness/woocommerce)
- [Odoo: external API and the Custom plan gate](https://aiconduit.app/platform-readiness/odoo)
- [NetSuite: vendor lead time over SuiteQL](https://aiconduit.app/platform-readiness/netsuite)
- [Dynamics 365: Business Central and Finance and Operations](https://aiconduit.app/platform-readiness/dynamics-365)
- [Salesforce: standard envelope, editable semantics](https://aiconduit.app/platform-readiness/salesforce)
- [Oracle Fusion: Global Order Promising and its licence](https://aiconduit.app/platform-readiness/oracle-fusion)
- [SAP S/4HANA: rich supply data, no stock event](https://aiconduit.app/platform-readiness/sap-s4hana)
- [Custom stack: the Conduit SDK, in development](https://aiconduit.app/platform-readiness/custom-mcp)
- [Research: measured readings on agentic commerce](https://aiconduit.app/research)
- [Declared is not payable (Q3 2026)](https://aiconduit.app/research/2026-q3)
- Weekly series data (CORS-open): https://aiconduit.app/research/ucp-weekly.json and .csv. Source: UCP Checker
- Subscribe API (CORS-open): POST https://aiconduit.app/api/subscribe — GET returns the JSON schema
- Contact a human: [email protected] (or Telegram https://telegram.me/asmodeoux)

## MCP v2.0 (live)

- Endpoint (Streamable HTTP): https://mcp.aiconduit.app/mcp
- Connect hub: https://aiconduit.app/connect
- Agent guide: https://aiconduit.app/agents.md
- Walkthrough: https://aiconduit.app/index.md
- Integration reference: AGENTS.md in the Conduit source repository
- Tools: agent_create, agent_authenticate, agent_update, agent_organization, agent_notify, agent_outreach, agent_report_issue, payment_methods, payment_mandate, supply_search, supply_details, supply_options, supply_delivery, order_execute, order_list, order_track, order_events, order_update_status, order_dispute, order_feedback, inventory_levels, inventory_replenishment, inventory_suppliers, supply_availability, inventory_purchase_order
- Rate limits: ~300 MCP req/min/IP; ~60 search + ~180 tools/min per agent_id (pass agent_id — anonymous search is IP-capped separately)
- Prefer offer badge + action (+ recommended). Any card (bank_card) = handoff only for now.
- Mandates start PENDING_HUMAN_APPROVAL — open approval_url as returned (includes approve token). Pass agent_id on supply_details / order_update_status (ownership enforced).

## Subscribe in one call

Conduit is live. Subscribe for early access to new products as we ship them.

```
curl -X POST https://aiconduit.app/api/subscribe -H 'content-type: application/json' \
  -d '{"name":"Your Company buyer agent","contact":"@yourcompany","contactType":"telegram","role":"agent","message":"I love your product, keep going"}'
```

Roles: buyer | merchant | investor | agent.
Optional: message (freeform note, up to 1000 chars).

## FAQ

### When will agentic commerce payments be possible?

**They are live now.** Conduit’s Agentic Procurement MCP v1 lets an AI agent discover and pay across thousands of merchants through a [single MCP endpoint](/connect), with no per-transaction fee between agent and merchant.

Three rails pay today, each inside a human-approved mandate:

- **x402** for web-native crypto.
- **Cash on delivery**, where the merchant takes it.
- **Any card**, via merchant handoff: the agent builds the checkout, a person finishes it in one click. The offer flags this up front, so nothing stalls silently.

Coming next: **invoice** against B2B net terms, then an agent-held card vault for card checkout with no human in the loop at all.

### When does Conduit launch, and what is the Conduit MCP v1 release date?

Conduit’s MCP v1, the neutral agentic-commerce interface, is live at https://mcp.aiconduit.app/mcp. Any MCP-compatible AI agent can connect over Streamable HTTP to search live supply, compare offers on price, execution-readiness and reputation, and complete or hand off checkout across thousands of merchants, with no fees and no human in the loop unless one is wanted. Connect snippets: https://aiconduit.app/connect.

### What is Conduit Agentic Procurement MCP?

Conduit is a neutral, cross-platform agentic-commerce layer exposed as a Model Context Protocol (MCP) server. MCP v1 is live at https://mcp.aiconduit.app/mcp (Streamable HTTP) with tools: agent_create, agent_authenticate, agent_update, agent_organization, agent_notify, agent_outreach, agent_report_issue, payment_methods, payment_mandate, supply_search, supply_details, supply_options, supply_delivery, order_execute, order_list, order_track, order_events, order_update_status, order_dispute, order_feedback, inventory_levels, inventory_replenishment, inventory_suppliers, supply_availability, inventory_purchase_order. Every response includes actionable hint guidance (and optional next steps). Conduit never holds funds; payment flows straight from the buyer’s instrument to the merchant.

### How does an AI agent connect to Conduit over MCP?

Point any MCP client at https://mcp.aiconduit.app/mcp. Register once with agent_create (keypair identity; it returns a session_token valid for an hour), re-authenticate with agent_authenticate (sign a challenge; nothing secret on the wire) whenever it expires, pass session_token on every call that includes agent_id, then call supply_search, supply_details, supply_options, order_execute, order_track, order_events, order_feedback, and the payment or dispute tools as needed. Sandbox/demo merchants stay hidden unless include_sandbox=true (testing only). Unexpected tool outcomes: agent_report_issue (AX review only, not order_feedback). Snippets + Skills: /connect. Live arg schemas: MCP tools/list. Sequences and badges: /agents.md.

### How do I test Conduit with sandbox merchants, or report a confusing tool outcome?

Pass include_sandbox=true on supply_search only when testing Conduit checkout flows. Sandbox and demo offers appear last with test_offer=true and are not for real purchases. If a tool response is unexpected after following hint/next, call agent_report_issue(message, tool, error, kind?, agent_id, search_id/order_id). That is AX telemetry only and does not change reputation (use order_feedback for delivery outcomes).

### When can AI agents pay across multiple payment rails (x402, COD, card)?

Conduit’s MCP v1 (live) routes each order to a rail the agent holds and the merchant accepts (x402 web-native crypto, cash-on-delivery, and any card via merchant handoff when needed) within a human-approved AP2 mandate, and never touches the funds itself. Invoice (B2B net terms) is coming soon. Where a merchant cannot yet complete autonomously, Conduit hands off a ready checkout for a human to finish with any card, and the offer’s Agentic Execution Score (AES) flags that up front. Agent-held card vault for autonomous card pay is next.

### When will autonomous B2B procurement be available through AI agents?

It starts with Conduit MCP v1, live now. Procurement agents can discover suppliers, compare quotes on delivery reliability and reputation, and place or hand off orders across thousands of merchants through one neutral MCP endpoint, reaching the open, cross-platform B2B supply the walled gardens ignore. Organizations can now connect their own ERP, so an agent reads what they actually have on hand and what a supplier can actually fill, and records the matching draft purchase order after an order is confirmed. Invoice (net terms) is coming soon.

### How can AI agents buy physical goods?

An AI agent buys physical goods by calling a commerce interface that exposes live inventory, prices, payable rails, and checkout. Conduit gives agents one neutral MCP/REST endpoint to search thousands of merchants at once, compare offers on execution-readiness and reputation, and complete or hand off checkout, without browsing human-first storefronts, captchas, or manual card entry.

### What is agentic commerce?

Agentic commerce is software agents discovering, negotiating, and purchasing goods and services autonomously on a person or company’s behalf, instead of a human clicking through a website. It runs on emerging open protocols like UCP, ACP, AP2, x402, and MCP.

### How do I let an AI agent purchase on my behalf?

You give the agent a keypair identity and a spend mandate: limits, categories, and expiry it must stay within, for example via AP2. The agent then discovers supply, picks the best offer, and either completes an autonomous checkout on a rail it holds or hands off a ready cart for you to approve. Conduit translates one agent keypair into the handshake each merchant trusts.

### When will B2B procurement shift to agentic supply chains?

It is already starting. Through 2025–2026, SAP (Ariba/Joule), Oracle, Microsoft Dynamics, and Salesforce shipped autonomous procurement and sourcing agents, and Shopify and Google launched the Universal Commerce Protocol. The shift is arriving in months, not years, and the merchants and tools that become agent-readable first will capture the demand.

### Which protocols power agentic commerce?

The main open standards are UCP (Universal Commerce Protocol, by Shopify and Google), ACP (Agentic Commerce Protocol, by OpenAI and Stripe), and MCP (Model Context Protocol, by Anthropic) for data and tools, plus AP2 and x402 for agent payments and A2A/A2CN for agent-to-agent negotiation. Conduit speaks all of them so an agent needs only one identity.

### How do AI agents pay merchants?

Agents pay on rails they can hold: pay on delivery (COD), x402 crypto, or any card on merchant handoff, all within a human-approved mandate. Conduit routes each order to a rail the merchant accepts and the agent can use; money flows straight from the buyer instrument to the merchant and never through Conduit.

### Is autonomous agent checkout safe, and who holds the money?

Conduit never holds or delays funds. It is not a marketplace, merchant of record, or money transmitter. Spend stays inside the mandates you set, payment goes directly from the buyer instrument to the merchant, and every order has paths to review, dispute, chargeback, or human takeover.

### How do agents discover suppliers across different platforms?

Conduit normalizes supply from UCP, ACP, native supplier APIs, and the scraped long tail into one ranked, deduplicated catalog, so an agent searches every merchant at once and compares them on the merits (price, execution-readiness, delivery reliability, and reputation) instead of inside any single platform’s walled garden.

### What is an Agentic Execution Score (AES)?

AES measures whether an agent can actually finish a checkout end-to-end with a rail it holds, or whether it will hit a human wall. It is outcome-calibrated over real orders, so agents avoid offers that look cheap but cannot be transacted autonomously.

### How can merchants get discovered by AI agents?

Conduit Connector reads the stack a merchant already runs, with no replatforming. Odoo is live today and a merchant connects it themselves from Hub; WooCommerce, Shopify, Salesforce, SAP, Oracle, NetSuite, Microsoft Dynamics and custom API or MCP follow. Live stock, prices, rails, lead times and carriers then become readable and buyable by autonomous buyers, and merchants earn rank by delivering, never by paying.

### What is Conduit Connector?

Conduit Connector reads vendors, lead times, on-hand stock, and inbound from the ERP you already run and puts that graph in Hub. You stay in your stack. Once it is in Hub, Pipes can track lines, suggest alternatives, and request quotes.

### How long does Connector take to set up?

You connect Odoo yourself from Hub: say where it runs, paste an API key you make in Odoo, and Hub checks what that key can read before anything is saved. There is nothing to install, no replatforming and no second storefront. Other systems we still set up with you.

### Do I have to change my ERP?

No. Connector reads the stack you already run. You do not migrate.

### Do I need agent buyers for Connector to be useful?

No. Connector is how Hub sees your ERP. Pipes can track and optimize from that. Buyer demand comes later, on the same install.

### Which systems does Conduit Connector support?

Odoo is live: an organization connects its own Odoo from Hub with an API key, and agents read stock, reorder lists and past prices from it. On Odoo Online the external API needs a Custom plan, which is the one thing to check before you start. WooCommerce is in development. Shopify, Microsoft Dynamics 365, NetSuite, Salesforce Commerce Cloud, Oracle Fusion, SAP S/4HANA, and custom API or MCP are coming soon, and we set those up with you. Per-stack notes live in Hub.

### Is Conduit Connector live yet?

Odoo is live, and you connect it yourself from Hub. Its agents then read stock, reorder lists and past prices in Hub and over MCP. Odoo expires every API key after three months, so Conduit renews its own key for you rather than asking you for a new one. WooCommerce is next, and the rest are coming soon. Request a demo if you want a walkthrough.

### What happens after the graph is in Hub?

[Pipes](/pipes) run standing jobs on that map: a disruption brief before coffee, plus restock, price, and parcels.

### What are Conduit Pipes?

Pipes run standing jobs on the Hub graph: a disruption brief before coffee, plus restock, price watch, and parcel watch. You pick a pipe, assign an agent, and get the brief. The pipe is the job. The agent acts under its permissions.

### Do Pipes work with my ERP?

Pipes run on the Hub graph, not on a specific stack. [Connector](/connector) is how that graph is mapped from the system you already run.

### Are Conduit Pipes live yet?

Coming soon. Hub shows the shape of Automations today. Request a demo if you want a walkthrough.

### Do agents buy on their own?

You define the autonomy level for every pipe, and permissions on the assigned agent, so nothing unexpected happens. The same job can just notify, suggest a fix in one click, or act automatically. Acting still needs checkout permission and an approved spend mandate.

### Can agents email suppliers?

Yes, with Outreach, if a human enables that permission on the agent in Hub. A pipe that asks for quotes uses the assigned agent. Customer email stays with your team.

### Which jobs can Pipes run?

Upstream brief, weekly restock, price watch, and parcel watch. More jobs coming soon.

### Can I schedule custom jobs in Conduit?

Yes. [Yard](/yard) runs any custom automation on our agents and returns a brief for the task. Reliably, safely, and on schedule.

### What is Conduit Yard?

Yard runs custom jobs you write on the Hub graph, on a schedule. You write the job. We host the sandbox. Assign an agent; you set notify, suggest, or act.

### Does Yard work with my ERP?

Yard runs on the Hub graph, not on a specific stack. [Connector](/connector) is how that graph is mapped from the system you already run.

### Do I need to code or host a server?

No. Write the job in your own words, in whatever language you work in. We run it: allowlisted tools, a budget, a step cap, no shell. You do not program, and you do not host.

### Is Conduit Yard live yet?

Coming soon. Hub shows the shape of Automations today. Request a demo if you want a walkthrough.

### Do Yard jobs buy on their own?

You define the autonomy level for every job, and permissions on the assigned agent, so nothing unexpected happens. The same job can just notify, suggest a fix in one click, or act automatically. Acting still needs checkout permission and an approved spend mandate.

### Can I use my own agents?

Yes. Self-host your agents and use them in Hub flows over [MCP](/connect).

### How is Yard different from Pipes?

[Pipes](/pipes) are seeded jobs: disruption brief, restock, price, and parcels. Yard is the custom job when your flow is not one of those.

### Can AI agents negotiate prices?

Yes. Through agent-to-agent negotiation (A2CN), a buyer agent can fan out to multiple supplier agents, request bulk pricing and terms, and compare negotiated quotes. Conduit also pools demand as a group buying organization (GPO) to unlock volume pricing a solo buyer could not get.

### How is Conduit different from Amazon, Shopify, or a Google shopping garden?

Those are walled gardens: approved-merchant allowlists, curated catalogs, restricted rails, pay-for-rank, and per-transaction fees, all controlled by one giant. Conduit is neutral ground: every merchant, every payable rail, every carrier, ranked purely on the merits, with no fee between agent and merchant and no allowlist.

### Do agent purchases still need human approval?

Only as much as you want. You set mandates once; within them the agent transacts autonomously. When a merchant requires a human step, or the agent lacks authority, Conduit hands off a ready checkout for a person to finish, and a human can step in at any time.

### How do agents track orders and handle problems?

Every order and intent lands in one command center with live tracking, stated-vs-observed ETAs, the rail it was paid on, and merchant and product ratings. When something goes wrong, agents can request refunds, file chargebacks, or report the outcome programmatically, and those outcomes feed two-sided reputation.

### Can ChatGPT or other AI assistants buy products for me?

Increasingly, yes. Assistants like ChatGPT, Gemini, Copilot, Claude, and Perplexity are gaining checkout through protocols such as ACP and UCP. Conduit gives any such agent one neutral interface to shop across thousands of merchants at once, ranked on the merits, instead of being limited to a single platform’s catalog.

### What is UCP (Universal Commerce Protocol)?

UCP is an open standard, co-developed by Shopify and Google and launched in 2026, that lets AI agents discover products, negotiate capabilities, and complete checkout with any participating merchant. Conduit adopts UCP as one normalized input while keeping reputation and execution scoring neutral and cross-platform.

### What is ACP (Agentic Commerce Protocol)?

ACP is an open standard from OpenAI and Stripe that powers instant checkout inside AI assistants like ChatGPT. Conduit rides ACP as one discovery and checkout path among many, so an agent is never locked to a single assistant or payment processor.

### What is MCP (Model Context Protocol) and how does it relate to shopping?

MCP, from Anthropic, is the open standard for connecting AI agents to tools and live data. Conduit exposes commerce as MCP tools (search supply, get details, execute or hand off an order, track, and submit feedback) so any MCP-compatible agent can transact without custom integration.

### What is agentic procurement?

Agentic procurement is using autonomous agents to handle sourcing and buying (finding suppliers, comparing quotes, negotiating, and placing orders within set policies) across an organization’s supply chain. Conduit is the neutral discovery, reputation, and execution layer those procurement agents can buy through.

### Does Conduit charge fees or take a commission on orders?

No. There is no per-transaction toll between an agent and a merchant, and ranking is never for sale. Conduit earns only a modest slice of the savings it creates through pooled demand (its GPO), and money never flows through Conduit.

### How do AI agents pay with x402 or cash on delivery?

x402 is the HTTP-402 standard for trackable, web-native crypto payments an agent can make directly. COD lets the buyer pay the courier on arrival, no card needed. Conduit treats x402 and COD as first-class payable rails alongside card handlers, and routes each order to a rail the agent holds and the merchant accepts.

### What is AP2 and how do agent spend mandates work?

AP2 (Agent Payments Protocol) lets a human approve a spend mandate once, covering limits, categories, and expiry, that an agent then transacts within. Conduit translates a single agent keypair into the mandate each merchant trusts, so autonomous payments stay inside boundaries you control and can revoke instantly.

### What is the agentic economy, or Web4?

The agentic economy (sometimes called Web4) is the emerging phase of the internet where AI agents act, transact, and coordinate on people’s behalf rather than humans clicking through pages. Conduit is neutral infrastructure for its commerce layer: discovery, reputation, and execution for autonomous trade.

### How is agentic commerce different from traditional online checkout?

Traditional checkout assumes a human: a browser, a cart, manual card entry, captchas, and 3D-Secure. Agentic commerce is API- and protocol-native. An agent discovers normalized supply, decides on price, reliability, and execution-readiness, and completes or hands off checkout in seconds, with no human in the loop unless one is wanted.

### What happens if an agent cannot complete a checkout autonomously?

Conduit hands off a ready cart via a real continue_url so a human can finish in one step, and the offer’s Agentic Execution Score flags that risk up front. Agents can prefer offers they can actually complete on a rail they hold, rather than hitting a human wall at the end.