Walter
Walter is a San Francisco-based Y Combinator (Spring 2026) startup building an AI employee for the manufacturing back office. Founded in 2026 by Nikolas Keller (CEO) and Lukas Postulka (CTO), Walter logs into the enterprise systems a company already runs on — SAP, Oracle NetSuite, Microsoft Dynamics 365, Teams, Outlook and Gmail — the way a new hire would, and takes over manual paperwork: reading sales orders and purchase orders from emails and PDFs, capturing and validating the data, cross-checking it against the ERP, ordering from suppliers and catching pricing errors before they ship. It uses a purpose-built document-understanding model (rather than legacy template OCR) that supports 270+ languages and reaches 90%+ accuracy after minimal training, cutting an order that used to take 15 minutes down to about one. Walter requires no integration project and no rip-and-replace, operating the same screens the team already uses. It is an early-stage company with no public API, developer program, SDKs or documentation; this profile captures its public identity and security posture for the API Evangelist network.
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 Walter the way a machine reads it — 2 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 — Walter scores 14.1/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 Walter
Each block below is one kind of artifact we hold for Walter. 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 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.
Resources
Every other property we hold for Walter — 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
Access & Security 3
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/walter · machine-readable index on apis.io