ProxyGate Status

Use when checking ProxyGate status — balance, usage, listings, tunnel health, earnings, seller profile, or job status. Make sure to use this skill whenever s...

Security Scan

The skill is internally consistent for checking ProxyGate status: it simply instructs use of the local proxygate CLI and SDK, but it implicitly relies on local config/keypair files that are not declared in the registry metadata.

Purpose & Capability

Name/description match the instructions: all commands and SDK calls are about balance, usage, listings, jobs, and related status. However, the metadata lists no required config paths or credentials while the docs and SDK examples reference a config file (~/.proxygate/config.json) and a keypair path (~/.proxygate/keypair.json), which the CLI uses for authentication — this is proportionate to the purpose but a minor metadata omission.

Instruction Scope

SKILL.md only instructs running the proxygate CLI and using the official SDK for status queries and troubleshooting. It does not instruct reading unrelated system files or sending data to unexpected external endpoints beyond the documented gateway (https://gateway.proxygate.ai).

Install Mechanism

Instruction-only skill with no install spec. It requires the proxygate binary to be present (declared in metadata), which is appropriate for a CLI-based status skill and avoids arbitrary downloads.

Credentials

No environment variables or primary credentials are declared, which is reasonable for a read-only status skill. But the documentation and command reference show the CLI uses a local keypair and config file for authentication; those file-access requirements are not declared in requires.configPaths. Users should be aware the CLI will access local keypair/config files when invoked.

Persistence & Privilege

The skill does not request permanent presence (always: false) and does not modify other skills or system-wide settings. Autonomous invocation (default) is normal for skills and not by itself a concern here.

Assessment

This skill appears to do exactly what it says: run the proxygate CLI or SDK to get status information. Before installing, ensure you trust the proxygate binary on your system (it will be executed) and be aware that invoking the CLI will read your ProxyGate config and keypair (e.g., ~/.proxygate/config.json and ~/.proxygate/keypair.json) to authenticate. If you do not already have the proxygate CLI installed, inspect its source or official release channel. Limit agent/file access if you are uncomfortable allowing reads of your keypair file, and verify the gateway URL in use (defaults to https://gateway.proxygate.ai).

Quick status checks for buyers and sellers.

Buyer status

proxygate balance                              # USDC balance (total, pending, available, cooldown)
proxygate usage                                # recent request history
proxygate usage -s openai -l 10                # filtered by service, last 10
proxygate usage --from 2026-03-01 --json       # date range, machine-readable
proxygate settlements -r buyer                 # cost breakdown (total requests, cost, fees, net)
proxygate settlements -s anthropic --from 2026-03-01  # filtered

Seller status

proxygate listings list                        # active listings (ID, service, status, RPM, price)
proxygate listings list --table                # human-readable table
proxygate listings docs <id>                   # view docs for a listing
proxygate settlements -r seller                # earnings (total requests, earnings, fees, net payout)
proxygate settlements --from 2026-03-01 --to 2026-03-14
proxygate balance                              # earned balance

Job status

proxygate jobs list --status claimed           # jobs you've claimed
proxygate jobs get <job-id>                    # full job details + submission status

SDK

import { ProxyGateClient } from '@proxygate/sdk';

const client = await ProxyGateClient.create({
  keypairPath: '~/.proxygate/keypair.json',
});

const { balance, available, pending_settlement } = await client.balance();
const usage = await client.usage({ service: 'openai', limit: 10 });
const settlements = await client.settlements({ role: 'seller', from: '2026-03-01' });
const { listings } = await client.listings.list();
const profile = await client.sellerProfile('wallet-address');

Troubleshooting

Symptom	Check
Balance 0	Deposit: proxygate deposit -a <amount> — see pg-buy
Proxy returns 503	Listing paused or seller tunnel down
"Unauthorized"	Run proxygate init to reconfigure — see pg-setup
Tunnel disconnects	Check proxygate dev logs, verify local port is open
Gateway unreachable	Verify URL: https://gateway.proxygate.ai

Related skills

Need	Skill
First-time setup	pg-setup
Buy API access	pg-buy
Sell API capacity	pg-sell
Job marketplace	pg-jobs
Check status	This skill
Update CLI/SDK	pg-update