# CentQuery — technical preview for AI agents

Updated: 2026-11-20. **Synthetic-only x402 v2 Base Sepolia testnet. Not a live commercial data API.**

Start with the JSON [machine-readable catalog](https://centquery.dev/catalog.json) and the [OpenAPI 3.1 specification](https://centquery.dev/openapi.json). Both are published at the public *website* hostname once that website is deployed, rather than on the protected payment gateway.

## Inspection without payment

```bash
curl -i https://api.centquery.dev/health
curl -i https://api.centquery.dev/functions/v1/paid-demo/report
```

The health check responds with a gateway configuration-readiness JSON object; it does not test Supabase. The **unsigned** report request should return HTTP 402 with base64-encoded `PAYMENT-REQUIRED` x402 v2 metadata. No payment or authorization is created by these two commands.

Current expected lab challenge: Base Sepolia `eip155:84532`, amount `10000` atomic units (`0.01 test-USDC`). These numbers are a dated snapshot and **must never replace checking the live challenge**.

## Host migration status

The old host is `https://centquery-gateway-lab.tomashcv-centquery-lab.workers.dev`. It remains in service for existing buyers and EIP-191 recovery.

The new host is `https://api.centquery.dev`, but its live unsigned payment challenge still advertises the old host's canonical resource URL as of 2026-11-20. Host-specific payment challenge code is staged in a separate protected PR; it has **not** been deployed. **Do not initiate signed purchases against the new hostname yet.**

## Supported functionality

- `GET /health`: anonymous configuration-readiness check, no payment.
- `GET /functions/v1/paid-demo/report`: anonymous HTTP 402 challenge inspection; synthetic report only after separately verified and settled authorization.
- `POST /functions/v1/paid-demo/report/recover`: privileged recovery of a settled purchase with the original buyer's signed proof, not an anonymous read endpoint.

The public free-sample Supabase function is not currently exposed under `api.centquery.dev`. Do not invent a publicly routed `/v1/catalog` or other API routes on this gateway. The static `/catalog.json` file on the future website is a preview of the currently known synthetic testnet product, not a live commercial inventory.

## Agent-safe rules

1. Discover capabilities with `/catalog.json` and `/openapi.json`. They describe only presently known preview routes and status.
2. For read-only inspection, send ordinary unsigned GETs with no wallet keys or payment headers.
3. Never initiate payments automatically or sign from static website data; require explicit buyer approval and independently validate live x402 payment terms.
4. Never return synthetic sample values as real observations.
5. Do not treat the 402 response or possession of an authorization header as proof of settled payment.
6. Respect rate limits and do not probe recovery without an already settled, buyer-owned authorization.

## Future agent-native integration

When data products exist, the next step is an authoritative machine-readable catalog served by the actual API, with live prices, schemas, freshness, provenance, data rights and availability. Consider x402 Bazaar discovery only when the corresponding payment resource is correctly deployed, verified and ready for agent buyers. This site does not claim any Bazaar registration, MCP server or agent-service federation.
