Empowerly
Empowerly is an education-technology company founded in 2017 by Hanmei Wu and Changxiao Xie that delivers personalized college admissions and career counseling to high-school students. The platform pairs students with a network of more than 100 counselors — including former college admission officers — and layers on data-driven tooling: a proprietary admissions calculator built from thousands of past student outcomes, college-list building, essay editing and review, interview preparation, and startup and research internship placement programs. Students and families work through the Empowerly web portal at app.empowerly.com; counseling packages are sold through an enrollment conversation rather than published price tiers. Empowerly publishes no public developer program, API documentation, or SDKs; the only publicly callable surface on its own domains is the Atlassian-hosted status page API at status.empowerly.com.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Empowerly the way a machine reads it — 8 machine-readable artifacts across 1 API, 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 — Empowerly scores 41.9/100 (thin), with a separate agent-readiness read of 37/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.
Why this profile is thin
Empowerly runs a live production API host (api.empowerly.com/health returns 200 "Empowerly Production API is up and running") purely as the private backend for its student web portal, and publishes nothing around it — no developer portal, no docs, no spec, no SDKs, no GitHub org; developer.empowerly.com and docs.empowerly.com do not even resolve.
This is an honest zero, not a gap in our research. Empowerly does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://api.empowerly.com/health→ HTTP 200https://api.empowerly.com/openapi.json→ HTTP 404https://empowerly.com/developers→ HTTP 404https://empowerly.com/api→ HTTP 404https://empowerly.com/llms.txt→ HTTP 403https://api.github.com/orgs/empowerly→ HTTP 404https://status.empowerly.com/api/v2/summary.json→ HTTP 200
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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Empowerly's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/empowerly/"
title="Empowerly on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/empowerly.svg"
alt="Empowerly Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/empowerly/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/empowerly/"
title="Empowerly on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/empowerly/card.svg"
alt="Empowerly Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Empowerly
Each block below is one kind of artifact we hold for Empowerly. 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 1
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.
Empowerly Status API
Read-only, unauthenticated JSON status API served from Empowerly's own status subdomain by Atlassian Statuspage. Exposes the overall page status indicator, the component roster ...
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).
Empowerly Status 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.
Empowerly Rate Limits
RATE LIMITSSecurity 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.
Resources
Every other property we hold for Empowerly — 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
Agent Surfaces 3
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 6
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/empowerly · machine-readable index on apis.io
This is an independent, third-party profile of Empowerly, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.