AgentPact is one product in four layers: an open format (AGIF), an intent-based router, a cryptographic provenance standard, and a live HTTP 402 endpoint that autonomous agents can buy access to. Not another data feed — the trust layer that makes any feed safe to act on.
Five overnight prototypes became one honest product. Each layer below is real, statused plainly, and linked to the thing itself — no ghost products, no invented counts.
Typed signals, intent profiles, provenance chains. MIT-licensed, versioned, open comment window.
READ THE SPEC ↓AGIF-typed signal streams behind a working paywall. Unpaid request → HTTP 402. Paid key → typed, signed intelligence.
CALL THE ENDPOINT ↓A curated catalog of real, working agent skills and frameworks from the IDC shop — honest counts, real install commands.
BROWSE THE BAZAAR ↓Agent memory taxonomy — episodic, semantic, procedural. Parked until feed revenue data makes the build case.
HONEST STATUS ↓This is the core of the product, working in your browser: a stream of AGIF-typed signals, filtered in real time by the intent profile you build on the left. The controls emit valid profile JSON — copy it out, or send it straight to the live endpoint below.
SIGNALS IN THIS DEMO ARE SYNTHETIC AND GENERATED CLIENT-SIDE — THE ROUTING LOGIC IS THE REAL REFERENCE IMPLEMENTATION. THE VAULT BELOW SERVES REAL ONES.
A human reads a headline and infers. An agent parsing freeform JSON guesses — and a guessing agent with execution authority is a liability, not an asset.
Feeds bill for volume, so they ship volume. Your agent burns context window and inference cost discarding 99% of what it paid to receive.
No signature, no chain of custody, no confidence score. An agent acting on unprovenanced data can't tell intelligence from injection.
AGIF — the Agent Intelligence Format — is an open, versioned schema for machine-consumable intelligence, now published with JSON Schemas, a zero-dependency validator, and CI. Three core objects do the work. Explore the draft below; every block is copyable.
{
"agif": "0.1", // spec version — always present, always first
"id": "sig_7f3a9c", // globally unique, sortable
"type": "price_move", // one of 14 typed classes, closed enum
"domain": "finance", // routing namespace
"entity": "NVDA", // named subject, normalized
"value": { "pct": -4.2, "window_s": 300 }, // payload typed BY signal class
"confidence": 0.91, // 0–1, ML-scored upstream
"ts": 1781171526904, // epoch ms
"provenance": "prv_e21b…" // pointer into the hash chain →
}
{
"agif": "0.1",
"agent_id": "agent_prod_7a3f",
"domains": ["finance", "competitive"], // subscribe by namespace
"signal_types": ["price_move", "news_event"],
"entities": ["NVDA", "TSLA"], // empty array = all entities
"min_confidence": 0.70, // router-enforced floor
"delivery": "at_least_once"
}
{
"agif": "0.1",
"id": "prv_e21b4d",
"source": "curated:idc_research", // where it entered the world
"chain": [ // every transform, hashed
{ "op": "ingest", "sha256": "9f2c…" },
{ "op": "normalize", "sha256": "b7a1…" },
{ "op": "score", "sha256": "e4d8…" }
],
"payload_sha256": "…" // verify before acting — demo below ↓
}
Every AGIF signal carries a hash chain from ingestion to delivery. Below is a real verification: the button computes SHA-256 over the payload in your browser and checks it against the recorded hash. Tamper with the payload and watch trust collapse — exactly as your agent would.
GET /v1/signals serves real, curated, AGIF-typed signals about the agent economy — every one provenance-hashed, every one citable. No key? You get an honest HTTP 402 with payment instructions, machine-readable. That's not an error page; that's the product working. Try it right here — this page calls the real endpoint.
The Bazaar lists what the IDC shop actually ships — build orchestration, design pipelines, the AGIF validator — with install commands that work and counts pulled from GitHub, not imagination. Small catalog, every entry real.
The memory-taxonomy thinking (episodic / semantic / procedural) is good and we're keeping it. But we don't ship claims without code: Context Engine stays parked until /v1/signals revenue data justifies a thin, real MVP — or it folds into NeuralForge, where IDC's memory work actually lives.
Nobody out-feeds Bloomberg from Huntsville. But standards have a different physics: the spec that agents adopt first becomes the spec every feed must speak. Stripe never owned money — it owned the format for moving it. The rails for agent payments got built by giants in 2025; we ride them and own the format on top.
The three core objects — signal, intent profile, provenance — published as an open draft with JSON Schemas, a zero-dependency validator, CI, and a public comment window. The playground on this page is its living documentation.
A real vault of curated, provenance-hashed signals behind HTTP 402. Stripe checkout issues metered keys; every request lands in a usage ledger. Small, real, typed — 15 honest signals beat 2,847 fake ones.
The routing logic running in your browser right now, hardened and packaged: an in-memory intent matcher, the schema validators from the spec repo, and a client SDK with replay support.
Managed AGIF streams over WebSocket with at-least-once delivery, then cross-publisher signature verification so intelligence from any AGIF-speaking source carries portable trust. The endgame — and the reason the spec comes first.
We're onboarding a handful of agent builders to pressure-test AGIF v0.1 against real workloads. You bring an agent and opinions; we bring the format, the router, the vault, and fast iteration. Replies come from a human.