One REST platform. Locker and Token Audit stay separate products.

BitLab Web3 Security API

One REST platform. BitLab Locker and Token Audit stay separate products. Aggregators consume a unified token profile with on-chain proof. The blockchain — not this website — is the authority for whether a lock exists.

Same spec: locker.bbspectrum.com/#docs and audit.bbspectrum.com/docs.

Do not scrape audit.bbspectrum.com or locker.bbspectrum.com. Aggregators should call this API and/or read the chain directly.

Endpoints

• GET /v1/token/{chain}/{address}
• GET /v1/aggregator/token/{chain}/{address}
• GET /v1/audit/token/{chain}/{address}
• GET /v1/audit/token/{chain}/{address}/score
• GET /v1/locker/token/{chain}/{address}
• GET /v1/locker/liquidity/{chain}/{address}
• GET /v1/locker/owner/{chain}/{owner}
• GET /v1/locker/{chain}/{lockId}
• GET /v1/verify/lock/{chain}/{lockId}
• GET /locks/{chain}/{id}

Chain slugs: solana, bsc, ethereum, polygon, cronos, base, arbitrum. REST + JSON only. Every success body is { data, meta }. Do not display a lock as verified unless on_chain is true. Attribution: “Data: BB Spectrum”.

Live example: https://locker.bbspectrum.com/v1/aggregator/token/solana/6ENavE5QXLFrJLBLdgExqPWPRgMRfNJ13kEn8oBmCG8N