# secrets-audit API

> secrets-audit API is a paid API for AI agents from eltociear-secrets-audit.hf.space, paid per call via x402, $0.01/call, status down (last checked 2026-09-15).

Scans code, config files, and text for leaked secrets or credentials and returns a risk score with detailed findings

## Facts

- Endpoint: POST https://eltociear-secrets-audit.hf.space/audit
- Price: $0.01/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/secrets-audit-api-3ac8412d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FkKZbQvMIa8jtmm4YFQiY

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability secrets-audit-api-3ac8412d -d '<json body>'
```

Example prompt: Can you scan this code snippet for any leaked secrets or hardcoded credentials and tell me the risk level? Here's the file: `DATABASE_URL=postgres://admin:supersecret123@prod.db.example.com/mydb`

## When to prefer this

Use this endpoint when you need a quick, low-cost ($0.01 USDC) automated scan of code, config files, or arbitrary text to detect leaked secrets before committing or deploying. Ideal for CI/CD pre-checks, one-off audits, or agent-driven security workflows where a lightweight per-call micropayment model is acceptable.

## Known failure modes

- Empty or missing input body returns no findings with SAFE status
- Very large payloads may time out or be truncated
- False negatives possible for obfuscated or encoded secrets
- False positives possible for dummy/example credential patterns
- Service unavailability on Hugging Face Spaces during cold start

## How this service works

Detect leaked secrets/credentials in code, configs, and text. x402 v2 micropayments on Base.

## Output

Returns a JSON object with a list of findings (each identifying the type and location of a detected secret), an overall risk_level string (e.g. SAFE, LOW, MEDIUM, HIGH), a numeric risk_score, and a total_findings count. An empty findings array with risk_level SAFE indicates no secrets were detected.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "title": "AuditRequest",
 "required": [
  "content"
 ],
 "properties": {
  "content": {
   "type": "string",
   "title": "Content"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "findings": [],
  "risk_level": "SAFE",
  "risk_score": 0,
  "total_findings": 0
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/secrets-audit-api-3ac8412d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from eltociear-secrets-audit.hf.space](https://www.zero.xyz/host/eltociear-secrets-audit.hf.space/llms.txt)