Koobz
Koobz is a Ventura, California additive-manufacturing company rebuilding the footwear supply chain around on-demand 3D printing. Its "gigafactory" prints circular-ready, mono-material foamed-TPU shoes to order, so brands carry zero inventory and face no minimum order quantities: a consumer buys on the brand's own storefront, the order and personalization specs sync to the Koobz factory, the shoe is printed in Ventura and dropshipped direct to the customer in days. The company markets 10x faster concept-to-market cycles (4-6 weeks, no tooling), custom cushioning and foot-scanning personalization, and a KoobzWeave toolpath-as-textile upper pattern engine. Its mono-material architecture is positioned for Extended Producer Responsibility regimes such as California SB 707, since a single-polymer shoe yields premium TPU on take-back rather than mixed waste. Koobz has raised $7.2M and is backed by Uncork Capital. It describes its factory as API-driven and its order intake as an API sync from brand storefronts, but as of this profile it publishes no public developer portal, API documentation, or machine-readable API definition; integration appears to run through its partner ("Partner With Us") channel.
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 Koobz 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 — Koobz scores 11.8/100 (minimal), with a separate agent-readiness read of 4/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.
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 Koobz
Each block below is one kind of artifact we hold for Koobz. 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 Koobz — 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 2
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/koobz · machine-readable index on apis.io