🔐
Security basics
API keys, request IDs, HTTPS-only access, origin isolation, least-privilege secrets, and administrative access controls.
Trust center
Infrastructure customers can explain to procurement.
SilkRouter is being designed with clear data handling, abuse controls, account limits, and enterprise procurement needs from day one.
🧭
Routing transparency
Enterprise customers can request provider restrictions, no-retention handling, and written route policies.
🧾
B2B operations
Invoices, account-level limits, usage exports, acceptable-use rules, and support channels for customer procurement teams.
Current commitments
These commitments apply to the early access service unless a written enterprise agreement states otherwise.
| Area | Commitment | Enterprise option |
|---|---|---|
| Training use | Customer prompts and outputs are not used by SilkRouter to train foundation models. | Written no-training commitment |
| Retention | Operational logs may be retained for abuse prevention, billing, debugging, and security. | Custom no-retention or shortened retention |
| Provider routing | Requests may be routed to configured upstream model providers. | Allowlist or blocklist providers |
| Abuse prevention | Spam, phishing, credential theft, malware, and evasion use cases are not allowed. | Custom review workflows |
| Support | Email support for approved early access customers. | Dedicated support and SLA by agreement |
Security contact
Report suspected vulnerabilities, leaked keys, or abuse patterns to [email protected].
Abuse contact
Report platform abuse, phishing, spam, or suspicious activity to [email protected].