AWS X-Ray
AWS X-Ray is a service that helps developers analyze and debug distributed applications by providing end-to-end tracing of requests as they travel through the application, identifying performance bottlenecks and errors. It is now part of Amazon CloudWatch Application Signals for unified observability.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles AWS X-Ray the way a machine reads it — 92 machine-readable artifacts across 9 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 — AWS X-Ray scores 65.8/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 AWS X-Ray
Each block below is one kind of artifact we hold for AWS X-Ray. 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 9
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.
AWS X-Ray Encryption API
Manage encryption configuration
AWS X-Ray Groups API
Manage trace groups
AWS X-Ray Insights API
Automated anomaly detection insights
AWS X-Ray Sampling API
Manage sampling rules
AWS X-Ray Service Graph API
Service map and statistics
AWS X-Ray TagResource API
The TagResource API from AWS X-Ray — 1 operation(s) for tagresource.
AWS X-Ray Tags API
The Tags API from AWS X-Ray — 1 operation(s) for tags.
AWS X-Ray Traces API
Upload and retrieve trace data
AWS X-Ray UntagResource API
The UntagResource API from AWS X-Ray — 1 operation(s) for untagresource.
Scroll within the panel for all 9 ·
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).
AWS X-Ray 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.
Aws X Ray 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.
Aws X Ray Finops
FINOPSFeatures 9
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.
End-to-End Tracing
Trace requests from client to backend across all services in your distributed application.
Service Map
Visualize service dependencies and real-time health indicators in an interactive map.
Trace Analytics
Filter, search, and analyze traces using filter expressions and groups.
Sampling Rules
Control trace collection rates with dynamic sampling rules to manage cost and volume.
Annotations and Metadata
Add indexed annotations and non-indexed metadata to traces for custom filtering and context.
Error Analysis
Identify and analyze errors, faults, and throttling across distributed services.
Latency Analysis
Identify performance bottlenecks with detailed latency histograms and percentile data.
CloudWatch Integration
Integrated with CloudWatch Application Signals for unified observability and alerting.
SDK Support
Instrument applications with X-Ray SDKs for Java, Python, Go, Node.js, Ruby, and .NET.
Scroll within the panel for all 9 ·
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.
Aws X Ray Context
JSON-LDSpectral Rules 2
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.
AWS X-Ray API Rules
SPECTRALAWS X-Ray API Rules
SPECTRALJSON Schema 19
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.
BatchGetTracesResult
JSON SCHEMAEdgeStatistics
JSON SCHEMAEncryptionConfig
JSON SCHEMAGetServiceGraphResult
JSON SCHEMAGetTraceSummariesResult
JSON SCHEMAGroup
JSON SCHEMAGroupSummary
JSON SCHEMAHistogramEntry
JSON SCHEMAInsight
JSON SCHEMAInsightSummary
JSON SCHEMASamplingRule
JSON SCHEMASamplingRuleRecord
JSON SCHEMAService
JSON SCHEMAServiceId
JSON SCHEMAServiceStatistics
JSON SCHEMATag
JSON SCHEMATimeSeriesServiceStatistics
JSON SCHEMATrace
JSON SCHEMATraceSummary
JSON SCHEMAScroll within the panel for all 19 ·
JSON Structure 19
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
X Ray Batchgettracesresult Structure
JSON STRUCTUREX Ray Edgestatistics Structure
JSON STRUCTUREX Ray Encryptionconfig Structure
JSON STRUCTUREX Ray Getservicegraphresult Structure
JSON STRUCTUREX Ray Gettracesummariesresult Structure
JSON STRUCTUREX Ray Group Structure
JSON STRUCTUREX Ray Groupsummary Structure
JSON STRUCTUREX Ray Histogramentry Structure
JSON STRUCTUREX Ray Insight Structure
JSON STRUCTUREX Ray Insightsummary Structure
JSON STRUCTUREX Ray Samplingrule Structure
JSON STRUCTUREX Ray Samplingrulerecord Structure
JSON STRUCTUREX Ray Service Structure
JSON STRUCTUREX Ray Serviceid Structure
JSON STRUCTUREX Ray Servicestatistics Structure
JSON STRUCTUREX Ray Tag Structure
JSON STRUCTUREX Ray Timeseriesservicestatistics Structure
JSON STRUCTUREX Ray Trace Structure
JSON STRUCTUREX Ray Tracesummary Structure
JSON STRUCTUREScroll within the panel for all 19 ·
Examples 19
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
X Ray Edgestatistics Example
EXAMPLEX Ray Group Example
EXAMPLEX Ray Groupsummary Example
EXAMPLEX Ray Histogramentry Example
EXAMPLEX Ray Insight Example
EXAMPLEX Ray Insightsummary Example
EXAMPLEX Ray Samplingrule Example
EXAMPLEX Ray Service Example
EXAMPLEX Ray Serviceid Example
EXAMPLEX Ray Tag Example
EXAMPLEX Ray Trace Example
EXAMPLEX Ray Tracesummary Example
EXAMPLEScroll within the panel for all 19 ·
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.
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.
Performance Optimization
Identify and resolve latency bottlenecks in distributed microservices applications.
Error Debugging
Trace errors and exceptions to their root cause across service boundaries.
Dependency Analysis
Understand service dependencies and the impact of downstream failures.
SLA Monitoring
Monitor request latency and error rates against service level agreements.
Microservices Visibility
Gain observability into complex microservices architectures and their interactions.
Resources
Every other property we hold for AWS X-Ray — 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
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Operate 3
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/aws-x-ray · machine-readable index on apis.io