OpenRouter-compatible Gateways Integration Guide

Overview

OpenRouter-compatible aggregator traffic is governed by routing it through a managed proxy to attribute outbound activity across providers and shield keys.

Support level

Compatibility Adapter + Provider/API Proxy

What Cup’n’String detects

• Custom base URLs
• Known provider domains
• API-key-bearing environment variables/config files
• Local proxy endpoints

What it governs

• Approved provider access
• API key shielding
• Model gateway routing
• Audit of agent/provider traffic

Recommended policies

• Require provider allowlist
• Use organization-approved proxy URLs
• Block direct calls to unapproved providers
• Redact API keys from logs and prompts

Setup outline

1. Ensure the Cup’n’String client is running.
2. Direct OpenRouter requests through the local proxy.
3. Configure target credentials in the secure manager interface.

Verification

Confirm OpenRouter API calls are logged and credentials are redacted in the logs.

Troubleshooting

If messages fail to deliver, verify proxy settings and SSL configuration.

Known limitations

Provider-specific metadata varies across APIs and compatibility layers.