Use this page to verify the website API surface that is currently backed by source files. Each route lists its method, request shape, response behavior, auth boundary, and owning route file.
8
Generated from live route handlers
3
Verification, lead capture, telemetry
4 GET / 4 POST
No legacy /api/v1 routes
Endpoint taxonomy
These are the documented website API surfaces currently backed by source routes. Each entry names the method, route, request shape, response expectation, auth boundary, and owning route file.
| Route | Method | Exposure | Owner file |
|---|---|---|---|
| /api/intel/verify | GET | Public status | app/api/intel/verify/route.ts |
| /api/intel/verify | POST | Validated request | app/api/intel/verify/route.ts |
| /api/contact | POST | Validated request | app/api/contact/route.ts |
| /api/subscribe | POST | Validated request | app/api/subscribe/route.ts |
| /api/health | GET | Public status | app/api/health/route.ts |
| /api/vision/stats | GET | Operator telemetry | app/api/vision/stats/route.ts |
| /api/analytics/page-views | GET | Operator telemetry | app/api/analytics/page-views/route.ts |
| /api/analytics/page-views | POST | Operator telemetry | app/api/analytics/page-views/route.ts |
Routes for checking the intelligence proxy and submitting validated verification requests when provider credentials are configured.
/api/intel/verifyPublic statusapp/api/intel/verify/route.tsReturns service name, operational status, and whether the backend intelligence provider key is configured.
/api/intel/verifyValidated requestapp/api/intel/verify/route.tsValidates a query and optional entity type before proxying to the configured Innora intelligence provider.
Website request routes for contact, enterprise, support, partnership, and newsletter flows with validation and provider configuration checks.
/api/contactValidated requestapp/api/contact/route.tsValidates contact form payloads, verifies Turnstile, rate limits by client IP, and forwards configured messages to Telegram.
/api/subscribeValidated requestapp/api/subscribe/route.tsValidates newsletter email submissions and forwards them only when an HTTPS newsletter webhook is configured.
Operator-owned routes used by the website for health checks, Nora Vision showcase metrics, and page-view telemetry.
/api/healthPublic statusapp/api/health/route.tsReturns process uptime, memory usage, runtime version, and current health timestamp for deployment monitoring.
/api/vision/statsOperator telemetryapp/api/vision/stats/route.tsFetches Nora Vision node statistics with rate limiting and reports offline or degraded nodes without simulated success data.
/api/analytics/page-viewsOperator telemetryapp/api/analytics/page-views/route.tsReads single or batch page-view counts for blog and content surfaces when Redis is configured.
/api/analytics/page-viewsOperator telemetryapp/api/analytics/page-views/route.tsIncrements a page-view counter with client-IP rate limiting when Redis is available for persistence.
Integration handoff
The public API documentation is intentionally limited to verified website route handlers. For customer integrations, confirm data boundaries, provider configuration, and delivery secrets before relying on a success path.
Expose health or readiness information only; they do not imply customer environment availability.
Require schema validation, rate limiting, and configured server-side providers before success is returned.
Support website observability and showcase data; they are not customer integration contracts.
Start with SDK install commands, then use the contact integration review for provider-specific webhook or connector questions. Secret values are never documented on this public page.