使用已有密钥,在本站检测模型连接与响应表现;需要核对来源时,再验证独立的证明材料。Check model connectivity and performance here with an existing key. Verify independent evidence when you need to confirm the source.
不用准备文件,直接检测你的模型Check your model without preparing files
模型列表按所选密钥与线路读取,协议自动匹配。整个检测流程留在本站。Models are loaded for the selected key and route, with automatic protocol matching. The entire check stays on this site.
01
选择已有 KeyChoose an existing key读取账户里的密钥,无需复制粘贴Use keys from your account, without copying and pasting
02
选择模型与线路Choose a model and route自动获取模型,默认使用本站入口Load models automatically and use the default site endpoint
03
查看检测结果Read the results分项评分与详细报告Dimension scores and a detailed report
开始模型评测Start model assessment需登录;点击开始才调用模型,按实际用量计费。Sign in to use this feature. Inference starts only after you click Start and is billed by actual usage.
调用成功说明本次连接可用,不等于模型身份已被认证。A successful call confirms this connection worked. It does not certify the model’s identity.
来源证明尚未开放自动签发Automatic source evidence issuance is not available yet
线路检测可直接使用。已有兼容的证明文件,也可以在下方核验;普通 API 响应本身不包含硬件证明。Connection checks are ready to use. Existing compatible proof files can be verified below; ordinary API responses do not contain hardware evidence.
未提供本站证明No portal proof provided已有证明文件?在本站核验Already have a proof file? Verify it here需要完整响应与独立信任基准Requires the complete response and an independent trust reference
仅打开外部页面,不自动携带账户、API Key 或响应内容。这是开源工具入口,不表示本站已取得第三方认证。Opens an external page without automatically passing your account, API key, or response. This links to an open-source tool; it is not a certification of this portal.
用一条不含业务隐私的测试请求准备材料;API Key 不属于需要交给第三方的材料。Capture a test request without private business data. Your API key is not part of the evidence a third party needs.
01
完整响应Complete response
保存带 tee.proof 的原始 SSE,或完整 multipart/mixed 响应。只复制签名片段无法核对正文是否被改动。Save the original SSE with tee.proof, or the entire multipart/mixed response. A signature alone cannot establish whether your response body was modified.
02
可信的构建基准Trusted reference measurement
从公开源码复现构建,或从独立可信来源取得预期 PCR0。响应包自带的 PCR0 不能给自己背书。Reproduce the public source build or obtain the expected PCR0 from an independently trusted source. A PCR0 included in a response cannot establish its own trust.
03
请求与随机挑战Request and random challenge
保留发出的请求字节、预期上游和请求前生成的 nonce。按网关约定传入挑战,再核对证明绑定,防止拿旧响应冒充本次结果。Keep the request bytes, expected upstream, and a nonce generated before the request. Send the challenge using the gateway’s supported mechanism and verify its binding to detect replay.
如何取得响应材料Capture response evidence
Anthropic Messages · SSE
以下示例只适用于已经接入相应证明协议的线路。添加请求参数或保存文件本身不会生成 TEE 证明。These examples require a route implementing the proof protocol. Request parameters and saved files cannot create a TEE proof by themselves.
先在当前终端设置 PORTAL_API_KEY。命令适用于 Bash / Zsh;Windows 可在 WSL / Git Bash 执行。使用 --output 保留字节,不要用编辑器重新排版响应。测试调用按实际规则计费。Set PORTAL_API_KEY in the current terminal. Use Bash / Zsh, or WSL / Git Bash on Windows. Save with --output and do not reformat the response in an editor. Test calls use your normal billing rules.
预期 SSE 末尾包含 event: tee.proof。若网关返回 tee.proof_unavailable 或没有证明,结果应为缺少证明,不能判定模型真假。此通用示例未传入客户端 nonce;需要验证本次请求新鲜性时,先按实际网关支持的方式传入随机挑战。Expect event: tee.proof at the end of the SSE. Missing evidence or tee.proof_unavailable means unverified, not a counterfeit model. This generic example does not send a client nonce; use your gateway’s supported challenge mechanism to establish freshness for your request.
3交由第三方逐项核对Check each item with an external verifier
打开第三方验证器,手动载入完整响应,并核对自己保留的请求、挑战与独立 PCR0 基准。不要仅凭页面总状态或响应里的 model 名称判断。Open the verifier and manually load the complete response. Compare against your retained request, challenge, and independent PCR0 reference. Do not rely only on an overall status or the response’s model name.
非流式响应怎么保存?How do I capture a non-streaming response?
该参考实现通过 x-wokey-tee-proof-mode: multipart 请求头协商非流式证明,返回完整 multipart/mixed 材料。此请求头是该实现的约定,不是通用 API 标准;仅在运营方确认线路支持后使用。只保存普通 JSON 无法补出硬件证明。The reference implementation uses x-wokey-tee-proof-mode: multipart to request non-streaming evidence. This implementation-specific header is not an API standard; use it only on confirmed compatible routes. Saving ordinary JSON does not add hardware attestation.
READ THE RESULT
核对每一项证据,再理解结果Check each piece of evidence
硬件证明与代码Hardware attestation and code
验证 AWS 根证书链、COSE 签名和证书有效期,并将证明中的 PCR0 与独立构建基准比较。Validate the AWS certificate chain, COSE signature, and certificate validity, then compare the attested PCR0 with your independent reference.
签名与内容完整性Signature and content integrity
检查签名公钥是否被硬件证明绑定、声明签名是否有效,再核对原始请求和响应字节的哈希。Check the attested signing key and statement signature, then compare the hashes of the exact request and response bytes.
本次请求与来源Request binding and provenance
核对挑战 nonce、预期上游域名、路径与状态;再读取已经通过完整性验证的响应中的模型标识。Check the challenge nonce, expected upstream host, path, and status. Read the model identifier only from the integrity-verified response.
全部相关检查通过,可支持“这些字节来自证明中声明的上游,且未被中转改动”。仍需确认该上游是否为你认可的官方服务;任意域名返回 Claude / GPT 字样,并不能证明它是官方模型。Passing the relevant checks supports that these bytes came from the stated upstream without relay modification. You must still establish that the upstream is the official service you trust. A Claude / GPT label from an arbitrary domain is insufficient.
此类证明不检查供应商内部模型权重,也不保证输出质量或服务 SLA;它不保证中转方看不到明文。缺少证明表示无法验证,校验失败表示证据存在问题,二者都不应自动标记为假模型。This does not inspect a provider’s model weights, guarantee output quality or an SLA, or hide plaintext from the relay. Missing proof means unverified; failed checks indicate an evidence problem. Neither automatically establishes a counterfeit model.
真实性与使用质量,分别评估Assess provenance and quality separately
来源证明回答“这份响应从哪里来”;质量检测关注“这条线路与模型是否满足你的任务”。Provenance evidence addresses where a response came from. Quality testing assesses whether a route and model meet your task requirements.
01 / AVAILABILITY
可用性与稳定性Availability and reliability
在固定时间段记录成功率、429 限流、5xx 错误与超时;单次请求成功不能代表长期稳定。Track success rates, 429 rate limits, 5xx errors, and timeouts over a defined period. One successful request does not establish long-term reliability.
02 / PERFORMANCE
延迟与使用成本Latency and cost
结合首 Token 时间、整体耗时、缓存命中率与实际消费。不同提示词、输出长度和并发条件需要分别比较。Compare time to first token, total duration, cache hit rate, and cost under consistent prompts, output lengths, and concurrency.
03 / TASK QUALITY
固定任务表现Performance on fixed tasks
用相同模型参数和可评分任务多次测试代码、推理与工具调用,保留样本和时间。不能靠模型自述或一道题判定账号是否降智。Repeat scored coding, reasoning, and tool tasks with consistent model settings. Retain samples and timestamps. Self-descriptions or a single question cannot establish an account’s intelligence level.
检测线路与基础任务Check routes and basic tasks
登录后可手动检测自己的 API Key 与线路,并查看固定任务结果。上游账号健康仅管理员可见;尚未启用定时评测和长期质量评分。Sign in to manually check your API key and route and review fixed-task results. Upstream account health is visible only to administrators; scheduled evaluation and long-term quality scoring are not enabled.