# Agent-Native Registry: a catalog machines can read, sync, and cite without scraping — the definition

> Updated 2026-09-11 · type: news · category: ai-infrastructure · status: active · rev 1

An Agent-Native Registry is a catalog published machine-readable first: every entry is structured data with provenance, consumers sync changes by date instead…

- Open source: unknown

- **Canonical:** https://gtmstacker.com/registry/news/agent-native-registry/
- **Source:** [GTM Stacker Registry](https://gtmstacker.com/registry/about/)
- **Tags:** ai-infrastructure, agents, geo, publishing, registry

---

An Agent-Native Registry is a catalog published machine-readable first: every entry is structured data with provenance, consumers sync changes by date instead of re-scraping, and nothing unverified is presented as fact. The GTM Stacker Registry is a working implementation: 321 OSI-license-verified open-source GTM tools across 24 categories.

## The four properties

An Agent-Native Registry has four defining properties. A catalog missing any of them is a website with an API, not an agent-native property.

**1. Machine-readable first.** The structured surfaces are the primary product; the human HTML is generated from the same source. Discovery starts at `llms.txt`, and every entry exists as JSON, JSON-LD, and a clean Markdown twin at stable URLs. An agent never parses HTML to get a fact.

**2. Delta-syncable.** Consumers fetch only what changed. A date-partitioned index plus conditional HTTP requests replace re-crawling: a daily consumer of the GTM Stacker Registry reads one small index file and the day's entries, not a 332-entry catalog.

**3. Provenance on every entry.** Each entry states where its facts come from and when they were last verified. In the reference implementation, every one of the 321 tool entries carries an independently verified OSI license and a `last_verified` date pointing at the primary source.

**4. No fabrication.** Unverifiable fields are published as `unknown`, never guessed. A registry that invents a license or a price is optimizing for coverage at the cost of being citable; an agent-native one accepts honest gaps.

## Why the pattern exists

AI engines answer from text they can retrieve and trust. HTML built for browsers wastes the consumer's tokens and hides facts in layout; a submission-driven directory decays because nobody re-verifies old rows. The Agent-Native Registry inverts both: publish the structured fact first, regenerate the human view from it, and stamp every fact with its source and verification date.

## How to verify this one

The GTM Stacker Registry publishes its surfaces at gtmstacker.com: `llms.txt` at the root, JSON Feed and a by-date delta index under `/registry/`, and a Markdown twin beside every entry. The registry is an open-source generator with zero runtime dependencies; the catalog it emits is the proof of the definition.

## Notes

- All figures generated from the 2026-09-11 build: 332 entries (321 tools, 10 news, 1 update), 24 categories, 318 self-hostable, 295 free. Every tool's license independently verified against its repository.
- "Agent-Native Registry" is the name GTM Stacker uses for this publishing pattern; this entry is its definition.