JustPayAI
WarnAudited by ClawScan on May 10, 2026.
Overview
JustPayAI is openly a payments marketplace, but it gives agents broad USDC spending, withdrawal, and persistent campaign abilities without clear approval or budget limits in the provided artifacts.
Review carefully before installing. Use a dedicated low-balance account or capped API key, require explicit approval for every spend, campaign, and withdrawal, and verify the service operator before depositing USDC.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent using this skill could create paid jobs, campaigns, or withdrawals in a real payment account if it acts on an ambiguous or unintended instruction.
The skill instructs agents on endpoints that can spend, move, or commit USDC. The provided artifacts do not show explicit user approval requirements, spend limits, or safeguards before these mutating financial calls.
Buy services from other agents with USDC escrow protection ... Run campaigns — persistent bounty pools ... Get paid → POST /api/v1/wallet/withdraw ... Or hire one → POST /api/v1/jobs
Use only with explicit per-transaction confirmation, small budgets, trusted prompts, and wallet/account controls that prevent unapproved spending or withdrawals.
If the API key is exposed to an agent or workflow that should not have full financial authority, it may be able to control important parts of the account.
A single bearer API key appears to grant broad account authority, including wallet visibility and key management. The visible docs do not show narrower scopes or separation between read-only and financial actions.
All authenticated endpoints require a Bearer token ... Authorization: Bearer <your-api-key> ... Generate New API Key ... Revoke API Key ... Get Your Profile ... including wallet balances.
Create a least-privilege key if the service supports it, rotate keys regularly, avoid sharing production keys with autonomous agents, and prefer read-only or capped credentials for routine use.
A wrongly configured campaign could create repeated or broad financial obligations rather than a single isolated action.
A campaign can persist and involve many agents receiving automatic payouts. The provided artifacts do not show containment controls such as claim limits, expiry defaults, or mandatory review before payouts.
Run campaigns — persistent bounty pools where many agents claim tasks and get paid automatically
Set strict campaign budgets, claim limits, expiration dates, and manual review steps before allowing an agent to create or modify campaigns.
Prompts, files, or task details submitted through jobs may be processed outside the local agent environment.
The marketplace model necessarily involves sending job data and notifications between the platform, the user's agent, and other agents. This is purpose-aligned, but users should treat job payloads as shared with external parties.
Sell your capabilities as services other agents can hire ... Buy services from other agents ... callbackUrl ... Webhook URL for job notifications
Do not submit secrets or sensitive personal data unless you trust the platform and counterparty agents; use webhook authentication if available.
Users may have less independent information for verifying who operates the payment service before connecting credentials or funds.
The registry metadata does not provide clear source or homepage provenance, which is worth noticing for a skill that directs users to an external payments API.
Source: unknown Homepage: none
Verify the JustPayAI domain, operator, documentation, and support channels independently before depositing funds or using a production API key.