Npcink Cloud Addon
Npcink Cloud Addon connects a local WordPress site to npcink-cloud.
It stores the Cloud Base URL and Cloud API Key, parses Cloud-issued keys, signs runtime requests, probes health, reads Cloud entitlement summaries, and can upload metadata-only plugin behavior events after explicit administrator opt-in.
It does not execute WordPress writes, approve proposals, own billing truth, or manage prompts, routers, presets, workflow/task queues, scheduler truth, or workflow engines. Its observability buffer is only a bounded delivery buffer for monitoring metadata and is not Core audit, proposal, execution, billing, or workflow truth.
For media derivative jobs, local host code may pass the read-only
npcink-abilities-toolkit/build-media-derivative-cloud-request ability output and a short TTL
source artifact descriptor to the addon for signed Cloud dispatch. The addon
requires verified Cloud settings, rejects credential-bearing ability payloads,
and returns proposal-ready data with final_write_owner=local_wordpress_host.
Final review, recording, replacement, rollback, and WordPress writes remain in
the local host/Core approval path.
For plugin monitoring, the addon may upload operational metadata such as plugin slug/version, event kind, status, timing, error code, route, proposal id, ability id, correlation id, and counters. It must not upload prompts, generated content, article body content, media bytes, raw request or response payloads, provider credentials, Cloud API secrets, passwords, cookies, nonces, Authorization headers, database names, table names, or filesystem paths.
External Services
This plugin connects to the Npcink Cloud service configured by the site administrator through the Cloud Base URL setting.
The plugin contacts the configured Cloud service only after an administrator enters a Cloud Base URL and Cloud API Key, saves the settings, verifies the connection, or a local Npcink component explicitly uses the Cloud runtime client.
Requests may include the configured site identifier, key identifier, request timestamp, nonce, trace identifier, idempotency key, HMAC signature headers, runtime request payloads supplied by local Npcink components, metadata-only monitoring events when enabled, and read-only requests for health, run status, run result, usage statistics, entitlement summaries, and observability summaries. The stored Cloud API Key secret is used server-side for request signing and is not printed in wp-admin.
For host-supplied media derivative runtime jobs, requests may also include a short TTL source artifact descriptor and derivative request parameters from the local read-only ability output. Cloud credentials and signed headers are added by the addon transport and are not copied into the ability payload.
The configured Cloud service is responsible for its own privacy policy, terms of service, data retention, and account/key issuance. Because the Cloud Base URL is administrator-configured, site administrators should only connect this plugin to a Cloud service whose terms of service, privacy policy, data retention policy, and account/key issuance process they have reviewed.
Npcink Cloud service information:
- Terms of Service: https://cloud.npc.ink/terms/en/terms.html
- Privacy Policy: https://cloud.npc.ink/terms/en/privacy.html
- Data Retention: https://cloud.npc.ink/terms/en/data-retention.html