Tower
Tower is a Python-native data flow orchestrator and fully-managed data backend for pipelines, agents, and data applications, pairing serverless (or self-hosted) Python compute with an open Apache Iceberg-based lakehouse that is compatible with Snowflake, Spark, and DuckDB. Teams deploy versioned apps with a Towerfile, run dbt Core and dlt ingestion pipelines, schedule and observe runs, and power data agents grounded in fresh company data. Founded by engineers from Snowflake, Databricks, Google Cloud Dataflow, and Puppet, and backed by Speedinvest, Tower ships a REST API, a CLI, a Python SDK, an official MCP server, and provider-published agent skills.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Tower the way a machine reads it — 32 machine-readable artifacts across 27 APIs, 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 — Tower scores 56.6/100 (developing), with a separate agent-readiness read of 61/100 (agent native). 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 Tower
Each block below is one kind of artifact we hold for Tower. 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.
APIs 27
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Tower Accounts API
The Accounts API from Tower — 2 operation(s) for accounts.
Tower Alerts API
The Alerts API from Tower — 5 operation(s) for alerts.
Tower Api Keys API
The Api Keys API from Tower — 1 operation(s) for api keys.
Tower Apps API
The Apps API from Tower — 12 operation(s) for apps.
Tower Catalogs API
The Catalogs API from Tower — 4 operation(s) for catalogs.
Tower Environments API
The Environments API from Tower — 2 operation(s) for environments.
Tower Feature Flags API
The Feature Flags API from Tower — 1 operation(s) for feature flags.
Tower Guests API
The Guests API from Tower — 3 operation(s) for guests.
Tower Login API
The Login API from Tower — 3 operation(s) for login.
Tower Organizations API
The Organizations API from Tower — 1 operation(s) for organizations.
Tower Plan API
The Plan API from Tower — 1 operation(s) for plan.
Tower Runners API
The Runners API from Tower — 2 operation(s) for runners.
Tower Runs API
The Runs API from Tower — 1 operation(s) for runs.
Tower Sandbox API
The Sandbox API from Tower — 1 operation(s) for sandbox.
Tower Schedules API
The Schedules API from Tower — 4 operation(s) for schedules.
Tower Secrets API
The Secrets API from Tower — 5 operation(s) for secrets.
Tower Service Accounts API
The Service Accounts API from Tower — 3 operation(s) for service accounts.
Tower Session API
The Session API from Tower — 2 operation(s) for session.
Tower Shouldertaps API
The Shouldertaps API from Tower — 1 operation(s) for shouldertaps.
Tower Stats API
The Stats API from Tower — 2 operation(s) for stats.
Tower Storage API
The Storage API from Tower — 1 operation(s) for storage.
Tower Team Invites API
The Team Invites API from Tower — 1 operation(s) for team invites.
Tower Teams API
The Teams API from Tower — 6 operation(s) for teams.
Tower Usage API
The Usage API from Tower — 2 operation(s) for usage.
Tower User API
The User API from Tower — 3 operation(s) for user.
Tower Webhooks API
The Webhooks API from Tower — 3 operation(s) for webhooks.
Tower Whoami API
The Whoami API from Tower — 1 operation(s) for whoami.
Scroll within the panel for all 27 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
tower-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Tower Webhooks
ASYNCAPISecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Tower — 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 5
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/tower · machine-readable index on apis.io