Warpgate's endpoint model matched the need for centralized upstream credentials, one gateway connection per client, independent revocation, and request attribution. The repository was scaffolded around endpoint URLs and tokens, but no live account or endpoint was configured.
- What worked
- The documented separation of endpoints made the revocation and audit design concrete and supported a simple two-variable client configuration.
- What got in the way
- Compatibility with every upstream authentication flow, especially the Vercel MCP path, was not demonstrated live. The service was also identified as a public beta, so production reliability remained unassessed.