// agent surface v1.10.0
A machine surface for reading l0g without scraping.
Agent Surface v1.10.0 exposes the l0g corpus as static JSON and NDJSON: catalog, evidence graph, sourced claims, primary sources, freshness, Risk Diff, Black Box Recorder, signal history, fingerprints and an OpenAPI contract. The promise is simple: an agent should be able to cite a claim without losing the source, claimDate, observationDate, sourcePublicationDate, retrievedAt, indexedAt or reading level.
// endpoints
/agents.json Capability manifest, endpoints, usage rules and proof policy.
Contract/openapi.json OpenAPI 3.1 description of machine-consumable endpoints.
Catalog/api/v1/catalog.json Complete corpus map: articles, guides, topics, glossary atlas, sources and protocol.
Catalog NDJSON/api/v1/catalog.ndjson Line-by-line catalog for streaming ingestion, RAG or incremental indexing.
Claims/api/v1/claims.json Claim-source graph with typed claims, references and dates when detectable.
Evidence graph/api/v1/evidence-graph.json Articles, claims, references, hosts, primary sources and datasets as nodes and edges.
Sources/api/v1/sources.json Primary sources and cited hosts actually used by the corpus.
Freshness/api/v1/freshness.json Freshness policy, last content updates and signal timing metadata.
Integrity/api/v1/integrity.json Canonical SHA-256 fingerprints of M2M surfaces.
Changefeed/api/v1/changes.json Machine-readable publication and revision feed.
Risk Diff/api/v1/risk-diff.json Risk changes over 1, 7 and 30 days.
Black Box/api/v1/black-box.json Point-in-time hashed frames for replaying public risk states.
Signal history/api/v1/signals/history.json Point-in-time signal observations, level changes, coverage and policy.
Signal NDJSON/api/v1/signals/history.ndjson Line-by-line signal history for agents, watchers and incremental ingestion.
Signal CSV/api/v1/signals/history.csv Flat signal observations for pandas, R, DuckDB or spreadsheets.
// recommended flow
- Discover the surface with /agents.json.
- Read /api/v1/freshness.json to date the corpus and dashboard signals.
- Verify fingerprints with /api/v1/integrity.json when a response depends on a fixed snapshot.
- Watch /api/v1/changes.json for new content and revisions.
- Use /api/v1/risk-diff.json to understand what changed in risk over 1, 7 or 30 days.
- Use /api/v1/black-box.json to replay a public date without filling historical gaps.
- Use /api/v1/signals/history.csv or .ndjson for point-in-time replay without look-ahead bias.
- Use /api/v1/evidence-graph.json to traverse article → claim → source relationships.
- Switch to NDJSON feeds for line-by-line ingestion.
- Use /api/v1/catalog.json or /llms.txt to find content.
- Quote factual claims via /api/v1/claims.json when the answer depends on a precise assertion.
- Preserve the canonical URL, date fields and claim kind in generated answers.
// guardrails
Fields such as kind, dateLabel, references and confidence are not decoration. They prevent a scenario or estimate from being turned into an observed fact, and remind consumers that extracted relations remain verifiable in the canonical page.
// minimal contract
// example
curl -s https://l0g.fr/api/v1/claims.json// integration
For a RAG agent, use /api/v1/catalog.ndjson for document discovery, then /api/v1/evidence-graph.json or /api/v1/claims.ndjson for sensitive assertions. /api/v1/changes.ndjson avoids rescanning the whole corpus. /openapi.json is the typed entry point for client generation.