Assembly OSM
Assembly OSM is a New York City off-site manufacturing company founded in 2019 by SHoP Architects co-founders Bill and Chris Sharples to industrialise the construction of high-rise urban housing. The company calls its method "post-modular": rather than trucking finished volumetric boxes from a single factory, Assembly designs a kit-of-parts chassis and distributes fabrication across a network of specialist suppliers — an aerospace and automotive supply-chain model applied to buildings — then stacks the resulting units on site, claiming delivery of market-competitive high-rise residential architecture in roughly 60% of conventional schedule. Its buildings are all-electric and passive-design led, targeting 55-70% energy-efficiency improvement and 35% less embodied carbon today, net-zero operational carbon by 2027 and climate-positive buildings by 2040. Completed and in-progress work includes Prototype Alpha, 147 St. Felix Street and 247 East 117th Street in New York, plus an AOSM Canada operation. The company has raised more than $60 million, including a $38 million Series A in 2022, and draws engineering staff from SpaceX, Tesla and Boeing. Assembly runs a digital-twin engineering platform — a heavily scripted CATIA environment carrying each module from design through fabrication to installation — but that platform is an internal manufacturing tool, not a product: Assembly OSM sells buildings, and publishes no developer program, no public API, no SDK and no machine-readable API contract of any kind.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Assembly OSM the way a machine reads it — 1 machine-readable artifact, 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 — Assembly OSM scores 10.6/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Assembly OSM manufactures and stacks high-rise apartment buildings — its digital twin is a scripted CATIA environment used internally to drive its own fabrication line, not a product with an interface — so assemblyosm.com is an eleven-page Webflow marketing site where every spec path 404s, every /.well-known/* path returns "Invalid .well-known request", and the api./docs./developer./mcp. hosts that appear to resolve are a wildcard DNS record answering with the same Cloudflare 403 as a nonsense control subdomain.
This is an honest zero, not a gap in our research. Assembly OSM does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://www.assemblyosm.com/openapi.json→ HTTP 404https://www.assemblyosm.com/llms.txt→ HTTP 404https://www.assemblyosm.com/.well-known/agent-card.json→ HTTP 404https://www.assemblyosm.com/.well-known/security.txt→ HTTP 404https://api.assemblyosm.com/→ HTTP 403https://zzz-nonsense-control.assemblyosm.com/→ HTTP 403https://api.github.com/orgs/assemblyosm/repos→ HTTP 200https://status.assemblyosm.com/→ HTTP 200
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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Assembly OSM'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/assembly-osm/"
title="Assembly OSM on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/assembly-osm.svg"
alt="Assembly OSM Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/assembly-osm/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/assembly-osm/"
title="Assembly OSM on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/assembly-osm/card.svg"
alt="Assembly OSM 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 Assembly OSM
Each block below is one kind of artifact we hold for Assembly OSM. 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.
Security Posture 1
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 Assembly OSM — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
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 5
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/assembly-osm · machine-readable index on apis.io
This is an independent, third-party profile of Assembly OSM, 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.