Encrypt and verify text data with AES-256-GCM encryption via x402 micropayment for $0.02 per call.
What it does
The Cybercentry Quantum Cryptography Verification (CQCV) API is an x402-enabled endpoint that accepts text data and returns an encrypted record with a unique record ID and a decryption URL for later retrieval. The encryption uses AES-256-GCM, and each call costs $0.02 in USDC on the Base network.
The endpoint is accessed via POST to `/verify` with a `data` query parameter containing the text to encrypt. Upon successful payment and processing, the API returns a JSON object with a `record_id` (string) and a `decrypt_url` (string) that can be used to retrieve and decrypt the data later. The x402 payment challenge requires an exact payment of 20,000 base units of USDC (0.02 USD) to the specified wallet address on Base.
Documentation is minimal — the landing page provides a brief description and the docs/api/pricing routes all return 404. There is no OpenAPI spec, no detailed error documentation, and no information about rate limits, data retention policies, or the decryption retrieval process. The landing page mentions GET but the x402 challenge was captured on POST, so the actual HTTP method may vary.
Capabilities
Use cases
- —Encrypt sensitive text data before storing it elsewhere
- —Generate a shareable decryption URL for secure data exchange
- —Pay-per-use encryption for agent workflows that handle PII or secrets
- —Secure short text payloads with a unique record ID for later retrieval
Fit
Best for
- —Agents needing on-demand text encryption with no API key signup
- —Quick one-off encryption of small text payloads
- —x402-native workflows on the Base network
Not for
- —Large file or binary data encryption (only text via query param)
- —Use cases requiring detailed audit logs, SLAs, or compliance guarantees
- —Scenarios needing free or high-volume bulk encryption
Quick start
curl -X POST \
-H "X-PAYMENT: <x402_payment_header>" \
"https://x402-cybercentry-quantum-cryptography-verification.up.railway.app/verify?data=hello+world"Example
Request
{
"url": "https://x402-cybercentry-quantum-cryptography-verification.up.railway.app/verify?data=my+secret+text",
"method": "POST",
"headers": {
"X-PAYMENT": "<x402_payment_token>"
}
}Response
{
"record_id": "abc123-def456-ghi789",
"decrypt_url": "https://x402-cybercentry-quantum-cryptography-verification.up.railway.app/decrypt/abc123-def456-ghi789"
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a clear output schema and pricing, but documentation is extremely sparse — no OpenAPI spec, no detailed docs, no information on data retention or the decryption flow. The example response is inferred from the output schema since no actual successful response was captured. The landing page says GET but the probe succeeded on POST.
Warnings
- —No OpenAPI spec or detailed documentation available; /docs, /api, /pricing all return 404.
- —Landing page advertises GET /verify but the x402 challenge was captured on POST — actual supported method is unclear.
- —No information on data retention, decryption endpoint behavior, or rate limits.
- —The term 'quantum cryptography' appears to be marketing language; the actual encryption described is AES-256-GCM, a standard symmetric cipher.
- —Example response is inferred from outputSchema, not from an actual successful call.
Citations
- —Encryption uses AES-256-GCM and costs $0.02 per callhttps://x402-cybercentry-quantum-cryptography-verification.up.railway.app
- —The endpoint is live and returns a 402 x402 challenge on POST with USDC on Base network, maxAmountRequired 20000 (= $0.02)https://x402-cybercentry-quantum-cryptography-verification.up.railway.app/verify
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://x402-cybercentry-quantum-cryptography-verification.up.railway.app/verify
- —Landing page describes the service as GET /verify?data={data}https://x402-cybercentry-quantum-cryptography-verification.up.railway.app