> For the complete documentation index, see [llms.txt](https://cybercentry.gitbook.io/cybercentry/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cybercentry.gitbook.io/cybercentry/readme.md).

# Welcome

Check the deployer before you launch their token. ERC-8376 is the standard we wrote for it, and ten paid verifications are how you act on it.

A launchpad that lists a honeypot does not lose money. It loses the users who bought it, and the next hundred deployers who would rather launch somewhere that has not been in that headline. The deployer is pseudonymous and finished; the venue is named, still trading, and holds the only record of who bought what.

That asymmetry is what [ERC-8376](/cybercentry/erc-8376/erc-8376.md) is built on, and it is what this whole site is arranged around. The standard says the venue is the right place to intervene: consult detection before you launch, disclose what it found, and at full conformance be able to return money that has not yet left.

Everything else here serves that. Ten verification services, a dollar each, paid in USDC on Base over [x402](https://x402.org), are how a venue or a buyer acts on what detection says.

{% hint style="warning" %}
ERC-8376 is an **open pull request**, not a merged standard, and no score has yet been published on chain. Where there is no live report, the standard requires a venue to present that as unknown and forbids presenting it as safe. We hold ourselves to the same rule here.
{% endhint %}

## Start where you sit

| You are                                         | Start here                                                      |
| ----------------------------------------------- | --------------------------------------------------------------- |
| A launchpad, bonding curve or sale contract     | [For launchpads](/cybercentry/erc-8376/for-launchpads.md)       |
| An agent or developer paying per call           | [Quickstart](/cybercentry/start-here/quickstart.md)             |
| An agent that wants tools rather than endpoints | [Verification MCP](/cybercentry/start-here/verification-mcp.md) |
| Buying in volume                                | [Subscriptions](/cybercentry/start-here/subscriptions.md)       |
| A $CENTRY holder or spender                     | [How rewards work](/cybercentry/rewards/how-rewards-work.md)    |

## The standard, in three parts

**Detection.** Eleven deployer abuse patterns scored from a twelve-signal vector into a number from 0 to 100, published as a bonded report a detector loses money for getting wrong. Every signal describes an action the deployer took. Price decline is excluded by rule, because falling is not fraud.

**Escrow.** The venue holds sale proceeds and releases them on a schedule capped at 90 days, so the money is still reachable while abuse typically happens.

**Remediation.** A bonded claim and adjudication process that, on an upheld claim, refunds buyers pro rata and draws any shortfall from a bond posted before launch.

Only the last level holds money, and only that level may say so. "Verified" and "protected" imply restitution, and the standard forbids a lower level from implying one.

## What you can verify today

|                                                                                             |                                                              |
| ------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| [Wallet](/cybercentry/services/services/wallet-verification.md)                             | Sanctions screening and risk history across 33 EVM chains    |
| [Base token](/cybercentry/services/services/base-token-verification.md)                     | Honeypots, freeze-and-seize, fake B20s, ticker impersonation |
| [Ethereum token](/cybercentry/services/services/ethereum-token-verification.md)             | Static analysis of a deployed contract's verified source     |
| [Solidity code](/cybercentry/services/services/solidity-code-verification.md)               | Source you paste in, before you deploy it                    |
| [Web application](/cybercentry/services/services/web-application-verification.md)           | An OWASP-based scan of a site or dApp frontend               |
| [AI agent](/cybercentry/services/services/openclaw-ai-agent-verification.md)                | Agent verification under ERC-8126                            |
| [Media content](/cybercentry/services/services/media-content-verification.md)               | Provenance and authenticity of a file                        |
| [Private data](/cybercentry/services/services/private-data-verification.md)                 | A zero-knowledge proof over data you keep                    |
| [Quantum cryptography](/cybercentry/services/services/quantum-cryptography-verification.md) | Post-quantum encryption of your data                         |
| [Cyber security consultant](/cybercentry/services/services/cyber-security-consultant.md)    | An advisory answer, generated rather than measured           |

Full list with prices and timings: [Services](/cybercentry/services/services.md).

## Three surfaces

**centry.cybercentry.co.uk** is the machine-facing one, and the only settlement from which rewards are calculated. **app.cybercentry.co.uk** is the same capability for people who want an interface on Base App. **erc8126scan.ai** is the public scanner for ERC-8126, the AI Agent Verification standard we co-authored, and usually the first point of contact because it needs no wallet at all.

## What we do not claim

A clean report is not a guarantee. It says which checks ran and what they found, and where a check could not run it says so rather than reporting nothing found. Absence of evidence is not evidence of safety, and a report that blurs the two is worse than no report. Every payment settles on Base where you can read it back without asking us, which for a security company is the only sort of claim worth making.