Unified API Gateway
Call provider-independent functions such as ai.generate, email.send, sms.send, and adapter-enabled Stripe API operations through consistent authentication and response conventions.
Every feature reinforces five promises: simplify, route, protect, observe, and control.
Call provider-independent functions such as ai.generate, email.send, sms.send, and adapter-enabled Stripe API operations through consistent authentication and response conventions.
Choose compatible providers using deterministic rules for cost, latency, reliability, capability, health, usage, environment, and custom priority.
Move from primary to fallback providers on eligible timeouts, network failures, HTTP 429 responses, and provider 5xx errors.
Centralize encrypted, environment-specific provider secrets and distribute one CamiloAPI application key instead of many provider keys.
Separate keys, permissions, allowed functions, routing profiles, budgets, rate limits, and usage by project.
Trace requests and provider attempts while redacting authorization headers, keys, tokens, and other sensitive values.
Estimate spend by provider, application, and function when reliable pricing inputs are available. Estimates are not provider invoices.
Notify, prefer cheaper routes, disable expensive providers, reject requests, or continue with alerts when thresholds are reached.
Distinguish provider outages from credential errors, customer rate limits, degraded latency, and CamiloAPI connectivity.
Test functions and create cURL, Node.js, Python, and PHP starter examples from the authenticated control plane.
Reduce eligible repeat requests, latency, provider spend, and rate-limit pressure without caching sensitive or non-idempotent calls by default.
Model events such as request failures, fallbacks, budget warnings, unhealthy providers, and disabled applications.