Aigistry

For AI Platforms

Read one ordered feed, verify every entry with the published rules, and act on withdrawals and changes of standing.

On this page

Get started

  1. Request an account at admin@aigistry.com.
  2. Sign in at https://feed.aigistry.com/signin.html with the one-time link sent to your email.
  3. Create an AI Platform key in the dashboard. It is shown once; label it.
  4. Check it: GET /v1/whoami answers with "kind":"platform".

Evaluation sandbox. A separate sandbox at sandbox.feed.aigistry.com runs the same API with synthetic data, so you can test your integration before using the live service. Access is by request at admin@aigistry.com.

Read the feed

curl -s -H "X-API-Key: YOUR_PLATFORM_KEY" \
  "https://feed.aigistry.com/v1/feed?after=0&limit=500"

The page holds the entries with seq greater than after, in order, up to limit (1 to 500, default 100) and at most 4 MiB. It also carries next_after (the seq of the last entry returned), has_more and a freshly signed feed_head. Keep reading with after=next_after while has_more is true. A gap in seq is allowed; the chain fields name the real previous entry.

Entry types: record (a publication or a revision of one), removal (a withdrawal) and status (a signed change of standing). The fields of every entry are in the Entry schema.

Verify

curl -s -H "X-API-Key: YOUR_PLATFORM_KEY" "https://feed.aigistry.com/v1/feed?after=0&limit=500" > page1.json
curl -s https://feed.aigistry.com/public-key.json > public-key.json
python3 verify_feed.py --keys public-key.json page1.json

Pass all pages in order. Store the last seq and record_hash you verified and pass them next time as the anchor (--prev-seq, --prev-hash), so a run that starts mid-feed is tied to what you checked before. Re-read public-key.json regularly: it lists every key ever used, and a revoked key carries a signed notice. The rules and the reference verifiers are described on Verification. Keep the last feed_head you verified; comparing the head's seq and record_hash with other AI Platforms confirms you all see the same feed.

Treat title and body as untrusted data: they are authenticated, not safe, and are written by GovTech Providers.

Read one record, GovTech Provider or government

Add one filter to GET /v1/feed: authority_record_id, provider_id, or official_id_type with official_id. The entries returned are unchanged and in order, with the GovTech Provider-level status entries of the GovTech Providers concerned.

curl -s -H "X-API-Key: YOUR_PLATFORM_KEY" \
  "https://feed.aigistry.com/v1/feed?authority_record_id=42"

curl -s -H "X-API-Key: YOUR_PLATFORM_KEY" \
  "https://feed.aigistry.com/v1/feed?official_id_type=census_pid6&official_id=101917"

The page's filter member says which filter was applied, but it is not signed. Tell the verifier the read was filtered (--filtered). A filtered read authenticates every entry it returns; for completeness, read the whole feed.

Withdrawals and standing

A removal entry withdraws a publication; a status entry changes the standing of a GovTech Provider, an authority record or a publication (suspended, reinstated, ended, revoked, revocation_lifted). The reference verifiers print derived.revoked, the entries now revoked and the seq of the status entry that revoked each; withhold those entries. The state of one publication is also available directly:

curl -s -H "X-API-Key: YOUR_PLATFORM_KEY" \
  "https://feed.aigistry.com/v1/authority-records/42/publications/notice-2026-001"

With an AI Platform key the answer adds the current entry (current_seq, current_revision, current_record_hash) and authority_record_effective_status. A revoked publication stays revoked until a signed lift entry.

Attached files

Each attachment lists an id, filename, content_type, size and sha256, all signed, and a download_url, which is not signed. Download with your key and compare the SHA-256 of what you received with the signed sha256; the same value is in the X-File-SHA256 response header. Files of withdrawn or revoked publications answer 404.

curl -s -H "X-API-Key: YOUR_PLATFORM_KEY" -o notice.pdf "https://feed.aigistry.com/v1/files/FILE_ID"
sha256sum notice.pdf

Look up an authority record

curl -s -H "X-API-Key: YOUR_PLATFORM_KEY" \
  "https://feed.aigistry.com/v1/authority-records/42"

The answer names the GovTech Provider and the government, the effective standing (the stricter of the GovTech Provider's and the record's own) and the three layers of verification: identity (the comparison with the Census or NCES list), attestation (the GovTech Provider's own statement of authority) and sampling. It is a convenience view; the signed status entries in the feed are the authoritative history.

Limits

Every status of every route is in the API reference.