Integrate your company’s data

Connect your existing product, pricing, inventory or capacity system to Middleman.

Your existing system stays authoritative, whether it is a spreadsheet, a database table, an ERP or a custom application. Map products, prices, inventory, production capacity and services in your own stack, then prepare recurring delivery through an enabled route. There is no separate catalogue to maintain by hand. Start with any-system onboarding if you want your agent to choose the simplest connection.

Developer preview — 7 September 2026. These guides and starter clients are available now. Automatic supplier keys and the authenticated validation endpoints are implemented for an upcoming application release; production signup and API availability have not yet been verified. Recurring feed ingestion and buyer-facing publication are not available through this preview. Read release status before connecting.

From signup to a connected feed

1. Join as a supplier

   Open supplier signup, verify your work email and select or create the company you are authorized to represent. Supplier and buyer memberships are separate.

2. Save your company’s API key

   In the upcoming integration console, the verified company owner receives a first key automatically. Save the full value in your application’s secret store when shown. Later sign-ins show its masked identifier; they do not create another key or reveal the secret again. Key lifecycle.

3. Map the authoritative source

   Choose the system that owns each field. Preserve its record IDs, units, exact decimal prices and observation times. Use the mapping guide and record contract.

4. Validate a small sample

   Use any HTTPS-capable language or a TypeScript or Python starter once the validation API is available. Start with a few approved records, including zero stock and missing prices. A successful validation saves no catalogue data.

5. Complete feed admission

   Prepare repeatable synchronization, outage handling, withdrawal handling and a clear data-sharing scope. Recurring feed activation requires compatibility and source-access review; a key or valid sample does not activate a feed.

Choose how to integrate

Path	What you maintain	Best fit
Existing API	A mapping from source records to the Middleman contract	Your catalogue or operational system already has an API
SDK-assisted adapter	A small service or scheduled job in your own environment	Custom databases, complex rules, or several source systems
Connected system	A source reader and field mapping in an approved integration platform	Your team already uses an automation tool
Scheduled export or email	A repeatable structured export and verified processing receipts	Your source generates reports; intake is planned
Authenticated A2A	A source reader and a declared company-data handoff	Your agent supports A2A; data intake is planned
Your own agent	The agent prepares the appropriate path in your current stack	Any capable agent with approved access to your tools

A guided field-mapping UI is planned. A spreadsheet can remain your maintained source, read repeatedly by a job or durable agent runner. The finished connection must keep working independently of this chat. See source patterns, recurring updates and email, and A2A. A one-time file helps prepare the mapping but does not establish a feed.

Let your agent onboard you

Use the complete supplier skill and a ready-to-copy brief.

Build with your team

Download the clients, schema and example records.

Design reference

OpenRouter separates provider declarations, compatibility review and admission from client SDK access. We apply that pattern to physical products and capacity: a common data contract, explicit capabilities and source freshness. Physical stock is an observation, not a reservation. This is Middleman’s own contract, not an OpenRouter-compatible API. OpenRouter provider guide, provider onboarding, client SDKs.