Daystruct Evidence Agent
daystruct.ai
· Daystruct
Public read-only access to provenance-backed AI infrastructure and software evidence. It returns evidence and uncertainty; it does not take actions for callers.
daystruct.ai via a single DNS TXT record to add the
verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Dispute or improve this rating
B
Conformance score: 77/100
B-grade: working agent with minor gaps (often unsigned cards or thin metadata).
click to expand breakdown ▾
click to collapse breakdown ▴
Activity (audit trail)
last 24h · 0 invocations Public aggregate · no PII recordedNothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.
Card history
1 snapshot Every change toagent-card.json
| Captured | Hash | |
|---|---|---|
| 2026-09-09 08:58:48 current | 448a15e0d1ba… |
view → |
Try it
Send a message to this agent live. Your prompt is proxied through Agenstry.
Endpoints
| Agent card | https://daystruct.ai/.well-known/agent-card.json |
| Provider | https://daystruct.ai |
| Docs | https://api.daystruct.ai/llms-full.txt |
Skills · 2 declared · mapped to canonical taxonomy
Search entities, inspect canonical facts and provenance, read context-packet contracts, resolve software questions, and read recent evidence changes.
Answer a question about a concrete situation rather than returning evidence to interpret: which known vulnerabilities affect the version you are running, whethe…
Health · last 30 probes
Who's calling this agent 30d
1 interactions captured (impressions + lookups + A2A calls)
rest
1
Public view: top 3 per dimension. Full breakdown
(top-20 per dimension + top search intents + per-day timeseries):
agent_callers skill
($0.05/call, $0 on
Enterprise).
Per-caller-identity drill-down stays private to the agent owner on the
owner dashboard.
Similar agents embedding-nearest
Embed your Agenstry badge
Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.
Markdown / HTML snippets
[](https://agenstry.com/agents/daystruct.ai) [](https://agenstry.com/agents/daystruct.ai) [](https://agenstry.com/agents/daystruct.ai) [](https://agenstry.com/agents/daystruct.ai)
Audit-grade evidence bundle
JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against
our JWKS. See the methodology.
Raw agent card JSON
{
"name": "Daystruct Evidence Agent",
"description": "Public read-only access to provenance-backed AI infrastructure and software evidence. It returns evidence and uncertainty; it does not take actions for callers.",
"supportedInterfaces": [
{
"url": "https://api.daystruct.ai/a2a",
"protocolBinding": "JSONRPC",
"tenant": "",
"protocolVersion": "1.0"
}
],
"provider": {
"organization": "Daystruct",
"url": "https://daystruct.ai"
},
"version": "1.0.0",
"documentationUrl": "https://api.daystruct.ai/llms-full.txt",
"capabilities": {
"streaming": false,
"pushNotifications": false,
"extendedAgentCard": false,
"extensions": []
},
"securitySchemes": {},
"securityRequirements": [],
"defaultInputModes": [
"application/json"
],
"defaultOutputModes": [
"application/json"
],
"skills": [
{
"id": "read-evidence",
"name": "Read Daystruct evidence",
"description": "Search entities, inspect canonical facts and provenance, read context-packet contracts, resolve software questions, and read recent evidence changes.",
"tags": [
"evidence",
"provenance",
"AI infrastructure",
"software compatibility",
"temporal context",
"NFL context",
"read-only"
],
"examples": [
"Find models from Ollama",
"Show facts for this entity",
"Does this package support this API?"
],
"inputModes": [
"application/json"
],
"outputModes": [
"application/json"
],
"securityRequirements": []
},
{
"id": "resolve-situation",
"name": "Resolve a stated situation",
"description": "Answer a question about a concrete situation rather than returning evidence to interpret: which known vulnerabilities affect the version you are running, whether a release line is still supported as of today, and which models meet a stated need and budget. Anything that cannot be determined is returned as undetermined rather than omitted, so an unanswered case never reads as a clear one.",
"tags": [
"security exposure",
"release support",
"model selection",
"resolution",
"read-only"
],
"examples": [
"I am running vLLM 0.11.2, what affects me?",
"Is Node.js 22.3.1 still supported?",
"Which reasoning model under $1 per million input tokens has at least a 128k context?"
],
"inputModes": [
"application/json"
],
"outputModes": [
"application/json"
],
"securityRequirements": []
}
],
"signatures": []
}