Acadia
Acadia is a Connected Worker Platform designed for employee productivity, acquired by Epicor. It delivers digital work instructions, knowledge management, skills matrices, quizzing, process evaluations, and team communications to frontline workers across manufacturing, transportation, healthcare, and retail banking. Acadia integrates with SSO, ERP, HRIS, LMS, IoT, and credentialing systems to enable enterprise-grade workforce development at scale.
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 Acadia the way a machine reads it — 68 machine-readable artifacts across 5 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 — Acadia scores 51.5/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 Acadia
Each block below is one kind of artifact we hold for Acadia. 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 5
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.
Acadia Employees API
Manage employee profiles and training records
Acadia Quizzes API
Manage quizzes and assessments
Acadia Roles API
Manage job roles and training requirements
Acadia Skills API
Manage employee skills and skills matrices
Acadia Work Instructions API
Manage digital work instructions and task lists
Pricing 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.
Acadia Plans Pricing
PLANSRate 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.
Acadia 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.
Acadia 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.
Digital Work Instructions
Convert procedures to interactive task lists with videos, images, and dynamic content; assign via QR code, ERP integration, or manager distribution
Knowledge Management
Centralized document creation with automated translation, algorithmic search, and custom metadata filters
Skills Matrix
Track training and skill attainment, quantify individual and team performance, and identify capability gaps
Quizzing and Evaluations
Assess employee skill proficiency, measure comprehension, and perform objective skill evaluations during task execution
Team Communications
Auditable acknowledgements for process changes, group communications, and document change tracking
SSO Integration
Secure single sign-on via Active Directory and LDAP with role-based access control
ERP and HRIS Integration
Integration with ERP, HRIS, LMS, IoT, and credentialing systems for enterprise workforce management
SOC 2 Type II Certified
Enterprise-grade security with multi-layer encryption, intrusion prevention, and GDPR compliance
Career Path Visibility
Display advancement requirements and skill gap identification for employee career development
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.
Acadia Platform 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.
Acadia API Rules
SPECTRALAcadia API Rules
SPECTRALJSON Schema 11
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.
EmployeeList
JSON SCHEMAEmployee
JSON SCHEMAEmployeeSkillsMatrix
JSON SCHEMAQuizList
JSON SCHEMAQuiz
JSON SCHEMARoleList
JSON SCHEMARole
JSON SCHEMASkillRecord
JSON SCHEMAWorkInstructionList
JSON SCHEMAWorkInstruction
JSON SCHEMAWorkInstructionStep
JSON SCHEMAScroll within the panel for all 11 ·
JSON Structure 11
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.
Acadia Employee List Structure
JSON STRUCTUREAcadia Employee Skills Matrix Structure
JSON STRUCTUREAcadia Employee Structure
JSON STRUCTUREAcadia Quiz List Structure
JSON STRUCTUREAcadia Quiz Structure
JSON STRUCTUREAcadia Role List Structure
JSON STRUCTUREAcadia Role Structure
JSON STRUCTUREAcadia Skill Record Structure
JSON STRUCTUREAcadia Work Instruction List Structure
JSON STRUCTUREAcadia Work Instruction Step Structure
JSON STRUCTUREAcadia Work Instruction Structure
JSON STRUCTUREScroll within the panel for all 11 ·
Examples 11
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.
Acadia Employee Example
EXAMPLEAcadia Employee List Example
EXAMPLEAcadia Quiz Example
EXAMPLEAcadia Quiz List Example
EXAMPLEAcadia Role Example
EXAMPLEAcadia Role List Example
EXAMPLEAcadia Skill Record Example
EXAMPLEScroll within the panel for all 11 ·
Security 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.
Use Cases 6
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.
Manufacturing Workforce Onboarding
Use digital work instructions to onboard new manufacturing employees quickly and ensure procedure compliance
Compliance Training
Assign and track completion of compliance-critical training and policy acknowledgements with full auditability
Frontline Skill Gap Analysis
Use the skills matrix to identify capability gaps in frontline teams and prioritize training investments
Process Improvement Feedback
Capture structured employee feedback on task-specific procedures to improve standard work over time
ERP-Triggered Work Instructions
Automatically assign work instructions based on ERP work orders for synchronized production operations
Multi-Language Training Deployment
Deploy synchronized multi-language training content to global workforces without manual translation delays
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.
SAP
Integration with SAP ERP for work order-triggered digital work instruction assignment
Active Directory
Single sign-on via Microsoft Active Directory for enterprise identity management
LDAP
LDAP-based SSO for enterprise authentication systems
Learning Management Systems
Integration with third-party LMS platforms for training record synchronization
HRIS Systems
Integration with HR information systems for employee data synchronization
IoT Platforms
Integration with IoT systems for operational data correlation with training and task execution
Resources
Every other property we hold for Acadia — 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 2
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 2
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/acadia · machine-readable index on apis.io