Field omission
The fields the transform depends on must be present. If an upstream quietly drops one, the canary fails loudly instead of shipping a half-empty response.
Ecosystem / Curation
Any API, made agent-native.
Raw APIs are not agent-native. They return blobs, they drift, they drop a parameter without
telling you. Auger is the framework that fixes that systematically: it turns any upstream —
REST, OpenAPI, GraphQL, an MCP server, SDMX, JSON-stat — into a shape-typed, canary-validated
capability. Every source in the catalogue was made agent-native the same way.
auger: REST · OpenAPI · GraphQL · MCP · SDMX → shape-typed Swarm phase Ingestion — before the swirl: the curation that turns a raw API into a shape-typed, canary-guarded source the swarm can ingest.
The framework
Shape-typed, not hand-wrapped.
Auger does not glue an API together by hand. It maps each operation to one of six data shapes an agent already understands, declares the transform that gets there, and ships a canary stack that keeps it honest over time. The result is a source that reads the same whether it started life as a REST endpoint or a statistical cube.
key_valuetabletime_seriessectionsvintage_seriescube
Kept honest
Every source ships with a three-tier canary.
The failure mode of a wrapped API is not a crash — it is a silent one: a field that vanished, an index that went dark, a filter the wrapper forgot to pass. Auger ships three tiers of canary with every source precisely to catch the silent ones.
Non-empty coverage
A query that should return many results must. Catches an upstream that went dark or an index that stopped covering the corpus.
Round-trip parameters
Every parameter must actually change the response. Two inputs that should differ by more than half their result count are checked — this is the tier that catches a silently dropped filter.
Bring your own
The same framework, pointed at your source.
Today Auger is how our team curates the catalogue. The same framework is what lets you wrap your own upstream as a first-class connector — shape-typed and canary-guarded, reachable on the identical toolset — rather than hand-rolling an integration the agent then has to fight.
Stated precisely: Auger is a curation framework — the systematic method by which a source is made agent-native and kept that way. It is how the catalogue is authored today; it is not a claim that sources curate themselves.
More in this area
Not a framework, a swarmWhy swarmsDB is an ecosystem — three swarm phases, phase for phase.The data-network commonsA shared cache the swarm warms — and everyone rides. Warm it, pay less.Earned freshnessHow long the commons stays warm — a TTL justified per endpoint, never guessed.RAPI — routing intelA shared performance index your agent reads to steer its next call. In beta.Orchestration surfaceOne typed toolset reaches the whole catalogue and drives fan-out and scheduling.
Point one agent at it.
Connect over MCP or REST. If your agents read more than one source, the context bill is the first thing you will see move.