@@ -38,13 +38,42 @@ It is not a hosted provider, a general OpenAI API clone, or a way to bypass acco
3838
3939## Codex Pooler Vs Direct Account Credentials
4040
41- | Question | Direct account credentials | Codex Pooler |
42- | --- | --- | --- |
43- | Client configuration | Each client needs account-specific material | Clients use stable Pool API keys |
44- | Capacity changes | Every client may need reconfiguration | Operators adjust Pool assignments and policy centrally |
45- | Routing decisions | Usually fixed by client setup | Pool policy, account health, quota evidence, model support, and continuity decide |
46- | Operator visibility | Spread across clients and local logs | Admin UI and MCP expose sanitized metadata |
47- | Secret exposure | More places can hold account secrets | Upstream secrets stay inside Codex Pooler secret storage |
41+ <table >
42+ <thead >
43+ <tr >
44+ <th >Question</th >
45+ <th >Direct account credentials</th >
46+ <th >Codex Pooler</th >
47+ </tr >
48+ </thead >
49+ <tbody >
50+ <tr >
51+ <td >Client configuration</td >
52+ <td >Each client needs account-specific material</td >
53+ <td >Clients use stable Pool API keys</td >
54+ </tr >
55+ <tr >
56+ <td >Capacity changes</td >
57+ <td >Every client may need reconfiguration</td >
58+ <td >Operators adjust Pool assignments and policy centrally</td >
59+ </tr >
60+ <tr >
61+ <td >Routing decisions</td >
62+ <td >Usually fixed by client setup</td >
63+ <td >Pool policy, account health, quota evidence, model support, and continuity decide</td >
64+ </tr >
65+ <tr >
66+ <td >Operator visibility</td >
67+ <td >Spread across clients and local logs</td >
68+ <td >Admin UI and MCP expose sanitized metadata</td >
69+ </tr >
70+ <tr >
71+ <td >Secret exposure</td >
72+ <td >More places can hold account secrets</td >
73+ <td >Upstream secrets stay inside Codex Pooler secret storage</td >
74+ </tr >
75+ </tbody >
76+ </table >
4877
4978## How It Works
5079
0 commit comments