TeamCity
JetBrains TeamCity is a powerful continuous integration and deployment server that helps development teams build, test, and deploy software efficiently. TeamCity provides a comprehensive REST API for automating CI/CD workflows, managing projects, build configurations, agents, and infrastructure.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles TeamCity the way a machine reads it — 65 machine-readable artifacts across 17 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 — TeamCity scores 64.0/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). 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 TeamCity
Each block below is one kind of artifact we hold for TeamCity. 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 17
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.
TeamCity Agent Pools API
Manage agent pools
TeamCity Agents API
Manage build agents
TeamCity Audit API
Query audit log entries
TeamCity Build Configurations API
Manage build configurations (build types)
TeamCity Build Queue API
Manage the build queue
TeamCity Builds API
Trigger, query, and manage builds
TeamCity Changes API
Query VCS changes
TeamCity Cloud API
Manage cloud profiles and instances
TeamCity Investigations API
Manage build and test investigations
TeamCity Mutes API
Manage test mutes
TeamCity Problems API
Query build problems
TeamCity Projects API
Manage TeamCity projects
TeamCity Server API
Server information and configuration
TeamCity Tests API
Query test results
TeamCity User Groups API
Manage user groups
TeamCity Users API
Manage users and user groups
TeamCity VCS Roots API
Manage version control system roots
Scroll within the panel for all 17 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
TeamCity REST API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Teamcity Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Teamcity Finops
FINOPSFeatures 12
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Build Pipelines
Define multi-stage build pipelines with dependencies and parallel execution.
Build Chains
Create complex build chains with snapshot and artifact dependencies between configurations.
Branch Building
Automatically detect and build feature branches from VCS repositories.
Build Templates
Reusable build configuration templates for standardizing pipeline patterns.
Personal Builds
Run builds with local code changes before committing to the repository.
Cloud Agents
Dynamically provision build agents in the cloud for elastic scaling.
Kotlin DSL Configuration
Define build configurations as code using Kotlin DSL.
Test History and Flaky Tests
Track test history across builds and automatically detect flaky tests.
Investigation Management
Assign responsibility for failing builds and tests to team members.
Build Cache
Cache build dependencies and artifacts for faster subsequent builds.
Composite Builds
Aggregate results from multiple build configurations into a single view.
Audit Trail
Complete audit logging of all administrative actions and configuration changes.
Scroll within the panel for all 12 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Teamcity Rest Api Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
TeamCity API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
TeamCity REST API JSON Schema
JSON SCHEMASecurity 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 9
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Continuous Integration
Automatically build and test code on every commit or pull request.
Continuous Deployment
Deploy applications to staging and production environments automatically.
Multi-Platform Builds
Build and test across Linux, Windows, and macOS using diverse agent pools.
Monorepo CI
Manage CI/CD for monorepos with selective triggering based on changed paths.
Microservices Pipelines
Orchestrate build and deploy pipelines for microservices architectures.
Release Management
Manage release branches, versioning, and deployment gates.
Infrastructure as Code Testing
Validate Terraform, Kubernetes, and other IaC configurations in CI pipelines.
Mobile App CI/CD
Build, test, and distribute mobile applications for iOS and Android.
Compliance and Audit
Maintain audit trails and enforce build policies for regulatory compliance.
Scroll within the panel for all 9 ·
Integrations 16
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
GitHub
Pull request building, commit status publishing, and webhook triggers from GitHub.
GitLab
Integration with GitLab repositories for VCS operations and merge request builds.
Bitbucket
Bitbucket Cloud and Server integration for source code and pull request builds.
Docker
Build and push Docker images as part of CI/CD pipelines.
Kubernetes
Deploy to Kubernetes clusters and use Kubernetes pods as build agents.
AWS
AWS S3 artifact storage, EC2/ECS cloud agents, and CodeDeploy integration.
Azure
Azure cloud agents, Azure DevOps integration, and Azure deployment targets.
Jira
Link builds to Jira issues and track deployments.
Slack
Build notifications and status updates via Slack channels.
Terraform
Manage TeamCity infrastructure as code using the official Terraform provider.
HashiCorp Vault
Secure secrets management integration with HashiCorp Vault.
SAML SSO
Single sign-on authentication via SAML identity providers like Okta and OneLogin.
NuGet
NuGet package feed hosting and dependency resolution.
Maven
Maven build runner and artifact repository integration.
Gradle
Gradle build runner with build cache and configuration cache support.
Bazel
Bazel build system support via the TeamCity Bazel plugin.
Scroll within the panel for all 16 ·
Resources
Every other property we hold for TeamCity — 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
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/teamcity · machine-readable index on apis.io