Egress route table for the Soluta model gateway (SolutaCloud). Generated from the alias contract in force — not hand-written. QĐ-033 §3: any sales claim about where data goes must be anchored to this table.
ca_hai — Depends on the edition you use. The table below states the route THROUGH THE MODEL GATEWAY — it does not state where books and source documents are stored.
| alias | destination | actual model | what is sent | grade |
|---|---|---|---|---|
banhbao-1.0 | https://api.deepseek.com | deepseek-flash | the conversation for that call (every `messages` entry you send) | ĐÃ ĐO — 8 real calls have gone through this route, counted from the ledger |
banhbao-1.1 | https://api.deepseek.com | deepseek-flash | the conversation for that call (every `messages` entry you send) | ĐÃ ĐO — 29,111 real calls have gone through this route, counted from the ledger |
banhbao-1.2 | https://api.deepseek.com | deepseek-flash | the conversation for that call (every `messages` entry you send) | ĐÃ ĐO — 50 real calls have gone through this route, counted from the ledger |
| leg | destination | when | what is sent | NOT sent | grade |
|---|---|---|---|---|---|
| gateway → RDAP registry | https://rdap.org | only when someone calls the egress-location endpoint (or the matching command-line tool) | ONE IP ADDRESS — of a target the caller itself declared | conversation content; document content; the target hostname; anything read from customer books | ĐỌC MÃ |
| gateway → the server DNS resolver | the operating system DNS resolver (address not declared) | at the same time as the leg above | A HOSTNAME the caller itself declared (possibly the host where customer books live) | conversation content; document content | ĐỌC MÃ |
This page is GENERATED FROM the machine-readable declaration — not hand-written. view the source (JSON)