3M
3M is a global science and manufacturing company. The 3M Partner and Supplier API provides real-time access to product, pricing, order, delivery, and invoice data for partners and suppliers, enabling automated commerce and supply chain integration.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles 3M the way a machine reads it — 71 machine-readable artifacts across 1 API, 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 — 3M scores 36.4/100 (thin), with a separate agent-readiness read of 25/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from 3M's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/3m/"
title="3M on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/3m.svg"
alt="3M Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/3m/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/3m/"
title="3M on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/3m/card.svg"
alt="3M Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile 3M
Each block below is one kind of artifact we hold for 3M. 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 4
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.
3M Deliveries API
Track delivery status and logistics for partner orders.
3M Invoices API
Retrieve invoice status and details for billing reconciliation.
3M Orders API
Submit and track purchase orders with 3M.
3M Products API
Retrieve product catalog and pricing information.
Open Collections 6
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTION3M Partner and Supplier Deliveries API
OPEN COLLECTION3M Partner and Supplier Deliveries Invoices API
OPEN COLLECTION3M Partner and Supplier Deliveries Orders API
OPEN COLLECTION3M Partner and Supplier API
OPEN COLLECTION3M Partner and Supplier Deliveries Products API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
3M Plans Pricing
PLANSRate 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.
3M Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
3M Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Product Catalog Access
Real-time access to 3M product catalog with availability and pricing information
Partner Pricing
Negotiated pricing tiers based on partner agreements
Order Management
Submit and track purchase orders programmatically
Delivery Tracking
Real-time delivery status and carrier tracking information
Invoice Retrieval
Access invoices for billing reconciliation and accounts payable automation
OAuth 2.0 Authentication
Secure bearer token authentication via client credentials OAuth 2.0 flow
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
3M API Rules
SPECTRAL3M API Rules
SPECTRALJSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CreateOrderRequest
JSON SCHEMADeliveryList
JSON SCHEMADelivery
JSON SCHEMAInvoiceList
JSON SCHEMAInvoice
JSON SCHEMAOrderItem
JSON SCHEMAOrderList
JSON SCHEMAOrder
JSON SCHEMAProductList
JSON SCHEMAProductPrice
JSON SCHEMAProduct
JSON SCHEMAShippingAddress
JSON SCHEMAScroll within the panel for all 12 ·
JSON Structure 12
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
3M Partner Supplier Api Create Order Request Structure
JSON STRUCTURE3M Partner Supplier Api Delivery List Structure
JSON STRUCTURE3M Partner Supplier Api Delivery Structure
JSON STRUCTURE3M Partner Supplier Api Invoice List Structure
JSON STRUCTURE3M Partner Supplier Api Invoice Structure
JSON STRUCTURE3M Partner Supplier Api Order Item Structure
JSON STRUCTURE3M Partner Supplier Api Order List Structure
JSON STRUCTURE3M Partner Supplier Api Order Structure
JSON STRUCTURE3M Partner Supplier Api Product List Structure
JSON STRUCTURE3M Partner Supplier Api Product Price Structure
JSON STRUCTURE3M Partner Supplier Api Product Structure
JSON STRUCTURE3M Partner Supplier Api Shipping Address Structure
JSON STRUCTUREScroll within the panel for all 12 ·
Examples 12
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 12 ·
Security 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Automated Procurement
Automate purchase order creation based on inventory levels or demand signals
Supply Chain Visibility
Track order and delivery status in real-time for supply chain planning
ERP Integration
Integrate 3M product data, orders, and invoices with ERP systems
Price Comparison
Retrieve partner-negotiated pricing for procurement decision support
Accounts Payable Automation
Automatically retrieve and reconcile invoices with purchase orders
Inventory Management
Check product availability and pricing for inventory replenishment
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
ERP Systems
Integrate product, order, and invoice data with SAP, Oracle, or Microsoft Dynamics
Procurement Platforms
Connect with procurement management platforms for automated ordering
Accounting Systems
Sync invoices with accounting software for automated AP reconciliation
Supply Chain Platforms
Feed order and delivery data into supply chain visibility platforms
Resources
Every other property we hold for 3M — 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.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/3m · machine-readable index on apis.io
This is an independent, third-party profile of 3M, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.