# Solidity Static Scanner

> Solidity Static Scanner is a paid API for AI agents from chargers-borders-cedar-fig.trycloudflare.com, paid per call via x402, price unknown, status down (last checked 2026-09-15).

Performs static analysis on Solidity smart contract code to detect security vulnerabilities and code quality issues

## Facts

- Endpoint: POST https://chargers-borders-cedar-fig.trycloudflare.com/tools/solidity-static-scan
- Price: price unknown
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/solidity-static-scanner-74aa1650
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iGLUiqexnUI3r9v_Ln0gX

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 solidity-static-scanner-74aa1650 -d '<json body>'
```

Example prompt: Can you run a static security scan on this Solidity smart contract code and tell me if there are any vulnerabilities like reentrancy, integer overflow, or unsafe delegatecall patterns?

## When to prefer this

Use this endpoint when you need automated static security analysis specifically for Solidity smart contracts, particularly before deployment or code review. Prefer this over manual review for rapid vulnerability detection covering common patterns like reentrancy, integer overflow, and access control issues.

## Known failure modes

- Invalid or malformed Solidity code returns a parse error
- Empty or missing input body returns a 400 bad request
- Unsupported Solidity version may cause parsing failures
- Cloudflare tunnel downtime causes connection errors
- Very large contracts may timeout or be rejected

## How this service works

opentools utility endpoint

## Output

A static analysis report identifying security vulnerabilities, code quality issues, and potentially dangerous patterns found in the submitted Solidity smart contract code, likely including severity levels and affected code locations.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/solidity-static-scanner-74aa1650/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chargers-borders-cedar-fig.trycloudflare.com](https://www.zero.xyz/host/chargers-borders-cedar-fig.trycloudflare.com/llms.txt)