Praxis AI (Vortexify)
Praxis AI is a Y Combinator (Fall 2024) company that now operates as Vortexify (vortexify.ai). Vortexify is an AI-native platform that generates operational software directly from a company's data: teams connect data sources through 20+ prebuilt connectors (PostgreSQL, MySQL, SQL Server, MongoDB, BigQuery, Redshift, Snowflake, NetSuite, Oracle, S3, Azure Blob, Google Sheets/Drive, SharePoint and more), describe requirements in plain English, and AI agents plan, code, test and deploy backend logic plus custom frontends with no infrastructure to manage. The platform emphasizes building complete apps on operational data rather than just dashboards, with built-in scheduling, serverless compute execution, role-based access control, audit logs, sandboxed environments, token-based authentication, and SOC 2 Type II compliance. Praxis AI was founded by Aditya Tewari (ex-Palantir) and Ransika Liyanage (ex-Tesla, GM, Deloitte), originally focused on manufacturing-specific AI agents for predicting and preventing machine failures. This profile was surfaced as a portfolio company of Y Combinator. Vortexify does not currently publish a public developer API, SDK, or OpenAPI specification.
Praxis AI (Vortexify) is profiled on the APIs.io network. Tagged areas include Company, Artificial Intelligence, No-Code, Data Integration, and Application Development.
Praxis AI (Vortexify)’s developer surface includes documentation, pricing, signup flow, support, and 5 more developer resources.
Kin Score
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API