endpoint
Datasets
All datasets matching “endpoint”exodus-endpointsreasoning-duplication-endpoint-statex402-endpoint-readinessscvd.store x402 endpoint readiness corpus
scvd.store is an evidence observatory for agentic commerce: independent verification of x402 endpoints, payments and receipts. Before an agent pays an x402 endpoint, we check that it can be paid. After it pays, we check the signed receipt. Over time we watch endpoints and publish a dated, signed corpus. Sellers use it to prove a door works; buyers use it before spending. Every artifact is signed, expires, and names what we did not see. Not escrow, not… See the full description on the dataset page: https://huggingface.co/datasets/keeper-scvd/x402-endpoint-readiness.atlas-20-information-barrier-and-the-prompt-endpoint
ATLAS report 20: does the information barrier suppress verification, and where does the prompt line end?
Complete raw products of ATLAS rl-training report 20 (GitHub issue #43).
Two new selector surfaces over every question of the canonical LiveCodeBench
(175) and GPQA (198) validation sets, each question with all eight of its
cached candidates revealed. Both carry report 18's comparison closing and
change only the system message:
barrier relaxed — the finalization paragraph's… See the full description on the dataset page: https://huggingface.co/datasets/t2ance/atlas-20-information-barrier-and-the-prompt-endpoint.hf-inference-endpoint-benchmarks
Raw benchmark result files
Raw JSON outputs from the sessions described in benchmarking-methodology.md. Model: Qwen3.5-4B family, hf-endpoints deployed via the configs documented in cli-and-api.md.
Short-prompt decode comparison (valid metric — prompt negligible vs output, see trap #1 in methodology doc)
File
Setup
llamacpp_results.json
llama.cpp, GGUF Q8_0, MTP, A10G
vllm_results.json
vLLM, FP8-dynamic, MTP, A10G
vllm_bf16_results.json
vLLM, bf16… See the full description on the dataset page: https://huggingface.co/datasets/LostGentoo/hf-inference-endpoint-benchmarks.clinical-quad-endpoint-adjudication-drift-blinding-breach-pressure-governance-submission-v0.1Clarus Clinical Quad Coupling Endpoint Adjudication Integrity v0.1
PurposeDetect adjudication drift driven by four interacting nodes.
Quad nodes
Endpoint cluster shift
Blinding gap or reviewer dominance
Operational or vendor process change
Governance submission or review pressure
InputOne vignette.
OutputStrict JSON only.
Required keys
adjudication_integrity_risk
risk_type
driver_nodes
recommended_action
action_detail
rationale
confidence… See the full description on the dataset page: https://huggingface.co/datasets/ClarusC64/clinical-quad-endpoint-adjudication-drift-blinding-breach-pressure-governance-submission-v0.1.
