Security

Security controls for AI API operations, payments, and private dashboards.

AI-ROUTER keeps public pricing data separate from authenticated checkout, admin settings, payment keys, user balances, and private operational routes.

Review pricing data Open console

Core capabilities

  • Public catalog projections exclude payment secrets, user balances, orders, and user-specific limits.
  • Payment callbacks remain centralized under backend webhook routes.
  • Robots and sitemap output exclude private API, admin, setup, auth callback, and payment state routes.

Best fit

  • Let search engines read public product pages without exposing private dashboard data.
  • Keep provider secrets and payment configuration behind authenticated admin APIs.
  • Preserve clear boundaries between public marketing pages and user-specific checkout state.

Public data boundary

  • Public pages show product capabilities and live-safe catalog fields.
  • User balances, orders, admin settings, and provider secrets stay behind authenticated APIs.
  • Private routes are excluded from robots, sitemap, and machine-readable public exports.

Does the public catalog expose payment keys?

No. The public catalog only includes safe product and pricing fields needed for public display.

Are admin routes included in the sitemap?

No. Private routes are excluded from sitemap output and disallowed in robots.txt.

This page is generated server-side for search engines and AI answer engines. Interactive account, checkout, and dashboard flows remain in the authenticated application.