Perplexity Computer Payments | Make payments with Perplexity Computer

The skill's functionality (creating checkouts, wallets, signing x402 payments, encrypted-card checkout) is coherent with a payment service and the single required env var (CREDITCLAW_API_KEY). However the registry name/description (Perplexity/Perplexity Computer) doesn't clearly match internal metadata and file names (creditclaw/creditclaw.com), which could indicate repackaging or a naming mismatch that should be clarified.

Runtime instructions explicitly tell the agent to retrieve one-time decryption keys and perform AES-256-GCM decryption of card details in-memory, accept encrypted card payloads via webhooks/messages, and complete merchant checkouts using decrypted PAN/CVV data. Handling raw card data is highly sensitive (PCI-level data) and increases risk — even though the docs insist on ephemeral in-memory use, the agent will be asked to process full card data which may be inappropriate for many agent runtimes or environments.

Instruction-only skill with no install spec and no binaries — lowest install risk. All referenced URLs point to creditclaw.com (no obscure download hosts).

Only a single credential (CREDITCLAW_API_KEY) is required, which is proportionate to a payment API. That API key is highly sensitive because it authorizes spending; the docs repeatedly warn not to leak it. Verify the API key provider and that you trust the service before granting it to any agent.

Skill is not always-on and does not request special persistent platform privileges. It documents ephemeral operations (one-time keys, single-use tokens) and does not ask to modify other skills or system-wide settings.