ALICE Technologies
ALICE Technologies is a Menlo Park, California construction technology company that builds an AI-driven generative scheduling and construction optioneering platform. The product simulates millions of possible construction sequences for a project — varying crews, equipment, methods, and constraints — to find optimal schedules, accelerate timelines, recover delayed projects, and de-risk capital project delivery. ALICE's suite includes ALICE Optimize (generative scheduling from imported Primavera P6 or Microsoft Project schedules), ALICE Plan (a 2D visual planning canvas overlaid on drawings), ALICE Model (BIM-driven schedule generation from 3D models), and the Schedule Insights Agent (an LLM-powered conversational interface for analysing and recommending schedule changes, including automated DCMA 14-point schedule quality scoring). The platform is sold as SaaS to general contractors, owners and developers, and consultants working on industrial (data centres, energy, semiconductors), infrastructure (rail, highway, tunnels), and commercial projects, with reported impacts including up to 17% reduction in project duration and 14% labor cost savings. ALICE was founded in 2015 by René Morkos (Stanford PhD) and is backed by Merus Capital, Foundamental, Future Ventures, Lightspeed, Blackhorn Ventures, and Brick and Mortar; in 2026 it announced a formal alliance with McKinsey to deploy generative scheduling on capital projects. ALICE integrates by importing from Primavera P6, Primavera Cloud, Microsoft Project, and BIM/drawing formats, but does not publish a public developer API, SDK, or open-source repository — integration is delivered via the product's import/export surface and customer-success engagements.
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 ALICE Technologies the way a machine reads it — 3 machine-readable artifacts, 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 — ALICE Technologies scores 10.3/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.
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 ALICE Technologies
Each block below is one kind of artifact we hold for ALICE Technologies. 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 3
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 ALICE Technologies — 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 1
Portal, sign-up, and the first successful call
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
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/alice-tech · machine-readable index on apis.io