Contract Audit
by ManyLives Onchain in Onchain & crypto
Security pre-check for any Base network contract before your agent interacts with it (vault, router, token, bridge): built-in powers in its code (mint, pause, blacklist, upgrade, withdraw, self-destruct, delegatecall), proxy and who controls it (a single wallet or a multisig contract), whether the source is publicly verified, with red flags, a risk level and a plain-language verdict. Facts, not financial advice.
https://api.manylives.me/paid/contract/audit- Price
- $0.02
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 559 ms
- 730 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
How to call it
GET https://api.manylives.me/paid/contract/audit
Each call costs $0.02 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.
GET https://api.manylives.me/paid/contract/audit?address=0x4200000000000000000000000000000000000006Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | Yes | 0x... contract on the Base network (required) |
Example response
The provider's example. We can't check it without paying.
{
"address": "0x4200000000000000000000000000000000000006",
"checked_at": "2026-10-10T12:00:00Z",
"code_bytes": 4766,
"flags": [],
"has_selfdestruct": false,
"is_contract": true,
"notice": "Automated checks of public on-chain facts. Not a full audit and not financial advice.",
"owner": null,
"owner_is_contract": null,
"powers": [],
"proxy": {
"admin": null,
"implementation": null,
"type": null
},
"risk": "low",
"source_verified": true,
"uses_delegatecall": false,
"verdict": "…"
}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.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.manylives.me/paid/contract/audit?address=0x4200000000000000000000000000000000000006'
# 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 - 'https://api.manylives.me/paid/contract/audit?address=0x4200000000000000000000000000000000000006' \
| 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.manylives.me%2Fpaid%2Fcontract%2Faudit
const res = await pay("https://api.manylives.me/paid/contract/audit?address=0x4200000000000000000000000000000000000006");
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://api.manylives.me/paid/contract/audit?address=0x4200000000000000000000000000000000000006")
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 | 567 ms | $0.02 |
| 6 h ago | Passed | 402 | 546 ms | $0.02 |
| 11 h ago | Passed | 402 | 529 ms | $0.02 |
| 15 h ago | Passed | 402 | 559 ms | $0.02 |
| 19 h ago | Passed | 402 | 642 ms | $0.02 |
Show 10 older checks
| 23 h ago | Passed | 402 | 730 ms | $0.02 |
| 27 h ago | Passed | 402 | 620 ms | $0.02 |
| 31 h ago | Passed | 402 | 941 ms | $0.02 |
| 35 h ago | Passed | 402 | 524 ms | $0.02 |
| 39 h ago | Passed | 402 | 695 ms | $0.02 |
| 43 h ago | Passed | 402 | 502 ms | $0.02 |
| 47 h ago | Passed | 402 | 560 ms | $0.02 |
| 2 days ago | Passed | 402 | 512 ms | $0.02 |
| 2 days ago | Passed | 402 | 521 ms | $0.02 |
| 2 days ago | Passed | 402 | 633 ms | $0.02 |