Inference Cost Audit

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

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.

What this means

If the user benchmarks the service, they may create an account and use a provider API key.

Why it was flagged

The skill documents optional account registration and authenticated API use with GPU-Bridge. This is expected for testing a provider, but it means the user may provide identity and credential material.

Skill content
curl -X POST https://api.gpubridge.io/account/register ... -d '{"email":"your@email.com"...}' ... -H "Authorization: Bearer YOUR_API_KEY"
Recommendation

Use a dedicated account or limited-scope API key where possible, and avoid sharing credentials beyond the provider needed for the benchmark.

What this means

Prompts, documents, images, audio, or other benchmark inputs could be sent to GPU-Bridge if the user follows the testing workflow.

Why it was flagged

The benchmarking workflow sends input data to an external provider endpoint. The data flow is disclosed and purpose-aligned, but the artifacts do not describe privacy, retention, or filtering guidance for sensitive benchmark data.

Skill content
Test with real data, not marketing claims. ... curl -X POST https://api.gpubridge.io/run ... -d '{"service":"llm-4090","input":{"prompt":"Hello world","max_tokens":50}}'
Recommendation

Benchmark with non-sensitive samples unless the provider’s privacy and data-retention terms are acceptable for the data being tested.

What this means

Users choosing this path could authorize per-request payments through a crypto wallet.

Why it was flagged

The skill describes an optional payment path using a wallet transaction reference. It does not request a private key and appears purpose-aligned, but it involves payment-related identity and spend authority.

Skill content
For agents with crypto wallets — pay per-request with USDC on Base L2 (no account needed): X-Payment: base64({"txHash":"0x...","from":"0xYourWallet"})
Recommendation

Only use wallet payment if you understand the cost and have reviewed the transaction; never provide private keys or seed phrases.