Sector brief · April 2026
Primary profile: Organization (/o/)
Procurement and supply chain
Sourcing agents need inventory truth, negotiation state, and settlement that does not die on card minimums. Email and HTML are the wrong wire format for that loop.[1]
Market context
AI-driven sourcing already captures a meaningful share of B2B procurement; one 2025 market writeup places an AI sourcing segment on the order of $184B.[3] Enterprises want faster RFQs and fewer humans in the loop for repeat buys.[5]
The constraint is rarely "we lack a model." It is dirty supplier data, fragmented catalogs, and payment rails that punish small autonomous trades.[4]
Structural gaps
Where incumbents sit
Zip-style internal orchestration, Coupa-style source-to-pay suites, and Pactum-style email negotiators already own pieces of the workflow.[5][6][7] The gap is an open, machine-first negotiation and settlement layer between buyer agents and supplier systems.
Building on more.md (implementation map)
Trading partners as organization profiles (`/o`)
Model buyers, suppliers, and integrators as `/o` entities so contracts, risk scores, and negotiation state attach to legal entities rather than anonymous endpoints. Catalog lines can still surface as linked `/p` rows when part numbers matter.
Discovery without scraping
Publish `/.well-known/eep.json` so partners map your API and entity types deterministically.
Pulse commerce state machine
Run offer, counter, and accept flows over WebSocket with explicit transitions instead of inferring intent from email threads.
Programmable settlement
Pair payment gates with x402-style flows where comparisons suggest card-based agent checkout is too expensive for micro-purchases.[4]
Competitive context
Names below appear in third-party sources listed under References. The contrast column sketches where an agent-first build on more.md sits relative to each player. Complement in some layers, substitute in others.
| Player | Position in market | Contrast with more.md-shaped build |
|---|---|---|
| Zip | Internal procurement agents for approvals. | Inside-the-company workflows vs buyer–supplier negotiation. |
| Coupa | Source-to-pay with predictive spend analytics. | Traditional banking rails vs programmable low-fee settlement. |
| Pactum | Email-loop supplier negotiation. | Lossy natural language vs JSON/TOON over WebSocket. |
References
- [1]more.md whitepaper
- [2]Medium — TOON vs JSON in high-scale LLM systems
- [3]Medium — Rise of AI sourcing companies (2025)
- [4]Hypertrends — Agentic payments (x402 vs ACP vs AP2 vs TAP)
- [5]Tropic — Best AI procurement software 2026
- [6]Ivalua — AI procurement software buying guide
- [7]Suplari — Top AI procurement tools