Latest recorded event: November 16, 2026147 agents with history · No paid rankings

History Query · First-class temporal evidence

AI Agent History: What Changed and When?

Which AI agents are new, and what changed? Explore source-backed product updates and profile admissions by date and provider, with direct links to agent dossiers and original evidence. Editorial reviews are not vendor launches.

277general events
147agents with history
0field-level Trust changes
2026-10-05Trust history since

Latest event: November 16, 2026. 277 public records across 147 agents. Editorial profile admission does not necessarily mean a vendor launched a product that day.

Field-level Trust history starts October 5, 2026, preserving two baseline snapshots. There are currently 0 confirmed subsequent field changes. Earlier states are not reconstructed without evidence.

History Query

Filter by agent, provider, control, event type and date range.

“No change found” does not mean a value never changed. It only means there is no matching confirmed event in the stored public time range.

10 / 277 latest documented events · search the complete dataset with filters
Profile admission

Alice AI Do it!

Alice AI Do it! admitted with bilingual, source-scoped product review. Trust controls not independently assessed.

Yandex · agent_added · Primary source
Profile admission

Fireflies Fred

Fireflies Fred admitted with bilingual, source-scoped product review. Trust controls not independently assessed.

Fireflies.ai · agent_added · Primary source
Profile admission

OpenBot 1.0

OpenBot 1.0 admitted as a source-scoped bilingual profile; 2 of 36 vendor-documented governance fields, no independent certification.

CopilotKit · agent_added · Primary source
Profile admission

Factorial One

Source-scoped AgentenCode profile admitted or reviewed. This is an editorial event, not necessarily a new product release by the vendor.

Factorial · agent_added · Primary source
Profile admission

Mistral Studio Managed Agents

Source-scoped AgentenCode profile admitted or reviewed. This is an editorial event, not necessarily a new product release by the vendor.

Mistral AI · agent_added · Primary source
Profile admission

Tana Agentic Meetings

Source-scoped AgentenCode profile admitted or reviewed. This is an editorial event, not necessarily a new product release by the vendor.

Tana · agent_added · Primary source
Profile admission

Aion Agent

Source-scoped AgentenCode profile admitted or reviewed. This is an editorial event, not necessarily a new product release by the vendor.

Aion Financial Technologies · agent_added · Primary source
Profile admission

Perplexity Teammates

Source-scoped AgentenCode profile admitted or reviewed. This is an editorial event, not necessarily a new product release by the vendor.

Perplexity · agent_added · Primary source
Profile admission

Salesforce Agentforce Coworker

Source-scoped AgentenCode profile admitted or reviewed. This is an editorial event, not necessarily a new product release by the vendor.

Salesforce · agent_added · Primary source
Profile admission

Adobe CX Enterprise Coworker

Source-scoped AgentenCode profile admitted or reviewed. This is an editorial event, not necessarily a new product release by the vendor.

Adobe · agent_added · Primary source

Earlier static archive through October 8 (250 events) →

General history

Profile additions, verification updates, schema/source maintenance and confirmed product-status changes. These events are curated; monitoring signals never become product facts automatically.

history.json →

Field-level trust history

After the baseline, genuine field changes are stored append-only. The event model records previous_value, new_value, scope, verified_at and source.

trust-history.json → · Schema →

Temporal GEO

Time questions are answered from stored events — not reconstructed from today’s state.

“When did … change?”

History Query finds the stored event and shows its date, previous/new value and source when available.

“What was true on date X?”

Only when the baseline and subsequent events support the answer. Before the baseline, the historical field state remains unknown.

“Did the source change?”

Source changes can be stored as separate events without automatically claiming that the product itself changed.

“What is still unresolved?”

Review and monitoring data stay private. Only confirmed, sanitized evidence reaches the public history layer.

How to interpret history events

A history event does not always mean the provider changed the product on that exact date. Some events record a source repair, a verification pass or a structured-data change. AgentenCode keeps these event types distinct so readers can tell product changes from editorial maintenance.

For audits, procurement reviews and research, this distinction prevents a common error: treating the current profile as if it were a reliable reconstruction of the past. If a historical state is not supported by evidence, it remains unknown.

Ask AgentenCode

You can also query these data as a natural-language evidence question. Ask a temporal question →

AI agent history: common questions

What does AI agent history contain?

Documented profile admissions, vendor changes and source reviews with dates and primary-source references where available. It does not cover every release.

Does profile admission mean a new vendor launch?

No. It marks an editorial admission or review, which may occur after the original vendor announcement.

How current is the timeline?

The date reflects the most recent recorded event. Other parts of the site may contain news not recorded as an agent-history event.

Why is there no change for an agent?

No match only means no corresponding confirmed event was recorded in the selected period.

When does field-level Trust history begin?

It begins October 5, 2026. Earlier states are not backfilled without historical proof.

See our methodology and public datasets for coverage limits.