Integration release status

Check which supplier capabilities are published, implemented, or still planned.

Status date: 7 September 2026. Supplier record contract: 0.1.0.

Capability	Status
Integration guides and buyer/supplier agent skills	Published documentation
Downloadable TypeScript/Python starter clients and JSON schema	Preview source files; not npm or PyPI packages
Automatic first key for a verified supplier company owner	Implemented; application release and production signup acceptance pending
GET /api/v1/supplier/me	Implemented; production availability pending
POST /api/v1/supplier/validate	Implemented; production availability pending
Any-system guides, any-language HTTP examples and connection-plan template	Published preparation tools; no stack-specific SDK requirement
Recurring API ingestion, managed system connections and feed health monitoring	Planned
Scheduled structured exports/email intake	Planned; no published intake mailbox or receiving contract
Authenticated buyer/supplier data intake over A2A	Planned; no company-data skill advertised
Public A2A overview and Insights	Live read-only research; cannot receive company data
Recurring buyer requirement writes	Planned; current private writes use the supported website
Supplier-hosted provider endpoints and admission conformance tooling	Proposed in the contract guide
Buyer-facing publication of a connected feed	Requires a separate admitted feed and agreed sharing scope
Quotes, reservations, orders and payments through a supplier key	Unsupported

The any-system guide explains how to prepare each route; the A2A guide documents the current public agent separately. The preview clients do not install a connector, schedule a sync, or activate a supplier. An agent skill does not give its user account or commercial authority.

Check before calling

The live application contract is at https://middlemantechnologies.com/openapi.json. The supplier preview OpenAPI file describes the implementation being prepared for release.

If the live contract lacks a supplier route, wait for the application release. Do not treat a 404, login page or framework response as a successful integration. When available, /api/v1/supplier/me reports the capabilities your key can use. This preview reports validate: true, with ingest, publish, quote, reserve and order all false.

The existing public read API is separate and does not require a supplier key.