# 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.03/call, status down (last checked 2026-09-15).

Scans a URL for leaked secrets, credentials, and sensitive data in code, configs, or text files, returning findings and a risk assessment.

## Facts

- Endpoint: POST https://eltociear-secrets-audit.hf.space/audit/url
- Price: $0.03/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-a51346e3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3VDR8TbJSUqTJM-92uTNV

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-a51346e3 -d '<json body>'
```

Example prompt: Can you scan https://raw.githubusercontent.com/myorg/myrepo/main/config.env for any leaked secrets or exposed credentials and tell me the risk level?

## When to prefer this

Use this endpoint when you need to quickly check whether a publicly accessible URL (such as a raw GitHub file, a public config, or a deployment artifact) contains exposed secrets, API keys, or credentials. Ideal for automated security checks in CI/CD pipelines or pre-deployment audits.

## Known failure modes

- Inaccessible or non-existent URL returns an error or empty findings
- Non-text or binary file content may not be parseable
- Rate limiting or payment failure via x402 micropayment returns 402
- False negatives on obfuscated or encoded secrets
- Large files may time out or be truncated

## How this service works

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

## Output

A JSON object containing the scanned URL, an array of findings (each describing a detected secret or credential), a risk_level string (e.g. SAFE, LOW, MEDIUM, HIGH), a numeric risk_score, and a total_findings count.

## 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": {
  "url": "https://example.com/config.env",
  "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-a51346e3/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)