WP Engine
WP Engine is a WordPress digital experience platform offering managed WordPress hosting with a REST API for programmatically managing sites, environments (installs), domains, SSH keys, SSL certificates, backups, and cache operations. The API uses Basic Authentication with credentials generated from the WP Engine User Portal.
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 WP Engine the way a machine reads it — 137 machine-readable artifacts across 17 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 — WP Engine scores 49.4/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 WP Engine
Each block below is one kind of artifact we hold for WP Engine. 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 17
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.
WP Engine Account API
The Account API from WP Engine — 3 operation(s) for account.
WP Engine Account User API
The Account User API from WP Engine — 2 operation(s) for account user.
WP Engine Archive API
The Archive API from WP Engine — 1 operation(s) for archive.
WP Engine Backup API
The Backup API from WP Engine — 3 operation(s) for backup.
WP Engine Cache API
The Cache API from WP Engine — 1 operation(s) for cache.
WP Engine Certificates API
The Certificates API from WP Engine — 3 operation(s) for certificates.
WP Engine Domain API
The Domain API from WP Engine — 6 operation(s) for domain.
WP Engine Install API
The Install API from WP Engine — 3 operation(s) for install.
WP Engine Offload Settings API
The Offload Settings API from WP Engine — 2 operation(s) for offload settings.
WP Engine Site API
The Site API from WP Engine — 2 operation(s) for site.
WP Engine Site Reports API
The Site Reports API from WP Engine — 1 operation(s) for site reports.
WP Engine Site Transfer API
The Site Transfer API from WP Engine — 3 operation(s) for site transfer.
WP Engine SSH Key API
The SSH Key API from WP Engine — 2 operation(s) for ssh key.
WP Engine Status API
The Status API from WP Engine — 1 operation(s) for status.
WP Engine Swagger API
The Swagger API from WP Engine — 1 operation(s) for swagger.
WP Engine Usage API
The Usage API from WP Engine — 6 operation(s) for usage.
WP Engine User API
The User API from WP Engine — 1 operation(s) for user.
Scroll within the panel for all 17 ·
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.
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.
Wpengine 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.
Wpengine Finops
FINOPSSpectral Rules 1
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.
WP Engine API Rules
SPECTRALJSON Schema 52
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.
Account
JSON SCHEMAAccountLimits
JSON SCHEMAAccountUsageInsights
JSON SCHEMAAccountUsageMetricsResponse
JSON SCHEMAAccountUser
JSON SCHEMAArchive
JSON SCHEMAAuthenticationErrorResponse
JSON SCHEMABackup
JSON SCHEMABadGatewayOperation
JSON SCHEMABadRequestErrorResponse
JSON SCHEMACertificate
JSON SCHEMACertificateOrder
JSON SCHEMAConflictErrorResponse
JSON SCHEMADailyUsageMetrics
JSON SCHEMADailyUsageMetricsTrafficMetricsSource
JSON SCHEMADomain
JSON SCHEMADomainCertificate
JSON SCHEMADomainOrRedirect
JSON SCHEMADomainReport
JSON SCHEMADomainStatus
JSON SCHEMADomainStatusReport
JSON SCHEMADomainVerification
JSON SCHEMAEnvironmentMetrics
JSON SCHEMAEnvironmentTypeBreakdown
JSON SCHEMAForbiddenErrorResponse
JSON SCHEMAInstallation
JSON SCHEMAInstallDailyUsageMetricsSeries
JSON SCHEMAInstallSSLCertificatesResponse
JSON SCHEMAInternalServerErrorResponse
JSON SCHEMALargeFSConfig
JSON SCHEMALargeFSValidationFile
JSON SCHEMALatestMetricValue
JSON SCHEMANextPage
JSON SCHEMANotFoundErrorResponse
JSON SCHEMAPreviousPage
JSON SCHEMAResourceError
JSON SCHEMAResultsCount
JSON SCHEMAServiceUnavailableOperation
JSON SCHEMASite
JSON SCHEMASiteTransfer
JSON SCHEMASiteTypeBreakdown
JSON SCHEMASshKey
JSON SCHEMAStatus
JSON SCHEMATemplate
JSON SCHEMAThirdPartySuccessfulImportResponse
JSON SCHEMATooManyRequestsOperation
JSON SCHEMAUnprocessableEntityErrorResponse
JSON SCHEMAUsageErrorResponse
JSON SCHEMAUsageMetricBreakdown
JSON SCHEMAUsageMetricsRollup
JSON SCHEMAUsageRollup
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 52 ·
Examples 60
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.
Cancelsitetransfer
EXAMPLECheckstatus
EXAMPLECopyinstall
EXAMPLECreateaccountuser
EXAMPLECreatebackup
EXAMPLECreatebulkdomains
EXAMPLECreatedomain
EXAMPLECreatedomaincertificateorder
EXAMPLECreateinstall
EXAMPLECreatesite
EXAMPLECreatesitetransfer
EXAMPLECreatesshkey
EXAMPLEDeleteaccountuser
EXAMPLEDeletedomain
EXAMPLEDeleteinstall
EXAMPLEDeletesite
EXAMPLEDeletesshkey
EXAMPLEGetaccount
EXAMPLEGetaccountusageinsights
EXAMPLEGetaccountusagemetrics
EXAMPLEGetaccountusagesummary
EXAMPLEGetaccountuser
EXAMPLEGetaccountslimits
EXAMPLEGetcurrentuser
EXAMPLEGetdomain
EXAMPLEGetdomaincertificate
EXAMPLEGetdomainreportstatus
EXAMPLEGetinstall
EXAMPLEGetinstallcertificates
EXAMPLEGetinstallusagemetrics
EXAMPLEGetlargefsvalidationfile
EXAMPLEGetoffloadsettings
EXAMPLEGetsite
EXAMPLEGetsitetransfer
EXAMPLEListaccountsitetransfers
EXAMPLEListaccountusers
EXAMPLEListaccounts
EXAMPLEListarchives
EXAMPLEListbackups
EXAMPLEListdomains
EXAMPLEListinstalls
EXAMPLEListsitereporttemplates
EXAMPLEListsitetransfers
EXAMPLEListsites
EXAMPLEListsshkeys
EXAMPLEPatchoffloadsettings
EXAMPLEPurgecache
EXAMPLERefreshenvironmentdiskusage
EXAMPLERestorebackup
EXAMPLEShowbackup
EXAMPLEStatus
EXAMPLESwagger
EXAMPLEUpdateaccountuser
EXAMPLEUpdatedomain
EXAMPLEUpdateinstall
EXAMPLEUpdateoffloadsettings
EXAMPLEUpdatesite
EXAMPLEVerifydomaintxtrecord
EXAMPLEScroll within the panel for all 60 ·
Security Posture 3
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 WP Engine — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
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 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/wpengine · machine-readable index on apis.io