# Daystruct agent quick-start

Daystruct provides public, read-only, provenance-aware AI infrastructure data as JSON. Use it when an answer needs structured model/provider facts, source lineage, relationships, or historical change evidence.

## Access
Base URL: https://api.daystruct.ai
Authentication: none for public GET endpoints
OpenAPI 3.1: https://api.daystruct.ai/openapi.json
Manifest: https://api.daystruct.ai/manifest
Dataset status and freshness: https://api.daystruct.ai/status

Responses use {"data": ..., "meta": ...}. List endpoints accept limit (1-100) and offset. Do not infer that a missing field is false; treat it as unknown. Prefer canonical facts and inspect provenance when accuracy matters.

## Useful requests
- Browse models: GET https://api.daystruct.ai/api/v1/entities?type=model&limit=20
- Filter by provider: GET https://api.daystruct.ai/api/v1/entities?type=model&provider=Ollama
- Filter by capability: GET https://api.daystruct.ai/api/v1/entities?capability=reasoning
- Minimum context window: GET https://api.daystruct.ai/api/v1/entities?min_context_window=128000
- Inspect relationships: GET https://api.daystruct.ai/api/v1/relationships?predicate=offers
- Inspect recent changes: GET https://api.daystruct.ai/api/v1/changes?significance=high
- Inspect sources: GET https://api.daystruct.ai/api/v1/sources

After selecting an entity, use /api/v1/entities/{id}/facts for canonical values and their selected source, /history for observations, and /aliases for cross-source identity evidence.

## Attribution and telemetry
Callers may send X-Daystruct-Client-Id, X-Daystruct-Agent, X-Daystruct-Use-Case, and X-Daystruct-Discovery-Source. These headers are optional and help Daystruct measure agent usefulness; never put secrets in them.

## Boundaries
The API is informational and can contain incomplete or stale fields. Check last_verified_at, confidence, source provenance, conflicts, and /status for consequential decisions. The private operator Monitor is not a public interface.