AGV Web backend gateway
AGV API Gateway
Unified backend API surface for AGV Web apps, TaskOn compatibility, and downloads.
Current Topology
Non-verifier browser apps call agv-api. The verifier product boundary is agv-verifier web + /api/verifier/*.
Direct agv-http backend URLs stay server-side. Browser clients should not call verifier backends directly.
App Namespaces
/api/main/*— AGV Web main app backend namespace/api/fund/*— G3 funding backend namespace/api/invest/*— Investor portal backend namespace/api/buy/*— Buy page backend namespace/api/taskon/*— Live TaskOn compatibility API/api/downloads/manifest— Public download manifest
Archived Verifier Surface
The active verifier API facade now lives in agv-verifier. The old agv-api verifier implementation is retained only as archived history.
src/app/api/_archived/verifier/**— Archived verifier route handlerssrc/domains/_archived/verifier/**— Archived verifier gateway domain and tests
Runtime Boundary
agv-apiowns non-verifier backend namespaces.agv-verifierowns the verifier website and public verifier API facade.agv-httpowns verifier backend semantics, verdict generation, vectors, and evidence checks.- This page does not claim official W3bstream execution, IoTeX approval, production mint, yield, or reward readiness.
- TaskOn is live as a compatibility API namespace inside
agv-api; the retired standalone Vercel TaskOn project remains archived only for rollback reference.
Health check: /api/health