Vinculum
Vinculum is an AI-driven SaaS company for omnichannel retail and ecommerce. Its Vin eRetail platform unifies order management (OMS), warehouse management (WMS), product information management (PIM), and endless-aisle omnichannel retail across 150+ sales channels and marketplaces for 1,000+ brands, processing 20M+ orders monthly. The Vin eRetail REST API exposes orders, returns, products/SKUs, inventory/stock, vendors, purchase orders, inbounds, advance shipping notices, transfers, and fulfillment operations, alongside a SellerPanel V3 marketplace API for listing, order, and courier-allocation flows. Originally surfaced as an Accel portfolio company, this profile has been enriched from Vinculum's published Swagger.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Vinculum the way a machine reads it — 21 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Vinculum scores 29.8/100 (emerging), with a separate agent-readiness read of 62/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Vinculum
Each block below is one kind of artifact we hold for Vinculum. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Vinculum Advance Shipping Notice API
API to retrieve or manipulate ASN related information.
Vinculum Authentication Process API
API to retrieve or manipulate Order related information.
Vinculum Common API
API to facilitate Common Operations.
Vinculum Courier Allocation Process API
API to retrieve or manipulate Order related information.
Vinculum Inbounds API
API to retrieve or manipulate Inbound related information.
Vinculum Listing Managment API
API to retrieve or manipulate Order related information.
Vinculum Manifest API
API to create Manifest
Vinculum Order Managment API
API to retrieve or manipulate Order related information.
Vinculum Order Returns API
API to retrieve or create return for an order.
Vinculum Orders API
API to retrieve or manipulate Order related information.
Vinculum Products API
API to retrieve or manipulate SKU related information.
Vinculum Purchase Orders API
API to retrieve or manipulate Purchase Order related information.
Vinculum Putaway API
API to create putaway
Vinculum Return to Vendor API
API to retrieve or manipulate Return to Vendor related information.
Vinculum Stock API
API to retrieve or manipulate Stock related information.
Vinculum Transfers API
API to create Stock Transfer Order in Eretail
Vinculum Vendors API
API to retrieve or manipulate Vendor related information.
Scroll within the panel for all 17 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
vinculum-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Vinculum Rate Limits
RATE LIMITSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Vinculum — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/vinculum · machine-readable index on apis.io