x402basequality 0.50

Zero-Knowledge Proof verification for arbitrary text data via x402 micropayment on Base.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

Cybercentry Private Data Verification (CPDV) is an x402-enabled API that accepts arbitrary text input and returns a Zero-Knowledge Proof (ZKP) verification result. When you submit text data, the service analyzes it for integrity and authenticity, then generates a cryptographic ZKP. The response includes a `proof_id` and a `proof_url` that can be used to independently verify the proof, enabling trustless, privacy-preserving validation suitable for Web3 workflows such as login attestations or identity claims.

The endpoint is hosted on Railway and settles payments on the Base network using USDC (contract 0x8335…2913). Each call costs 20,000 base units of USDC, which equals $0.02 (6-decimal token). Payment is made via the x402 protocol's `X-PAYMENT` header with the "exact" scheme. The x402 challenge specifies a maximum timeout of 300 seconds and pays to address 0xfEE133…19e6.

The API accepts a POST request with a `data` query parameter containing the text to verify. No formal OpenAPI spec or extended documentation is published beyond the landing page description and the outputSchema embedded in the x402 challenge. The outputSchema indicates the response is a JSON object with `proof_id` (string) and `proof_url` (string) fields. Note that the landing page advertises the endpoint as GET while the x402 challenge was captured via POST; both methods may work, but POST is confirmed live.

Capabilities

zero-knowledge-prooftext-verificationdata-integrityzkp-generationx402-paymentbase-networkusdc-settlementprivacy-preserving-validation

Use cases

  • Generating a ZKP attestation for a user login event to prove it occurred without revealing credentials
  • Verifying the integrity of a text-based identity claim in a Web3 dApp
  • Producing a cryptographic proof-of-action for audit trails without exposing underlying data
  • Embedding privacy-preserving verification into automated agent workflows that settle via x402

Fit

Best for

  • Web3 developers needing lightweight ZKP generation for text data
  • Agent pipelines requiring pay-per-call privacy-preserving verification
  • Applications that need trustless proof URLs for third-party audit

Not for

  • Verifying non-text data such as images, files, or binary blobs
  • High-throughput batch verification (no documented batch endpoint)
  • Use cases requiring detailed ZKP circuit customization or advanced proof parameters

Quick start

curl -X POST \
  'https://x402-cybercentry-private-data-verification.up.railway.app/verify?data=hello+world' \
  -H 'X-PAYMENT: <x402_payment_token>'

Example

Request

{
  "url": "https://x402-cybercentry-private-data-verification.up.railway.app/verify?data=user+logged+in+at+2025-01-15T12:00:00Z",
  "method": "POST",
  "headers": {
    "X-PAYMENT": "<x402_payment_token>"
  }
}

Response

{
  "proof_id": "abc123def456",
  "proof_url": "https://cybercentry.example.com/proofs/abc123def456"
}

Endpoint

Transporthttp
Protocolx402
Pay to0xfEE13309251B632317ea2d475d6ABa7E7E0219e6
CurrencyUSD COIN

Quality

0.50/ 1.00

The endpoint is live (402 challenge captured) with a clear outputSchema and pricing, but there is no OpenAPI spec, no extended documentation, and the example response is inferred from the schema rather than observed. The landing page and x402 challenge disagree on HTTP method (GET vs POST). The proof_url domain is unknown.

Warnings

  • No formal OpenAPI or Swagger documentation is published.
  • Landing page says GET /verify but the x402 challenge was captured via POST — actual supported methods are unclear.
  • The example response proof_url domain is fabricated for illustration; the real domain is not documented.
  • No information on rate limits, SLA, or uptime guarantees.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 00:48:31Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access