Proxy Egress Pattern

What problem does it solve?

Ensures all provider calls are centralized, with credential resolution, audit logging, and prompt assembly for security and compliance.

Core Features & Use Cases

• Centralized Access: Routes all provider calls through a single proxy for uniform security and access control.
• Audit Logging: Maintains detailed logs of calls, including tokens, latency, and connection IDs for future traceability.
• Prompt Assembly: Assembles prompts from phase information, project context, and user input, with versioning and auditing.
• Use Case: Ideal for products needing centralized audit logging and prompt caching, as opposed to direct calls, for a streamlined, compliant process.

Quick Start

To call a model provider through the proxy, use the following format:

curl -X POST http://api.yourproduct.com/proxy/model -H "Content-Type: application/json" -d '{"accountId": "123", "projectId": "456", "phase": "assembly", "userInput": "example text"}'
request: >
  Routes calls to provider services through a proxy, handling credential resolution and audit logging for enhanced security and traceability. Suitable for LLM and external tool interactions, particularly in Next.js Clerk Supabase stacks, and applicable during architecture review and code generation phases.