Hosting

2 operations. Call each with POST https://app.chirply.io/api/v1/actions/<name> and a bearer token; the response is { "data": { "action", "summary", "result" } }. A read badge means the operation changes nothing; write requires the credential’s write scope.

Check DigitalOcean connection

hosting.digitalocean_statusread

Checks whether this account has authorized a DigitalOcean team and, when connected, verifies the live account without returning OAuth credentials.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/hosting.digitalocean_status \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Test with your API key

Over MCP the same operation is the tool hosting_digitalocean_status at https://app.chirply.io/api/mcp, same bearer token, same input.

Disconnect DigitalOcean

hosting.disconnect_digitaloceanwriteconfirmadmin only

Revokes the stored DigitalOcean OAuth token and removes the account connection. Refuses while any WordPress server still exists so live sites are not stranded.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

No parameters — POST an empty body.

Example

curl -X POST https://app.chirply.io/api/v1/actions/hosting.disconnect_digitalocean \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Test with your API key

Over MCP the same operation is the tool hosting_disconnect_digitalocean at https://app.chirply.io/api/mcp, same bearer token, same input.