1Factory
1Factory is a leading provider of quality management software solutions for manufacturing companies. The platform helps businesses streamline their operations, improve efficiency, and ensure product quality at every stage of the production process. Features include real-time monitoring, automated data collection, advanced analytics, and integration with ERP and PLM systems via a REST API.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles 1Factory the way a machine reads it — 218 machine-readable artifacts across 7 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 — 1Factory scores 58.8/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile 1Factory
Each block below is one kind of artifact we hold for 1Factory. 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 7
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.
1Factory Customers API
Data shared with your organization by your customers.
1Factory Manufacturing API
Data related to parts manufactured by your organization.
1Factory Part Master API
Part Master defines the part numbers, revisions and other information for parts referenced in Plans, Inspections, FAIs etc.
1Factory QMS API
Data related to Quality
1Factory Receiving API
Data related to parts received by your organization.
1Factory Suppliers API
Data shared with your organization by your suppliers, or details about your suppliers.
1Factory Work Orders API
Work Orders define a list of current work order primary & secondary identifiers that may be used as identifiers on Inspections & FAIs.
Scroll within the panel for all 7 ·
Open Collections 1
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).
1Factory 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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate 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.
1Factory 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.
1Factory Finops
FINOPSFeatures 7
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.
Manufacturing Quality Control
Factory floor quality control, inspection planning, and statistical process control (SPC)
Quality Management System (QMS)
Document control, training management, audits, and compliance workflows
Supplier Quality Management
Vendor oversight, incoming inspection management, and supplier corrective actions
First Article Inspection (FAI)
Automated drawing ballooning and AS9102-compliant first article inspection
Real-Time Analytics
Real-time quality analytics and audit-ready reporting dashboards
CMM Data Integration
Automatic import of CMM measurement data with SPC analysis
ERP/PLM Integration
API-based integration with ERP and PLM systems for part and work order sync
Scroll within the panel for all 7 ·
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.
1Factory Context
JSON-LDSpectral 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.
1Factory API Rules
SPECTRAL1Factory API Rules
SPECTRALJSON Schema 62
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.
Address
JSON SCHEMAAssemblyEntry
JSON SCHEMAAssembly
JSON SCHEMACapaList
JSON SCHEMACapa
JSON SCHEMACertification
JSON SCHEMAclosed_on
JSON SCHEMAComplaintList
JSON SCHEMAComplaint
JSON SCHEMAcreated_by_username
JSON SCHEMAcreated_on
JSON SCHEMAcustomer_name
JSON SCHEMAFaiDetail
JSON SCHEMAFaiList
JSON SCHEMAFai
JSON SCHEMAfai_type
JSON SCHEMAID
JSON SCHEMAinsp_ident_1
JSON SCHEMAinsp_ident_2
JSON SCHEMAinsp_ident_3
JSON SCHEMAInspectionDetail
JSON SCHEMAInspectionList
JSON SCHEMAInspection
JSON SCHEMAinspection_type
JSON SCHEMAIssue
JSON SCHEMAlot_size
JSON SCHEMAmachines
JSON SCHEMANcrList
JSON SCHEMANcr
JSON SCHEMANewFai
JSON SCHEMANewInspection
JSON SCHEMANewMfgInspection
JSON SCHEMANewPartMaster
JSON SCHEMANewRecInspection
JSON SCHEMAnumber_of_parts
JSON SCHEMAoperation
JSON SCHEMAowner
JSON SCHEMAPartData
JSON SCHEMApart_description
JSON SCHEMAPartMasterList
JSON SCHEMAPartMaster
JSON SCHEMApart_number
JSON SCHEMAparts_failed
JSON SCHEMAparts_passed
JSON SCHEMAPlanDetail
JSON SCHEMAPlanList
JSON SCHEMAPlan
JSON SCHEMAproject_identifier
JSON SCHEMAQualification
JSON SCHEMArev
JSON SCHEMASpecInspectionType
JSON SCHEMASpecification
JSON SCHEMAstatus
JSON SCHEMASubPartList
JSON SCHEMASuperInspection
JSON SCHEMASupplierList
JSON SCHEMAsupplier_name
JSON SCHEMAsupplier_number
JSON SCHEMASupplier
JSON SCHEMAupdated_on
JSON SCHEMAUser
JSON SCHEMAWorkOrderList
JSON SCHEMAScroll within the panel for all 62 ·
JSON Structure 62
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.
1Factory Address Structure
JSON STRUCTURE1Factory Assembly Entry Structure
JSON STRUCTURE1Factory Assembly Structure
JSON STRUCTURE1Factory Capa List Structure
JSON STRUCTURE1Factory Capa Structure
JSON STRUCTURE1Factory Certification Structure
JSON STRUCTURE1Factory Closed On Structure
JSON STRUCTURE1Factory Complaint List Structure
JSON STRUCTURE1Factory Complaint Structure
JSON STRUCTURE1Factory Created By Username Structure
JSON STRUCTURE1Factory Created On Structure
JSON STRUCTURE1Factory Customer Name Structure
JSON STRUCTURE1Factory Fai Detail Structure
JSON STRUCTURE1Factory Fai List Structure
JSON STRUCTURE1Factory Fai Structure
JSON STRUCTURE1Factory Fai Type Structure
JSON STRUCTURE1Factory Id Structure
JSON STRUCTURE1Factory Insp Ident 1 Structure
JSON STRUCTURE1Factory Insp Ident 2 Structure
JSON STRUCTURE1Factory Insp Ident 3 Structure
JSON STRUCTURE1Factory Inspection Detail Structure
JSON STRUCTURE1Factory Inspection List Structure
JSON STRUCTURE1Factory Inspection Structure
JSON STRUCTURE1Factory Inspection Type Structure
JSON STRUCTURE1Factory Issue Structure
JSON STRUCTURE1Factory Lot Size Structure
JSON STRUCTURE1Factory Machines Structure
JSON STRUCTURE1Factory Ncr List Structure
JSON STRUCTURE1Factory Ncr Structure
JSON STRUCTURE1Factory New Fai Structure
JSON STRUCTURE1Factory New Inspection Structure
JSON STRUCTURE1Factory New Mfg Inspection Structure
JSON STRUCTURE1Factory New Part Master Structure
JSON STRUCTURE1Factory New Rec Inspection Structure
JSON STRUCTURE1Factory Number Of Parts Structure
JSON STRUCTURE1Factory Operation Structure
JSON STRUCTURE1Factory Owner Structure
JSON STRUCTURE1Factory Part Data Structure
JSON STRUCTURE1Factory Part Description Structure
JSON STRUCTURE1Factory Part Master List Structure
JSON STRUCTURE1Factory Part Master Structure
JSON STRUCTURE1Factory Part Number Structure
JSON STRUCTURE1Factory Parts Failed Structure
JSON STRUCTURE1Factory Parts Passed Structure
JSON STRUCTURE1Factory Plan Detail Structure
JSON STRUCTURE1Factory Plan List Structure
JSON STRUCTURE1Factory Plan Structure
JSON STRUCTURE1Factory Project Identifier Structure
JSON STRUCTURE1Factory Qualification Structure
JSON STRUCTURE1Factory Rev Structure
JSON STRUCTURE1Factory Spec Inspection Type Structure
JSON STRUCTURE1Factory Specification Structure
JSON STRUCTURE1Factory Status Structure
JSON STRUCTURE1Factory Sub Part List Structure
JSON STRUCTURE1Factory Super Inspection Structure
JSON STRUCTURE1Factory Supplier List Structure
JSON STRUCTURE1Factory Supplier Name Structure
JSON STRUCTURE1Factory Supplier Number Structure
JSON STRUCTURE1Factory Supplier Structure
JSON STRUCTURE1Factory Updated On Structure
JSON STRUCTURE1Factory User Structure
JSON STRUCTURE1Factory Work Order List Structure
JSON STRUCTUREScroll within the panel for all 62 ·
Examples 62
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.
1Factory Address Example
EXAMPLE1Factory Assembly Example
EXAMPLE1Factory Capa Example
EXAMPLE1Factory Capa List Example
EXAMPLE1Factory Closed On Example
EXAMPLE1Factory Complaint Example
EXAMPLE1Factory Created On Example
EXAMPLE1Factory Fai Detail Example
EXAMPLE1Factory Fai Example
EXAMPLE1Factory Fai List Example
EXAMPLE1Factory Fai Type Example
EXAMPLE1Factory Id Example
EXAMPLE1Factory Inspection Example
EXAMPLE1Factory Issue Example
EXAMPLE1Factory Lot Size Example
EXAMPLE1Factory Machines Example
EXAMPLE1Factory Ncr Example
EXAMPLE1Factory Ncr List Example
EXAMPLE1Factory New Fai Example
EXAMPLE1Factory Operation Example
EXAMPLE1Factory Owner Example
EXAMPLE1Factory Part Data Example
EXAMPLE1Factory Part Master Example
EXAMPLE1Factory Part Number Example
EXAMPLE1Factory Plan Detail Example
EXAMPLE1Factory Plan Example
EXAMPLE1Factory Plan List Example
EXAMPLE1Factory Rev Example
EXAMPLE1Factory Status Example
EXAMPLE1Factory Supplier Example
EXAMPLE1Factory Updated On Example
EXAMPLE1Factory User Example
EXAMPLEScroll within the panel for all 62 ·
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 5
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.
Manufacturing Inspection
Create and track manufacturing inspections with measurement data and SPC analysis
Supplier Qualification
Manage supplier certifications, conduct receiving inspections, and track supplier CAPAs
Non-Conformance Management
Log, track, and resolve non-conformances, CAPAs, and customer complaints
First Article Inspection
Conduct and document AS9102 first article inspections for aerospace and defense
ERP Data Sync
Synchronize part master data, work orders, and inspection results with ERP systems
Integrations 3
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
Sync part master data, work orders, and inspection records with ERP platforms
PLM Systems
Connect with PLM systems for design-to-manufacturing quality continuity
CMM Equipment
Auto-import measurement data from CMM equipment directly into inspections
Resources
Every other property we hold for 1Factory — 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 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Access & Security 3
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/1factory · machine-readable index on apis.io