Atlassian Compass
Atlassian Compass is a developer experience platform that helps engineering teams understand, manage, and improve the health of their software components and services. It provides a centralized catalog of software components with scorecards, metrics, dependency tracking, and event ingestion to improve developer productivity and software quality. Compass exposes a GraphQL API for querying and mutating component data and a REST Operations API for integrations.
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 Atlassian Compass the way a machine reads it — 34 machine-readable artifacts across 4 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 — Atlassian Compass scores 58.0/100 (developing), 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 Atlassian Compass
Each block below is one kind of artifact we hold for Atlassian Compass. 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 4
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.
Atlassian Compass GraphQL API
The Compass GraphQL API enables programmatic management of software components, scorecards, metrics, relationships, custom fields, and event ingestion within the Compass develop...
Atlassian Compass REST API
The Compass REST API v1 provides operations for component management, scorecard configuration, and webhook registration via standard HTTP REST conventions with OAuth 2.0 authent...
Atlassian Compass Events API
Ingest events into a Compass event source
Atlassian Compass Metrics API
Ingest metric values
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).
Atlassian Compass REST API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Atlassian Compass GraphQL API
The Compass GraphQL API enables programmatic management of software components, scorecards, metrics, relationships, custom fields, and event ingestion within the Compass develop...
GRAPHQLPricing 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.
Atlassian Compass 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.
Atlassian Compass Finops
FINOPSFeatures 6
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.
Component Catalog
Central catalog of all software components with metadata, ownership, and lifecycle tracking across teams.
Scorecards
Configurable scorecards that evaluate components against engineering standards and best practices to measure health.
Event Ingestion
Ingest build, deployment, incident, and vulnerability events from CI/CD pipelines and monitoring tools via webhooks and REST.
Dependency Tracking
Track relationships and dependencies between software components to understand blast radius and system topology.
Custom Fields
Extend component metadata with custom text, number, boolean, and user fields to capture team-specific data.
Forge Integration
Build custom Compass apps using the Atlassian Forge platform with the GraphQL toolkit for deep platform integration.
Security Posture 4
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.
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 5
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.
Software Catalog Management
Register and track all microservices, libraries, and software components with ownership and lifecycle metadata.
Engineering Health Monitoring
Create scorecards to measure and improve engineering standards like on-call coverage, documentation, and security posture.
DORA Metrics Tracking
Ingest deployment and incident events to track DORA metrics including deployment frequency and change failure rate.
Dependency Mapping
Map dependencies between services to identify coupling, blast radius, and architectural debt.
Developer Portal Integration
Integrate Compass with internal developer portals and CI/CD pipelines for automated component registration and event tracking.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Jira
Native integration with Jira for linking components to project tracking and incident management workflows.
Bitbucket
Connect Bitbucket repositories to Compass components for automated code health and deployment event tracking.
GitHub
Integrate GitHub repositories and GitHub Actions CI/CD pipelines with Compass component events.
PagerDuty
Ingest PagerDuty incident events into Compass for on-call and incident tracking scorecard criteria.
Datadog
Connect Datadog monitoring data and deployment events to Compass component metrics.
Terraform
Manage Compass resources via the Atlassian Operations Terraform provider for infrastructure-as-code workflows.
Solutions 2
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Developer Experience Platform
Provide engineering teams with a centralized platform to understand, manage, and improve the health of their software systems.
Platform Engineering
Enable platform engineering teams to enforce standards, track compliance, and improve developer productivity at scale.
Resources
Every other property we hold for Atlassian Compass — 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 3
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 1
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
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/atlassian-compass · machine-readable index on apis.io