Opkey
Opkey (Smart Software Testing Solutions, Inc.) is a US-headquartered Cloud Application Lifecycle Management and AI-powered test automation vendor for enterprise packaged applications. Its no-code platform ships pre-built automated tests and change-impact analysis for Oracle Cloud/EBS, Workday, Salesforce, SAP, Coupa, Veeva, UKG/Kronos and Microsoft Dynamics, alongside an agentic layer (Argus AI, Testing/Configuration/Training/Impact-Analysis/PMO agents, Release Advisor and Maestro). Opkey also operates pCloudy, the real-device mobile and browser testing cloud it acquired, which carries the company's public developer surface: a documented REST API for device booking, app upload/install, device interaction, performance capture, network simulation, Appium/XCTest orchestration and APK instrumentation, plus a published pCloudy MCP server that exposes device booking, app management and QPilot AI test authoring as tools to MCP clients. The core Opkey product help and user guides sit behind a customer login; the pCloudy documentation, API reference and release notes are public.
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 Opkey the way a machine reads it — 36 machine-readable artifacts across 16 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 — Opkey scores 51.8/100 (developing), with a separate agent-readiness read of 30/100 (agent aware). 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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Opkey'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/opkey/"
title="Opkey on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/opkey.svg"
alt="Opkey Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/opkey/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/opkey/"
title="Opkey on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/opkey/card.svg"
alt="Opkey 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 Opkey
Each block below is one kind of artifact we hold for Opkey. 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 16
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.
pCloudy MCP Server
The official pCloudy MCP server, published by pCloudy as the Python package pcloudy-mcp and run over stdio with uvx. It exposes 36 tools across four groups — device booking, bro...
Opkey Apk Instrumentation API
The Apk Instrumentation API from Opkey — 3 operation(s) for apk instrumentation.
Opkey Apk Instrumentation Apis API
The Apk Instrumentation Apis API from Opkey — 3 operation(s) for apk instrumentation apis.
Opkey App Center Api API
The App Center Api API from Opkey — 5 operation(s) for app center api.
Opkey App Control API
The App Control API from Opkey — 4 operation(s) for app control.
Opkey Appium Automation API
The Appium Automation API from Opkey — 11 operation(s) for appium automation.
Opkey Authentication API
The Authentication API from Opkey — 1 operation(s) for authentication.
Opkey Device Booking & Session API
The Device Booking & Session API from Opkey — 3 operation(s) for device booking & session.
Opkey Device Interaction API
The Device Interaction API from Opkey — 8 operation(s) for device interaction.
Opkey File Management API
The File Management API from Opkey — 2 operation(s) for file management.
Opkey Generic API
The Generic API from Opkey — 30 operation(s) for generic.
Opkey Network Simulation API
The Network Simulation API from Opkey — 5 operation(s) for network simulation.
Opkey Performance API
The Performance API from Opkey — 1 operation(s) for performance.
Opkey Resigning Apis API
The Resigning Apis API from Opkey — 3 operation(s) for resigning apis.
Opkey Session Media & Logs API
The Session Media & Logs API from Opkey — 5 operation(s) for session media & logs.
Opkey Xctest Automation API
The Xctest Automation API from Opkey — 6 operation(s) for xctest automation.
Scroll within the panel for all 16 ·
Open Collections 16
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).
API Collection
OPEN COLLECTIONpCloudy Device Cloud Apk Instrumentation API
OPEN COLLECTIONpCloudy Device Cloud Apk Instrumentation Apis API
OPEN COLLECTIONpCloudy Device Cloud App Center Api API
OPEN COLLECTIONpCloudy Device Cloud App Control API
OPEN COLLECTIONpCloudy Device Cloud Appium Automation API
OPEN COLLECTIONpCloudy Device Cloud Authentication API
OPEN COLLECTIONpCloudy Device Cloud Device Booking & Session API
OPEN COLLECTIONpCloudy Device Cloud Device Interaction API
OPEN COLLECTIONpCloudy Device Cloud File Management API
OPEN COLLECTIONpCloudy Device Cloud Generic API
OPEN COLLECTIONpCloudy Device Cloud Network Simulation API
OPEN COLLECTIONpCloudy Device Cloud Performance API
OPEN COLLECTIONpCloudy Device Cloud Resigning Apis API
OPEN COLLECTIONpCloudy Device Cloud Session Media & Logs API
OPEN COLLECTIONpCloudy Device Cloud Xctest Automation API
OPEN COLLECTIONScroll within the panel for all 16 ·
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.
opkey-pcloudy-mcp.yml
MCP SERVERSecurity 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 Opkey — 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 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/opkey · machine-readable index on apis.io
This is an independent, third-party profile of Opkey, 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.