x402basequality 0.72

Scan deployed smart contracts for vulnerabilities via Cybercentry for $0.02 per call.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://x402-cybercentry-solidity-code-verification.up.railway.app/verify

What it does

This x402-enabled endpoint lets AI agents and developers pay $0.02 (in USDC on Base) per request to scan a deployed, verified Solidity smart contract using the Cybercentry security analysis engine. The caller provides a chain identifier and contract address as query parameters, and the service returns a structured risk assessment including an overall risk rating, total vulnerability count, and a severity breakdown (High, Medium, Low, Informational).

Supported chains include Ethereum mainnet, Base, Polygon (poly), Arbitrum (arbi), Optimism, Avalanche (avax), BSC, Gnosis, zkEVM, and Blast. The endpoint accepts POST requests with an x402 payment header; the payment settles in USDC (contract 0x8335…2913) on the Base L2 network using the "exact" payment scheme. The maximum timeout for a scan is 300 seconds (5 minutes), reflecting that on-chain contract analysis can take non-trivial time.

The response includes a job_id for tracking, the chain scanned, an overall_risk string, a status field, the total vulnerabilities_count, and a severity_breakdown object. No OpenAPI spec or extended documentation is available beyond the landing page and the x402 challenge metadata, but the input/output schema embedded in the challenge is well-defined and sufficient for integration.

Capabilities

smart-contract-auditsolidity-vulnerability-scanmulti-chain-supportx402-paymentseverity-breakdownrisk-assessment

Use cases

  • —Automated pre-deployment or post-deployment security scanning of Solidity contracts
  • —Agent-driven portfolio risk assessment by scanning contracts before interacting with DeFi protocols
  • —Continuous monitoring of deployed contracts across multiple EVM chains for new vulnerabilities
  • —Integrating contract security checks into CI/CD pipelines for smart contract development

Fit

Best for

  • —AI agents that need programmatic, pay-per-use smart contract security analysis
  • —Developers wanting quick vulnerability scans across 10 EVM-compatible chains
  • —Automated workflows that need structured severity breakdowns for risk scoring

Not for

  • —Auditing non-Solidity or non-EVM contracts (e.g., Solana, Move-based chains)
  • —Full manual audit reports with remediation guidance
  • —Scanning unverified (closed-source) contracts where source code is not available on-chain

Quick start

curl -X POST "https://x402-cybercentry-solidity-code-verification.up.railway.app/verify?chain=base&contract_address=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913" \
  -H "X-PAYMENT: <x402_payment_header>" \
  -H "Content-Type: application/json"

Example

Request

{
  "url": "https://x402-cybercentry-solidity-code-verification.up.railway.app/verify?chain=base&contract_address=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "method": "POST",
  "headers": {
    "X-PAYMENT": "<x402_payment_header>",
    "Content-Type": "application/json"
  }
}

Response

{
  "chain": "base",
  "job_id": "abc123-def456",
  "status": "completed",
  "overall_risk": "Medium",
  "severity_breakdown": {
    "Low": 1,
    "High": 0,
    "Medium": 2,
    "Informational": 0
  },
  "vulnerabilities_count": 3
}

Endpoint

URLhttps://x402-cybercentry-solidity-code-verification.up.railway.app/verify
Transporthttp
Protocolx402
Pay to0xfEE13309251B632317ea2d475d6ABa7E7E0219e6
CurrencyUSD COIN

Quality

0.72/ 1.00

The endpoint is live (402 challenge captured), has a well-defined input/output schema embedded in the x402 challenge, clear pricing ($0.02 USDC on Base), and supports 10 chains. However, there is no OpenAPI spec, no extended documentation, and the example response is inferred from the output schema rather than observed. The landing page and challenge metadata are consistent and sufficient for integration.

Warnings

  • —No OpenAPI or extended API documentation available; /docs returns 404
  • —Example response is inferred from the outputSchema, not from an actual observed response
  • —Landing page says GET but the x402 challenge was captured via POST — callers should use POST with x402 payment header
  • —Contract verification status (whether source must be verified on-chain) is not explicitly documented

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 23:53:25Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/kWPhnA
Scan deployed smart contracts for vulnerabilities via Cybercentry for $0.02 per call. — Clawmart · Clawmart