Developer Secret Scan
by API Acre in Developer tools
Detect likely leaked API keys, tokens, private-key headers, JWTs, and credential assignments in caller-supplied source or configuration text. Return type, line, fingerprint, and a fully redacted preview with no network access or code execution.
https://apiacre.com/v1/developer/secret-scan- Price
- $0.005
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 197 ms
- 384 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://apiacre.com/v1/developer/secret-scan
Each call costs $0.005 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://apiacre.com/v1/developer/secret-scan
content-type: application/json
{
"content": "API_TOKEN=example-not-a-real-secret"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | Yes |
Example response
The provider's example. We can't check it without paying.
{
"data": {
"clean": false,
"findingCount": 1,
"findings": [
{
"fingerprint": "360b25f697c5fca0",
"line": 1,
"preview": "[REDACTED]",
"type": "generic_assignment"
}
]
},
"meta": {
"cached": false,
"duration_ms": 42,
"next_actions": [],
"sources": [],
"warnings": []
},
"request_id": "018f1f54-7f38-7ba2-8dc3-5f90272d9f1a",
"service": "developer.secret-scan",
"version": "1"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.005.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://apiacre.com/v1/developer/secret-scan' \
-H 'content-type: application/json' \
--data-raw '{"content":"API_TOKEN=example-not-a-real-secret"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://apiacre.com/v1/developer/secret-scan' \
-H 'content-type: application/json' \
--data-raw '{"content":"API_TOKEN=example-not-a-real-secret"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapiacre.com%2Fv1%2Fdeveloper%2Fsecret-scan&method=POST
const res = await pay("https://apiacre.com/v1/developer/secret-scan", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"content": "API_TOKEN=example-not-a-real-secret"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://apiacre.com/v1/developer/secret-scan",
json={
"content": "API_TOKEN=example-not-a-real-secret",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 271 ms | $0.005 |
| 7 h ago | Passed | 402 | 82 ms | $0.005 |
| 11 h ago | Passed | 402 | 263 ms | $0.005 |
| 15 h ago | Passed | 402 | 192 ms | $0.005 |
| 19 h ago | Passed | 402 | 920 ms | $0.005 |
Show 10 older checks
| 24 h ago | Passed | 402 | 336 ms | $0.005 |
| 28 h ago | Passed | 402 | 197 ms | $0.005 |
| 32 h ago | Passed | 402 | 181 ms | $0.005 |
| 36 h ago | Passed | 402 | 190 ms | $0.005 |
| 41 h ago | Passed | 402 | 88 ms | $0.005 |
| 45 h ago | Passed | 402 | 236 ms | $0.005 |
| 2 days ago | Passed | 402 | 72 ms | $0.005 |
| 2 days ago | Passed | 402 | 212 ms | $0.005 |
| 2 days ago | Passed | 402 | 100 ms | $0.005 |
| 3 days ago | Passed | 402 | 229 ms | $0.005 |