Scan a build log for exposed credentials
Detect likely GitHub tokens, AWS keys, bearer credentials, JWTs, private-key blocks, database URLs, API keys, passwords, and secret assignments in a CI log. Return only types, counts, line numbers, and redacted snippets—never the detected values.
$0.002 USDC POST /v1/secret-scan
developer-tools · security · secrets · ci-cd
Use it for
- scan build log for secrets
- detect leaked CI credentials
- find tokens in logs
Example input
{
"log": "FAILED tests/test_math.py::test_total - AssertionError: assert 1 == 2",
"step_name": "pytest"
}Example output
{
"success": true,
"finding_count": 1,
"types": {
"bearer_token": 1
},
"findings": [
{
"line": 4,
"type": "bearer_token",
"redacted": "Authorization: Bearer [REDACTED]"
}
]
}Call it
Use an x402 v2 payment-aware client from the quickstart. An unpaid request safely returns the exact payment challenge before any work runs.