Stella Connect (Medallia Agent Connect)
Stella Connect, built by StellaService and acquired by Medallia in 2020, is now Medallia Agent Connect — a customer service team platform that pairs real-time customer feedback with agent coaching, quality assurance (QA), and recognition for contact center front-line teams. The product still runs on stellaconnect.net, and its Agent Connect API at api.stellaconnect.net exposes a Requests API for triggering feedback and service recovery surveys from any CRM or helpdesk, a Data Return API for pulling feedback, coaching sessions, QA reviews, audits, and calibrations, and a User Management API for employee lifecycle operations, secured with API keys and HMAC-signed JWTs.
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 Stella Connect (Medallia Agent Connect) the way a machine reads it — 11 machine-readable artifacts across 6 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 — Stella Connect (Medallia Agent Connect) scores 52.5/100 (developing), with a separate agent-readiness read of 76/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.
How we profile Stella Connect (Medallia Agent Connect)
Each block below is one kind of artifact we hold for Stella Connect (Medallia Agent Connect). 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 6
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.
Stella Connect (Medallia Agent Connect) Coaching API
The Coaching API from Stella Connect (Medallia Agent Connect) — 1 operation(s) for coaching.
Stella Connect (Medallia Agent Connect) Data API
The Data API from Stella Connect (Medallia Agent Connect) — 1 operation(s) for data.
Stella Connect (Medallia Agent Connect) Employees API
The Employees API from Stella Connect (Medallia Agent Connect) — 5 operation(s) for employees.
Stella Connect (Medallia Agent Connect) Qa API
The Qa API from Stella Connect (Medallia Agent Connect) — 3 operation(s) for qa.
Stella Connect (Medallia Agent Connect) Recoveries API
The Recoveries API from Stella Connect (Medallia Agent Connect) — 1 operation(s) for recoveries.
Stella Connect (Medallia Agent Connect) Requests API
The Requests API from Stella Connect (Medallia Agent Connect) — 1 operation(s) for requests.
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.
stellaconnect-mcp.yml
MCP SERVERRate 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.
Stellaconnect Rate Limits
RATE LIMITSSecurity 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.
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.
Resources
Every other property we hold for Stella Connect (Medallia Agent Connect) — 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 2
Reference material describing how the API behaves
Agent Surfaces 6
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/stellaconnect · machine-readable index on apis.io