zauth
zauth is our optional x402 trust and telemetry layer — endpoint directory, verification checks, and Provider Hub events after successful paid calls. It does not replace PayAI/Dexter settlement.
Status: Integrated (enable with ZAUTH_API_KEY in Vercel)
Directory: zauth.inc/database ↗
Provider Hub: zauth.inc/provider-hub ↗
Public APIs on Concierge
| Route | Purpose |
|---|---|
GET /api/zauth-directory | CORS-open proxy to zauth endpoint directory |
GET /api/zauth-status | Live verification checks for this origin (when key set) |
GET /api/x402-config | zauthTelemetryEnabled + discovery links |
Source: lib/concierge-api/zauth.ts, zauth-paid-response.ts
Telemetry (Provider Hub)
After successful x402 settlement on paid routes (Concierge, intel, news-open, signals), Concierge fires async events to zauth when ZAUTH_API_KEY is configured.
Helps agents choose reliable APIs via success rate, uptime, and verified badges in the zauth Database.
Enable (operators)
# Vercel environment variables
ZAUTH_API_KEY=your_zauth_provider_api_key
# optional override:
# ZAUTH_API_ENDPOINT=https://back.zauthx402.comSee .env.example and full markdown guide in repo docs/zauth.md.
Verify integration
curl -s https://conc-exe.xyz/api/zauth-directory | jq '.endpoints | length'
curl -s https://conc-exe.xyz/api/x402-config | jq '.zauthTelemetryEnabled, .discovery.zauth'Related
Concierge Agent · zauth trust layer · zauth.inc