Build with clarity.
This is a read-only introduction to the CentQuery testnet gateway. It intentionally does not guide users to sign a payment or connect wallets while the custom-domain resource migration is pending.
Agent-first entry points
An AI agent can start from the machine-readable resources below without navigating the website or opening a wallet. These are discovery artifacts published with the static site; they do not change the protected API itself.
/catalog.json— synthetic testnet inventory, example response, safety constraints and verified host status./openapi.json— OpenAPI 3.1 contract for the two safe, unsigned GET inspection routes./llms.txt— concise agent-readable site index./docs/index.md— direct Markdown guide and agent-safety instructions.
Autonomous payment is not available in this preview. Static discovery metadata is never a substitute for validating live payment requirements and obtaining explicit buyer authorization.
API hosts
| HOST | PURPOSE |
|---|---|
api.centquery.dev | New custom API hostname, reachable over HTTPS. The new hostname's payment challenge still advertises the legacy resource URL until the staged dual-host deployment completes. |
centquery-gateway-lab.tomashcv-centquery-lab.workers.dev | Legacy protected gateway. It must remain active for existing clients and previously settled purchase recoveries. |
1. Check gateway configuration
This GET requires no credentials and does not create payment authorizations. A 200 response signals that required gateway configuration and rate-limiter bindings are present. It does not prove that the upstream Supabase service is healthy.
curl -i https://api.centquery.dev/health
{
"service": "centquery-gateway",
"mode": "testnet",
"status": "configured"
}
2. Inspect the x402 payment challenge
An unsigned GET of the protected demo route should return HTTP 402, with a base64-encoded x402 v2 payment challenge in the PAYMENT-REQUIRED header. This example does not sign, settle, or purchase anything.
curl -i \
https://api.centquery.dev/functions/v1/paid-demo/report
| FIELD | CURRENT LAB VALUE |
|---|---|
| Protocol version | 2 |
| Network | eip155:84532 (Base Sepolia) |
| Amount | 10000 atomic units = 0.01 test-USDC at 6 decimals |
| Resource URL | Currently the original workers.dev payment URL on both hosts. The branch-only update is designed to announce the matching hostname separately. |
Never replace the challenge resource URL client-side, blindly follow redirects for protected requests, or assume that a 402 response proves a payment. The server must verify and settle an authorized payment before revealing protected data.
3. Understand the intended flow
- The client discovers a resource and evaluates its terms and schema.
- An unsigned request receives HTTP 402 and payment requirements.
- A compatible buyer explicitly validates the network, amount, asset, recipient and canonical resource URL before signing.
- The gateway protects the origin; verified settlement and private ledger reconciliation control access.
- Previously settled purchases may use an EIP-191 buyer proof to recover the original report without an extra payment.
The publicly accessible lab has verified historical testnet recoveries. This documentation is not an invitation to run new paid transactions, and no signing instructions or credentials are published here.
Current limits
The protected gateway currently exposes only GET /health, GET /functions/v1/paid-demo/report and POST /functions/v1/paid-demo/report/recover. The recovery route requires a legitimate buyer proof and is not a public data endpoint. The separate synthetic free-sample API is not routed through this payment gateway hostname.
Real datasets, redistribution rights, commercial pricing, usage guarantees, consumer accounts and a general-purpose public catalog are not launched. The API is a testnet prototype for verifying safe machine-to-machine delivery.
Back to homepage