Intake

Where data enters the federation.

The federation — the shared network of city nodes behind the index — takes data four ways: connect a live API, drop a file, subscribe to a webhook, or enter manually. Each route lands in one of the matrix's twenty cells (pillar × scale). Every upload runs an extraction preview with confidence scores before commit — high-confidence fields auto-commit; low-confidence fields queue for human approval in the review queue. Demonstration intake — uploads and entries here are sample flows; operator accounts arrive with live ingestion.

▤ Source registry ⟲ Review queue

▦ File upload — PDF / CSV / Excel / JSON / GeoTIFF

drop or click

Drop a file to extract. Supports PDF (LLM extraction with confidence per field), CSV/Excel (schema mapper), JSON (validation against cell schema), GeoTIFF (tile registration).

.pdf · .csv · .xlsx · .json · .tif · .tiff · .geojson

↻ Live API connectors

—

All sources →

↦ Webhook subscriptions

push from source → node · sample list

INE Spain regional accountsPOST → /webhooks/ine-quarterly

Eco × Reg
live
IAAC sensor courtyardPOST → /webhooks/iaac-courtyard

Env × Com
live
Fab Lab BCN machine logsPOST → /webhooks/fablab-bcn-mlog

Eco × Com
partial

Add webhook · name

Feeds cell

✎ Manual entry — for the field

always provenance-logged

For indicators where no API exists — repair-café logs, council attendance, machine-hours, banjar (Balinese hamlet council) records. Manual entries always carry your signature and the timestamp of submission.

Cell

Indicator

Value

Observation date

Justification / context